[frameworks-solid] [Bug 427092] btrfs multiple device handling

[Méven Car]

https://bugs.kde.org/show_bug.cgi?id=427092

Méven Car <meven29 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|REPORTED                    |CONFIRMED

--- Comment #14 from Méven Car <meven29 at gmail.com> ---
(In reply to Chris Murphy from comment #13)
> Unfortunately I forgot to label this 2-drive Btrfs file system, so it has no
> label in the "2" version of attached udisksctl dump and sh5 details.
> 
> It appears as two "Linux filesystem" icons with a small orange/red symbol on
> the lower left corner, in Dolphin. And it doesn't automount, but if I click
> on either one, it mounts the btrfs file system correctly, it just looks odd
> to see two icons for the same file system, i.e. somehow dedup for the same
> file system UUID? e.g. in this case from blkid:
> 
> /dev/vdb1: UUID="b5c151d7-46e9-413b-8061-54d52f655b67"
> UUID_SUB="22d9fd70-0b6b-4720-879c-7186d5c47abf" BLOCK_SIZE="4096"
> TYPE="btrfs" PARTLABEL="Linux filesystem"
> PARTUUID="ea70e8dc-ac59-44b2-8e98-a77b49505611"
> /dev/vdc1: UUID="b5c151d7-46e9-413b-8061-54d52f655b67"
> UUID_SUB="0d9e14e0-20fb-4c6c-bf3a-eb17cce88a7f" BLOCK_SIZE="4096"
> TYPE="btrfs" PARTLABEL="Linux filesystem"
> PARTUUID="996e199c-0ed2-4ed5-beda-a64d2823
> 
> 
> If I click the first drive icon, its actually the icon below it that appears
> to get mounted. The icon I click on still has the "not mounted" symbol. The
> drive icon below it no longer has the "not mounted" symbol. Path to the file
> system mount is:
> 
> /run/media/chris/b5c151d7-46e9-413b-8061-54d52f655b67
> 
> I'm not at all certain about the proper way to handle it but maybe dedup by
> UUID? Btrfs doesn't care which /dev/ node is used for mounting. And also the
> mount command can accept a UUID directly as well as by /dev/disk/by-uuid/...
> 
> Possibly such functionality belongs in udisksd, if it's the service being
> requested to do the mount.

Once the filesystem is mounted how are the `solid-hardware5 details` and
`udisckctl` like ?

Does umount work ?

I guess we can dedup by FS UUID, which one to select though, maybe naively the
first one is enough.

udisksd is the service used to do the mount, so it seems any value we choose
should work.

-- 
You are receiving this mail because:
You are on the CC list for the bug.