Disk space question

[Dave Johnson_1]

I am rather new to Tru64. I have managed HP-UX for more than 10 years, now I have this Tru64 box to keep running. The output from uname -a includes "V5.1 2650 alpha".
I received an email from root telling me it was out of disk space, but the message does not tell me which filesystem it was, it reports a domain. When I run bdf on that system, the reported domain is listed several times associated with all but the root file system. The output is not what I would have expected. It looks like all the file systems are actually sharing the same disk space. How does this work? Can you recommend a good admin book for me?
Thanks,
-Dave

[Steven Schweda]

"sizer -v" can be slightly more informative
than "uname -a".

> [...] but the message does not tell me
> which filesystem it was, it reports a
> domain.

And you didn't tell anyone else what "bdf"
actually said, so it's tough for anyone else
(non-psychic) to interpret its output for
you (without a lot of guessing).

> Can you recommend a good admin book for me?

http://h30097.www3.hp.com/docs/
http://h30097.www3.hp.com/docs/pub_page/doc_list.html
http://h30097.www3.hp.com/docs/pub_page/V51B_DOCS/V51B_DOCLIST.HTM
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/ARH96DTE/TITLE.HTM

[Dave Johnson_1]

#root#@/> sizer -v
Compaq Tru64 UNIX V5.1B (Rev. 2650); Fri Oct 1 02:26:46 EDT 2004

Filesystem kbytes used avail %used Mounted on
root_domain#root 4194304 158104 4030832 4% /
linus_fdmn#dir01 2088763384 48 76289400 1% /dir01
linus_fdmn#usr 2088763384 2597808 76289400 4% /usr
linus_fdmn#var 2088763384 1414976 76289400 2% /var
linus_fdmn#dir02 2088763384 136 76289400 1% /dir02
linus_fdmn#users 2088763384 2545080 76289400 4% /usr/users
linus_fdmn#dir03 2088763384 757392 76289400 1% /dir03
linus_fdmn#dir04 2088763384 14412520 76289400 16% /dir04
linus_fdmn#dir05 2088763384 4364320 76289400 6% /dir05
linus_fdmn#dir06 2088763384 24 76289400 0% /dir06
linus_fdmn#dir07 2088763384 20452032 76289400 22% /dir07
linus_fdmn#dir08 2088763384 8935896 76289400 11% /dir08
linus_fdmn#dir09 2088763384 10559216 76289400 13% /dir09
linus_fdmn#dir10 2088763384 309208 76289400 1% /dir10
linus_fdmn#dir11 2088763384 6310048 76289400 8% /dir11
linus_fdmn#dir12 2088763384 32214088 76289400 30% /dir12
linus_fdmn#dir13 2088763384 16 76289400 1% /dir13
linus_fdmn#dir14 2088763384 10182552 76289400 12% /dir14
linus_fdmn#dir15 2088763384 1977088 76289400 3% /dir15
linus_fdmn#dir16 2088763384 415319576 76289400 85% /dir16
linus_fdmn#dir17 2088763384 135299672 76289400 64% /dir17
linus_fdmn#dir18 2088763384 268971168 76289400 78% /dir18
linus_fdmn#dir19 2088763384 41622088 76289400 36% /dir19
linus_fdmn#dir20 2088763384 32800 76289400 1% /dir20
linus_fdmn#dir21 2088763384 182860112 76289400 71% /dir21
linus_fdmn#dir22 2088763384 343776 76289400 1% /dir22
linus_fdmn#dir23 2088763384 17591504 76289400 19% /dir23
linus_fdmn#dir24 2088763384 141059272 76289400 65% /dir24
linus_fdmn#dir25 2088763384 233808448 76289400 76% /dir25
linus_fdmn#dir26 2088763384 41675904 76289400 36% /dir26
linus_fdmn#dir27 2088763384 16 76289400 1% /dir27
linus_fdmn#dir28 2088763384 141110472 76289400 65% /dir28
linus_fdmn#dir29 2088763384 233808448 76289400 76% /dir29
linus_fdmn#dir30 2088763384 41630848 76289400 36% /dir30
linus_fdmn#dir31 2088763384 16 76289400 1% /dir31

