commit b96de000bc8bc9688b3a2abea4332bd57648a49f breaks subvolume mount on one of my systems. I've bisected a mount problem to this commit. Situation is:
- one hdd with btrfs - default subvolume (rootfs) is different from subovlid=0 - at boot, several subvols are mounted at /home/$DIR after commit b96de000bc8bc9688b3a2abea4332bd57648a49f this is not possible anymore. Trying to mount results in (example): mount: /dev/sda1 is already mounted or /home/video busy The output of btrfs show is curious too: btrfs fi show Label: none uuid: 43438ef5-adac-46a9-823e-14951ee6866a Total devices 1 FS bytes used 150.05GiB *** Some devices missing Btrfs v3.16 As this is a laptop with only one drive bay, this was never a multi device setup. I've two more systems with kernel version >3.17-rc3 running and no problem like this. regards, Johannes -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html