last 541 kernel damages fileystem .. starting fresh FC3T2 candidate.

Andy Green fedora at warmcat.com
Mon Sep 6 16:31:41 UTC 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 06 September 2004 17:11, Stephen C. Tweedie wrote:

> I had seen that on older kernels too --- it doesn't seem to be related
> to the recent data-corrupting problems.  And when "df" shows bad data,
> I'm still seeing the kernel return valid data from strace:
>
> statfs("/boot", {f_type="EXT2_SUPER_MAGIC", f_bsize=1024, f_blocks=248895,
> f_bfree=389288, f_bavail=376438, f_files=64256, f_ffree=64210, f_fsid={0,
> 0}, f_namelen=255, f_frsize=1024}) = 0 write(1, "/dev/sda1              
> 248895 -"..., 74) = 74
> /dev/sda1        248895 -18446744073709411223    376438 101% /boot
>
> At the moment they look like separate problems.

Hum, an fsck makes the df -h problem go away.  It's hard to see how if the 
data returned from the kernel is really correct in both cases?

BTW what kind of unhappiness can we expect from this "inode problem"?  Just 
things that e2fsck will make go away?

- -Andy

- -- 
http://www.addintelligence.co.uk -- we design custom hardware and software for 
your products 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBPJDzjKeDCxMJCTIRAt0hAJ9WQ1myVFsdII9WDhWlH7xJodQ/UwCeInBp
mmYTFCdwG2IY+hgI2wJO2fs=
=dFCy
-----END PGP SIGNATURE-----





More information about the test mailing list