At 08:30 -0400 28-03-2009, Theodore Tso wrote:
Can you verify exactly what kernel version you are using? This issue
is being discussed at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/330824
... and one person has said it was fixed in 2.6.28-rc8, and at least
one, possibly two people have reported that it has been fixed in
2.6.29. I think you're running some version of 2.6.28 or 2.6.28.y,
correct?
Had the problem with 2.6.28, 2.6.28.4 and 2.6.29-rc6. After
yesterday's crash I've upgraded to 2.6.29. For completeness' sake, my
ext4 RAID had been created from scratch, not upgraded from ext3.
Should I still apply the oneliner you posted yesterday on 2.6.29?
In the meantime I've tried mkfs -S, this complained about "File
exists while trying to create journal". fsck -y is running (has been
for a few hours) and appears to cycle through
Group xx inode table at yy conflicts with some other fs block. Relocate?
[repeated enough times to overflow my xterm's scrollback buffer]
Root inode is not a directory. Clear?
We'll see what I can fish out of the lost+found once it's done.
JDB.
--
LART. 250 MIPS under one Watt. Free hardware design files.
http://www.lartmaker.nl/
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
