On 06/06/97 11:18:16 you wrote:
>I have started to run real low on free disc space on drive 1.  I have
>lots of free disc on drives 2 and 3.  I want to move some files from
>drive 1 to drive 2 and/or 3 to get drive 1 back above 10% free.
>However,  the I am having a hard time finding any databases that are one
>drive 1.  I think that most of my problems come from loading on samba
>and odbclink/se.  But they are mostly in the posix name spaces and I
>can't find out what drive they are on.
>
>Is there a command that shows what disc a file is on in the posix name
>space?  How do you move a file in the posix name space to another drive?

I would like to add a couple of notes in addition to the replies already posted to this topic...

1) By performing an UPDATE CONFIG from the most recent SLT, you will be able to resurrect files
from the SLT that you need (but were on non-LDEV1 drives) for booting, but note that you then
should run FSCHECK.MPEXL.TELEUP with the command CA ALL.  FSCHECK will display messages
(essentially) about orphaned extents, which will most likely be those that you re-created on
LDEV1 with the SLT, that were not solely on LDEV1 before the UPDATE CONFIG.  You'll want to
delete the orphans, do not re-insert them into the directory. (remember though: before you do
this, backup-backup-backup!)

2) There were also mentions about using DEFRAGX to move files off of LDEV1.  I do not recommend
that quite yet.  I am working with LUND & Allegro to double-check a problem I have run into with
the MAKEROOM command (I am *not* de-recommending DEFRAGX; it is an excellent disk utility, I
just suggest holding off on the moving of files off of LDEV1 until the next release).  I believe
that I have found it possibly moves certain .SYS files that are not labelled as on device
$SYSTEM_MASTER.

3) You can easily prevent new files from being written to LDEV1 by doing an ALTERVOL in VOLUTIL.
I recommend this method *much* more than moving files around after the fact!  Set the PERM to
whatever the current perm usage is on LDEV1 (DISCFREE C), but make sure that you place TRANS to
100 for LDEV1 at the same time (for virtual memory, etc).  In fact, you can set the PERM to a
low value, such as 50, and then re-install any suspect products and they should re-install on
devices other than LDEV1!  You should be able to keep PERM low on LDEV1 even after this point,
but keep in mind that in order for you to be able to save files on LDEV1 (for example, if you do
changes in NMCONFIG, it'll want to save it to LDEV1) you'll have to temporarily change PERM to a
higher value (and possibly at the same time, lower the TRANS on LDEV1), save the config file,
then set the PERM/TRANS back.

Good luck...
Garry Darrer  716-272-5366
(of course, the opinions expressed above are yaddah, yaddah, yaddah...)