Renaat Dumon wrote:
Mounting the filesystem without the geometry doesn't change things, the size
is still wrongly reported for .db files.
Ok, good to know. You should put it back now :)
I have however found files that should be 44 bytes (from ls -al) and
bacardi 0 # ls -al 000b21176cda012e1c0a7828f75347c3.289492.db
-rw------- 1 root root 44 Nov 2 20:18
000b21176cda012e1c0a7828f75347c3.289492.db
bacardi 0 # du -sk 000b21176cda012e1c0a7828f75347c3.289492.db
2147483532 000b21176cda012e1c0a7828f75347c3.289492.db
The value that du reports is the same as the one for 28-byte files, so it's
a constant, regardless of the real size of the file.
Interesting.
FWIW, this is a filesystem with a huge amount of files:
bacardi 0 # df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/root 8.0M 44K 8.0M 1% /
/dev/md0 12K 33 12K 1% /boot
/dev/md3 224M 11M 214M 5% /Storage
none 63K 1 63K 1% /dev/shm
I have requested my vendor to actually build a kernel with the most recent
patches + include the most recent userland progs. Could it be that a newer
version of xfs_repair might catch some inconsistencies the current version
would not ?
It would probably be good to see some of the repair output when you run it on a
problematic filesystem...
-Eric
|