Hello,
thanks for your info. That means it is a bug in ext3. It seems
to ignore the errors=continue mount option, although
according to the manpage it should support all the
options that ext2 does.
Unfortunately I'm not able to reproduce this exact behaviour, however
I am able to produce a file
We're also seeing this bug with 2.6.15 after replacing disks in an NFS
server. It seems worth mentioning that the new filesystem has fewer
inodes, both in use and available total than the old filesystem.
In the kernel source, look at nfs_vfs_read() in fs/nfsd/vfs.c. It's
called through about a ha
2 matches
Mail list logo
