Summary: | xfs with blocksize 1024 suggest corrupted disk | ||
---|---|---|---|
Product: | Gentoo Release Media | Reporter: | Marcin Rybak <marcin.rybak> |
Component: | InstallCD | Assignee: | Gentoo Release Team <releng> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | base-system, duaneg, kernel |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcin Rybak
2008-11-24 19:59:35 UTC
Base-system, do you guys have any idea what's going on here? have the kernel guys look at it ... sounds like a bug in xfs assuming the hardware stack is OK ... also, you might want to make sure you arent using 4k stacks in the kernel. i seem to recall that stacking xfs on things tends to result in kernel stack overflows. The suggestion to check 4k stacks is a good one. Could you attach your .config, please. Also which kernel you are using (output from "uname -a" will do nicely). Assuming you aren't using the latest vanilla kernel (2.6.27.7 as of writing) it would be helpful if you could also try that to check it hasn't already been fixed. Next, could you please attach a task dump after reproducing the problem. To do that ensure Magic-SysRq is enabled in the kernel, reproduce the bug, then do an "echo t > /proc/sysrq-trigger". Do this with the latest vanilla kernel, if possible. I've just tired to reproduce this bug in 2.6.27.7 and it does not appear. As I said, it appers at gentoo live cd 2008.0 and for example kernel 2.6.22 too. No more time for more tests - sorry OK, thanks for testing. If you see the problem recur with a current kernel please reopen the bug (ideally with the info requested in 3). |