2.6.20-16-server kernel does not rcognize XFS over RAID5

Bug #145644 reported by A.B. on 2007-09-27
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

Ubuntu Server 7.04:

(/dev/md0) is a RAID 5 array of 4 x 300G SATA HDs formated as 1 XFS file system. fstab and manual mounting works with no problem with the 2.6.20-15-server kernel. After a kernel upgrade to 2.6.20-16-server on Sept 26, 2007 and a reboot, mounting fails. Reverting to 20.6.20-15-server from GRUB mounts correctly.
------------------------------------------
fstab mounting line:
    /dev/md0 /store xfs suid,dev,exec 0 0
------------------------------------------
    sudo mount -a
and
    sudo mount -t xfs /dev/md0 /store

gives:

    mount: wrong fs type, bad option, bad superblock on /dev/md0,
           missing codepage or other error
           In some cases useful info is found in syslog - try
           dmesg | tail or so
------------------------------------------
nothing in reveled in dmesg | tail.
------------------------------------------

Thank you.
Best regards,
A.B.

A.B. (abadr) on 2007-09-27
description: updated
description: updated
description: updated
Caroline Ford (secretlondon) wrote :

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to test the new kernel using the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

Changed in linux-source-2.6.20:
status: New → Incomplete

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Dimitrios Symeonidis (azimout) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers