Re: /u directory, users and filePro
- From: bv@xxxxxxx (Bill Vermillion)
- Date: Mon, 29 May 2006 06:35:01 GMT
In article <1148758841.450667.69160@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Dan Martin <dc.martin@xxxxxxxxxxx> wrote:
FrankS wrote:
"Steve M. Fabac, Jr." <smfabac@xxxxxxx> wrote in message
news:44774E00.19D4EED5@xxxxxxxxxx
FrankS wrote:have
"Steve M. Fabac, Jr." <smfabac@xxxxxxx> wrote in message
news:44772A0D.218ACFBA@xxxxxxxxxx
FrankS wrote:
"Jean-Pierre Radley" <jpr@xxxxxxx> wrote in message
news:20060526010537.GA20419@xxxxxxxxxxxxxxxxxxx
FrankS typed (on Thu, May 25, 2006 at 11:53:46PM +0000):
| Maybe someone can offer some advice.
|
| I've just installed a new server running SCO Open Server 6 and
running. On all of| installed my application and users. The system is up and
directory.| my previous systems, I've had my application and users in the /
directory?| df -v shows that most of the freespace is in the /u directory.
|
| Should I move my application (/appl) and my users to the /u
%used
Yes.
| If so, what is involved in doing this?
Well, using mv, tar or cp... Which part seems daunting?
--
JP
==> http://www.frappr.com/cusm <==
Sorry,
I'm not real comfortable with Unix, just thought I'd ask.
Thanks for the response. I appreciate your help.
Frank
Frank,
No need to be sorry, JP was just asking if you have done
any work to investigate your problem.
There are so many ways to answer your question, that without
specifics on your request, we could get involved in writing a
book.
1) dfspace will show your file usage. Run it and post it here.
Mount Dir Filesystem blocks used free
/ /dev/root 10239996 4437988 5802008 44%
/stand /dev/boot 81918 12830 69088 16%
/u /dev/u 128735440 4070168 124665272 4%
Frank, Post /etc/dfspace not df its easier for humans to grasp:
$ /etc/dfspace
/ : Disk space: 29945.86 MB of 33321.78 MB available (89.87%).
/stand : Disk space: 33.30 MB of 39.99 MB available (83.26%).
Total Disk Space: 29979.16 MB of 33361.78 MB available (89.86%).
My rough calculations indicate root is approx. 5G and u is 67G.
$ /etc/dfspace
/ : Disk space: 2832.74 MB of 4999.99 MB available (56.66%).
/stand : Disk space: 33.73 MB of 39.99 MB available (84.34%).
/u : Disk space: 60871.71 MB of 62859.10 MB available (96.84%).
Total Disk Space: 63738.19 MB of 67899.09 MB available (93.87%).
$
Openserver
2) You said /u has most of the free space. This only would happen
if you installed it that way by specifying the blocks dedicated
to the u file system. The OS does not put any files in /u during
the system installation (Openserver 5.0.x, I can't speak for
6.0).
I did not Install the operating system (OS 6), but, when I
create users, the default is /u/usr. I changed that, and
all my users are in /usr
Well, someone did, and when they did, they set /u to > 10X
the size of the root file system (67G?).
So if you have moved the users to /usr and nothing remains
in /dev/u, just use divvy and make /u 2 to 3 Gigs, and make
some of the freed up space as "appl" and size it to fit your
requirements for /appl plus room to grow.
Hello Frank,
Why shouldn't I just reduce the size of /u, as you mention, and then
increase the size of /(root)?
Unless you know otherwise, and with certainty, I would assume that
resizing the root fs would wipe it clean.
Correct.
Is there a convention that says that I shouldn't put anything
in the / (root) directory? This application has run on Xenix
and Unix in the root directory for that last 20+ years.
There is a convention that says keep your user data, application
programs application data off of the root fs. I'm not sure what
the origin is, but it allows you, for example, to have separate
backups of separate filesystems, and allows for recovery of
specific filesytems, while leaving others undisturbed. Many do
not follow the convention.
When I've seen a corrupted file-system it seem to be that the vast
majority of time it is in /, while all other file systems survive
intact. Since / need to be bootable, and the others don't,
repairing a system with a bad / means that you usually have all the
data on the other filesystems intact. Even if you perform nightly
verified backups, intact non-root filesystems will be more
up to date, and will typically require less data re-entry.
Since you have a /u filesystem, consider these 2 steps:
mv /appl /u/
ln -s /u/appl /appl
He doesn't have to do that.
All he needs to do is change the filePro defaults in the
/etc/default directory. Using the documented variables you can
even split the data and the programs into separate places.
I used to do this in the days when the biggest hard drives
were 70 MB, and I'd have part of the filePro on one drive, and
the data on the other. I also found that on a heavily used system
having the indexes on one drive and the key/data on another meant
for less head contention and improved performance. Now with the
really fast drives out there, the large amount of buffers in the
drive, and the large memory availabilty for the OS, you'd only have
to do this in extreme circumstance - and then only if you can
test and make sure it's working.
This should allow you to use the space on /u, without disturbing
any programs or scripts that refer to /appl
The filePro loves [or loved] to create /appl. This started with
it's first implementations on the old Radio Shack 16 running Xenix.
Only in the last few years do you have options to install this
elsewhere.
Bill
--
Bill Vermillion - bv @ wjv . com
.
- Follow-Ups:
- Re: /u directory, users and filePro
- From: FrankS
- Re: /u directory, users and filePro
- References:
- /u directory, users and filePro
- From: FrankS
- Re: /u directory, users and filePro
- From: Steve M. Fabac, Jr.
- Re: /u directory, users and filePro
- From: FrankS
- Re: /u directory, users and filePro
- From: Dan Martin
- /u directory, users and filePro
- Prev by Date: Re: /u directory, users and filePro
- Next by Date: Re: /u directory, users and filePro
- Previous by thread: Re: /u directory, users and filePro
- Next by thread: Re: /u directory, users and filePro
- Index(es):
Relevant Pages
|
Loading