[Rob Leadbeater]

Hi Dave,

A file domain, linus_fdmn can contain a number of different filesets, dir01, dir02 etc. on your system.

You can see the total diskspace available in the file domain with the output of showfdmn, so in your case:

# showfdmn -k linus_fdmn

That command will also show you the physical disks or volumes that make up the domain.

Hope this helps,

Regards,

Rob

[Dave Johnson_1]

#root#@/> showfdmn -k linus_fdmn

Id Date Created LogPgs Version Domain Name
4329a8e0.000884f4 Thu Sep 15 13:01:20 2005 512 4 linus_fdmn

Vol 1K-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 987758584 33185648 97% on 256 256 /dev/disk/dsk1d
2 786432000 23419760 97% on 256 256 /dev/disk/dsk2c
3 314572800 19676680 94% on 256 256 /dev/disk/dsk3c
---------- ---------- ------
2088763384 76282088 96%

[Rob Leadbeater · Accepted solution]

OK. So you've got three physical disks in your file domain, that total around 2TB, and there's about 72GB free.

That free space is shared between all of the file sets in the domain, so if one mount point were to use the remaining space, then all of the mount points would drop to 0 available.

Your layout does appear to differ from a standard installation, in that /usr and /var appear to be in a data domain. Not that there's anything wrong with that, but it's more usual to see something like:

usr_domain#usr /usr
var_domain#var /var

With /usr and /var being shared with data you run the risk of getting into trouble if the file systems do fill up.

As you're on 5.1B you might find the output of "df -h" more readable.

With regards to books, this one's quite good, although you can get a lot of info from the man pages.

http://www.amazon.com/Tru64-System-Administration-Handbook-Technologies/dp/1555582273

Hope this helps,

Regards,

Rob

[Venkatesh BL]

Welcome to Tru64! Yes, the concept here is that domain is a 'pool' of storage for your filesets. A fileset is the actual mountable entity. All filesets share the storage space available in the domain they reside in.

To see the filesets in your domain, use:
# showfsets linus_fdmn

Each fileset set would be mounted using the syntax:
# mount domain#fileset

Ex:
# mount linus_fdmn#dir01 /dir01

To add more space to the linus_fdmn domain, you can do:
# addvol

Ex:
# addvol /dev/disk/dsk1c linus_fdmn

All these have manpages, so check'em out.

[Dave Johnson_1]

Thank you very much for the information.

[Hein van den Heuvel]

Welcome to Tru64! You'll like it.

That's a mighty big domain with lots of mount points. Neither is very tyipcal, but it is valid.

If there is a cleanup / purge task in the application then this would be a good time to launch it :-).

Unless there are a bunch of 'core' and 'trc' or 'log' files building up this IMHO is an application problem, not a system management issue, but that might not help you.

If you want to help the application folks, then you may want to point then to (sub)directories where potentially a lot can be gained. Here, that would be those with more than '75% used', that is larger than 200GB.

Filesystem used %used Mounted on
linus_fdmn#dir16 415319576 85% /dir16
linus_fdmn#dir18 268971168 78% /dir18
linus_fdmn#dir21 182860112 76% /dir25
linus_fdmn#dir29 233808448 76% /dir29

Commands like "du -ks /dir16/*" might help.

If no significant amount of data can be purged and more data is expected, then would NOT add more diskspace to this domain, but create a 'fresh' domain and move one or more of the larger fileset there with a vdump | vrestore task.

Actually... if there are 'static' / old mount points there, then those are probably the best to be moved.

Keep that df output list, and run it again in a few days.
Write a small awk/perl script to figure out which fileset/mountpoint is growing most.
Focus the cleanup activity there.

Enjoy Tru64!
Hein.