mkfs.btrfs correctly work only with sequential order of the partitions

[RussianNeuroMancer]

First of all - not I found this bug. Credits to anonymous:
http://www.linux.org.ru/forum/general/5238223#comment-5240801

Bug description:

mkfs.btrfs work with sequential order of the partitions:

root@ubuntu:~# mkfs.btrfs /dev/sdb /dev/sdc /dev/sdd
WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
adding device /dev/sdc id 2
adding device /dev/sdd id 3
fs created label (null) on /dev/sdb
   nodesize 4096 leafsize 4096 sectorsize 4096 size 3.00GB
Btrfs Btrfs v0.19
root@ubuntu:~# mount /dev/sdb /mnt
root@ubuntu:~# mkfs.btrfs /dev/sdb /dev/sdc /dev/sdd
WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
/dev/sdb is mounted
root@ubuntu:~# umount /mnt
root@ubuntu:~# mount /dev/sdb /mnt

But not work with inverse order of partitions:

                                           ______please note______
root@ubuntu:~# mkfs.btrfs /dev/sdd /dev/sdc /dev/sdb
WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
adding device /dev/sdc id 2
/dev/sdb is mounted
root@ubuntu:~# umount /mnt
root@ubuntu:~# mount /dev/sdb /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
root@ubuntu:~# mount /dev/sdc /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
root@ubuntu:~# mount /dev/sdd /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sdd,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
root@ubuntu:~# uname -r
2.6.35-14-generic

I think this bug an easly reproduced in Maverick, but I can not test until Beta release.

[Jeremy Foshee (jeremyfoshee)]

Hi RussianNeuroMancer,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 628130

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[RussianNeuroMancer (russianneuromancer)]

This issue releated to any kernel version and reproduced with 2.6.35 and 2.6.36 kernels.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 628130

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]