David Greaves wrote: > I just attempted a kernel upgrade from 2.6.20.7 to 2.6.25.3 and it no longer > mounts my xfs filesystem. > > I bisected it to around > a67d7c5f5d25d0b13a4dfb182697135b014fa478 > [XFS] Move platform specific mount option parse out of core XFS code around that... not exactly? That commit should have been largely a code move, which is not to say that it can't contain a bug... :) > I have a RAID5 array with partitions: > > Partition Table for /dev/md_d0 > > First Last > # Type Sector Sector Offset Length Filesystem Type (ID) Flag > -- ------- ----------- ----------- ------ ----------- -------------------- ---- > 1 Primary 0 2500288279 4 2500288280 Linux (83) None > 2 Primary 2500288280 2500483583 0 195304 Non-FS data (DA) None > > > when I attempt to mount /media: > /dev/md_d0p1 /media xfs rw,nobarrier,noatime,logdev=/dev/md_d0p2,allocsize=512m 0 0 mythbox? :) Hm, so it's the external log size that it doesn't much like... > I get: > md_d0: p1 p2 > XFS mounting filesystem md_d0p1 > attempt to access beyond end of device > md_d0p2: rw=0, want=195311, limit=195304 what does /proc/partitions say about md_d0p1 and p2? Is it different between the older & newer kernel? What does xfs_info /mount/point say about the filesystem when you mount it under the older kernel? Or... if you can't mount it, xfs_db -r -c "sb 0" -c p /dev/md_d0p1 -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
