Hi,
On standard ubuntu 14.04 a with an encrypted (cryptsetup) /home as brtfs
subvolume we have the following results:
3.17-rc2 : Ok.
3.17-rc3 and 3.17-rc4 : /home fails to mount on boot. If one try mount
-a then the system tells that the partition is already mounted according
to matab.
On a 3.17-rc4, btrfs fi sh returns nothing special:
"
Label: none uuid: f4f554bb-57d9-4647-ab14-ea978c9e7e9f
Total devices 1 FS bytes used 131.41GiB
devid 1 size 173.31GiB used 134.03GiB path /dev/sda5
Btrfs v3.12
"
I'm not sure if it has something to do with cryptsetup...
Xavier
Hi Johannes,
I've two more systems with kernel version >3.17-rc3
running and no problem like this.
Does this 3.17-rc3 also has the same type of subvol config
and it mount operation/sequence as you mentioned ?
> - one hdd with btrfs
> - default subvolume (rootfs) is different from subovlid=0
> - at boot, several subvols are mounted at /home/$DIR
I ran a few tests, on our mainline
----
mount -o subvol=sv1 /dev/sdh1 /btrfs
mount /dev/sdh1 /btrfs
mount: /dev/sdh1 already mounted or /btrfs busy [*]
mount /dev/sdh1 /btrfs1
echo $?
0
-----
[*] hope this isn't the problem you are mentioning.
Thanks, Anand
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
