On Mon, Oct 07, 2002 at 05:07:20AM +0000, JP Howard wrote: > Over the last two days we've been seeing a fair bit of this: > > ---- > # ls -laR > /dev/null > ... > ls: ./server2/b/user/bxyz/392.: Input/output error > ---- Today, I saw a similar thing: ls shows a file ls -l doesn't show it, and ls -l filename gives an I/o error. > debugfs: stat 392. > Inode: 14992585 Type: regular Mode: 0600 Flags: 0x0 Generation: > 2449155561 > User: 504 Group: 505 Size: 0 > File ACL: 0 Directory ACL: 0 > Links: 0 Blockcount: 0 > Fragment: Address: 0 Number: 0 Size: 0 > ctime: 0x3da0be92 -- Sun Oct 6 17:52:02 2002 > atime: 0x3da05967 -- Sun Oct 6 10:40:23 2002 > mtime: 0x3da0be92 -- Sun Oct 6 17:52:02 2002 > dtime: 0x3da0be92 -- Sun Oct 6 17:52:02 2002 > BLOCKS: Our debugfs output is suspiciously similar: Inode: 28332642 Type: regular Mode: 0000 Flags: 0x0 Generation: 0 User: 503 Group: 100 Size: 0 File ACL: 0 Directory ACL: 0 Links: 0 Blockcount: 0 Fragment: Address: 0 Number: 0 Size: 0 ctime: 0x3eff64e1 -- Mon Jun 30 00:14:57 2003 atime: 0x3efffe54 -- Mon Jun 30 11:09:40 2003 mtime: 0x3eff64e1 -- Mon Jun 30 00:14:57 2003 dtime: 0x3ef38040 -- Fri Jun 20 23:44:32 2003 BLOCKS: > Any ideas on what's causing this? e2fsck causes the problem files to be > removed. For now we've disabled directory indexing--if the problem > continues after doing this, I'll update the list with the details. No idea, but on our server it happens without HTREE. It's a plain 2.4.21, but until yesterday, we had 2.4.18, so the corruption could have been caused by the older kernel. It's a 540GB ext3 partition on top of LVM, and has been resized a few times with e2fsadm. Jan
Attachment:
pgp00031.pgp
Description: PGP signature
