Messages in this thread | | | Date | Thu, 29 Jan 2004 06:44:00 -0500 | From | Theodore Ts'o <> | Subject | Re: ext3 on raid5 failure |
| |
On Wed, Jan 28, 2004 at 11:54:44AM +0100, Jan Dittmer wrote: > >>After 2 days in my freshly setup debian (2.6.1-bk6), same error. But > >>this time at least I know it's because I tried to delete those files in > >>the lost+found directory... > > > > > >How did you come to that conclusion? > > sfhq:/mnt/data/1/lost+found# ls -l > total 76 > d-wSr----- 2 1212680233 136929556 49152 Jun 7 2008 #16370 > -rwx-wx--- 1 1628702729 135220664 45056 May 4 1974 #16380
Ok, this looks like random garbage has gotten written into inode table.
If you can make this happen consistently with 2.6 and not with 2.4, then that would be useful to know. There may be some kind of race condition or problem with either the raid5 code, or the combination of raid5 plus ext3. It's unlikely this kind of error would be caused by a flaw in the ext3 code alone, since this is indicative of complete garbage written to the inode table, or a block intended for another location on disk getting written to the inode table. The natural suspect is at the block device layer and below.
- Ted - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |