1847203 Members
3126 Online
110263 Solutions
New Discussion

bdf discrepance

 
alessandro_37
Advisor

bdf discrepance

All,
this is the output of bdf command on my HP-UX Server 11.0

/dev/vg00/lvol3 143360 58136 80028 42% /
/dev/vg00/lvol1 83733 43176 32183 57% /stand
/dev/vg00/lvol8 1175552 460569 672897 41% /var
/dev/vg00/lvol7 1273856 1109533 154105 88% /usr
/dev/vg00/lvol4 1228800 196857 968125 17% /tmp
/dev/vg00/lvdati3 3145728 2153160 930538 70% /oradati3
...
...

For example in /tmp Fileystem:
if total kb are 1228800 the sum of used (196857) + avail (968125) should be equal to total kb ( 1228800), but:

Total = 1228800
Used + avail = 1164982

where are the others 63818 KB?

Thanks in advance for your support.
Alessandro

7 REPLIES 7
Steven E. Protter
Exalted Contributor

Re: bdf discrepance

There have been patches to bdf over the years. Is your system properly patched? patch database link http://itrc.hp.com

It also could have an issue due to files being deleted but still being on hold to a process. Booting the system or killng the process will fix that.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Robert-Jan Goossens
Honored Contributor

Re: bdf discrepance

Hi Alessandro,

About 8/9 % is used for filesystem administration on a hfs filesystem, check if your file system is hfs.

# cat /etc/fstab | grep tmp

Regards,
Robert-Jan
A. Clay Stephenson
Acclaimed Contributor

Re: bdf discrepance

Man bdf explains this pretty well; it depends upon the type of filesystem. For example, inode-tables, super-blocks, and other internal filesystem data structures (e.g. intent logs) are not taken into account.
If it ain't broke, I can fix that.
alessandro_37
Advisor

Re: bdf discrepance

These are my pathches...

B2491BA B.11.00 MirrorDisk/UX
B5456CA C.01.18.04 HP-UX Development Kit for Java*
B5725AA B.3.3.116 HP-UX Installation Utilities (Ign
ite-UX)
B8342AA B.11.00.05 Netscape Communicator 4.75
B8724AA A.01.06 CIFS/9000 Client
B8725AA A.01.06 CIFS/9000 Server
HPUXEng64RT B.11.00 English HP-UX 64-bit Runtime Envi
ronment
J2793B B.11.00.07 High Performance X.25 Link softwa
re for HP 9000
OnlineDiag B.11.00.17.08 HPUX 11.0 Support Tools Bundle, J
un 2001
T1302AA A.01.00 HP-UX Workload Manager Toolkits
T1471AA A.03.61.002 HP-UX Secure Shell
UnlimUserLic B.11.00.02 HP-UX Unlimited-User License
XSWGR1100 B.11.00.53.2 HP-UX General Release Patches, Ju
ne 2001
XSWHWCR1100 B.11.00.53.8 HP-UX Hardware Enablement and Cri
tical Patches, June 2001
#
# Product(s) not contained in a Bundle:
#

BEBagntux 10.5 BrightStor Enterprise Backup Agen
t for Unix 10.5 (Build 1226)
BEBcmagt 10.5 BrightStor Enterprise Backup Comm
on Module for Agents 10.5 (Build 1226)
bash 2.04 bash
binutils 2.11.2 binutils
gcc 3.0.1 gcc

I don't know wich is the patch to apply?

Thanks in advance Alessandro



Fabio Ettore
Honored Contributor

Re: bdf discrepance

Ciao Alessandro,

as Rob said, a part of filesystem is reserved to contain info about filesystem.
More is the size and more is this space used.
Or as SEP said it is a file deleted when it was opened yet; if this happens then bdf doesn't show that space freed.
Do

# du -sk /tmp

du is more reliable about space of file system.

Best regards,
Ettore
WISH? IMPROVEMENT!
alessandro_37
Advisor

Re: bdf discrepance

All,
thanks a lot for your reply.

/tmp is vxfs filesystem.
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2.

Now i have understood that could be some open file that are not shown in bdf command.

When i will execute an reboot on the Server
i will verify another one the bdf command.

Thanks to all
Alessandro
Gerhard Roets
Esteemed Contributor

Re: bdf discrepance

Alessandro

Open files does not influence it in this way. The thing is there is other file system structures ( Tables and intentlog etc) that have an influence. These should not be cleared with a reboot. That can be land you in a world of stress should they be cleared.

Few random examples.
Intentlog => Used by fsck apon reboot if the file system was not cleanly closed.
Inode table => by definitation very bad to clear.

But as stated earlier look at the patching for BDF. To display a list of patches on your system try " swlist -l patch" or "swlist -L patch" not to sure right now i always get the case in that parameter mixed up and no machine close by to test on.

Important things to look for is.
QPKxxxx this shows the support plus version you have updated to. This is General Release patches. If it is not there you will have to look in a lot more dtail.

Regards
Gerhard