Bug 282 - Kernel panic/Bad magic number on XFS filesystem
: Kernel panic/Bad magic number on XFS filesystem
Status: RESOLVED INVALID
Product: XFS
Classification: Unclassified
Component: XFS kernel code
: unspecified
: All Linux
: blocker
: ---
Assigned To: XFS power people
:
:
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2003-10-11 11:17 CDT by owen
Modified: 2003-10-16 18:24 CDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description owen 2003-10-11 11:17:10 CDT
Upon using kernel version 2.6.0-test5, the kernel panics and states that the
magic number on my root partition is bad. However, on the 2.4.22-ac4 kernel,
this problem does not exist.

This problem was encountered on:
2.4.20 kernels Con Kolivas built
2.6.0-test5 kernel
Gentoo's 2.4.20-gaming-r5 kernel

This problem was NOT encountered on:
2.4.22-ac4 kernel

This is a **blocker**. 

Gentoo's X86-Kernel team states the bug is upstream. I have reported this issue
many places :)
Comment 1 Stephen Lord 2003-10-14 11:08:10 CDT
The exact error message would be useful if you can provide it, we have
just seen a case here were a partition was reported as a different size
between 2.6 and 2.4. End result in that case was under 2.6 it was larger
and the end of the filesystem was not visible under 2.4. Mount does attempt
to read what the superblock reports as the last block in the fs and will
fail the mount if it cannot do so.
Comment 2 owen 2003-10-16 16:24:36 CDT
*sigh* I am resolving this as INVALID. This is my own stupid fault. Apparently
INITRD throws an error if I do not build in ext2fs support, and that error reads
bad magic number. This is by no means a bug with XFS. XFS rocks.

Sorry for the bugspam ;-((