SCO

Yes I rebooted and checked for No opened files !


Dexter

What about:
- telling what file system type you use ?
- running du on this file system while booted from a live media (emergency_disk) ?
- running fsck ?

> Fsck - reporting O.K.

> filesystems :

/stand (/dev/boot) - eafs
/ (/dev/root) - vxfs

> I haven't booted from live media yet and cannot report du of that.


Inspite of fsck O.K. and no opened files, what can be the reason for getting 26 gb extra ?


-----------------
Dexter

Did you run a full fsck ? (by default, fsck only checks the log with vxfs)

Code:

fsck -n -o full

Are you using a database ? AFAIK, vxfs supports specific extents that provide raw device like access that perhaps are not reported by du.

What says:

Code:

fsadm -E /

?

Not full but for /dev/root .

and I have never used fsadm . BTW, its output is :

fsadm -E /
Extent Fragmentation Report
Total Average Average Total
Files File Blks # Extents Free Blks
191612 80 1 420392286
blocks used for indirects: 400
% Free blocks in extents smaller than 64 blks: 8.82
% Free blocks in extents smaller than 8 blks: 1.00
% blks allocated to extents 64 blks or larger: 94.94
Free Extents By Size
1: 242 2: 428 4: 655 8: 663
16: 554 32: 466 64: 373 128: 258
256: 223 512: 144 1024: 92 2048: 4
4096: 4 8192: 2 16384: 1 32768: 8

I donot know how to read it.

----------------

Dexter

If you don't add the "-o full", SCO vxfs fsck doesn't check the file system. It just flushes the journal.
Neither do I as you posted it, please use code tags.