Version: unspecified (using KDE 4.5.90) OS: Linux Using the new udisks backend in solid, mdraid disks are not showing up in dolphin and open/save dialogs etc. The disks are included in udisks --dump (see below). I do see that udisks isn't picking up volume labels and such (perhaps because it's not partitioned, but has the filesystem directly on the block device?) Is this why solid isn't picking it up? Showing information for /org/freedesktop/UDisks/devices/md0 native-path: /sys/devices/virtual/block/md0 device: 9:0 device-file: /dev/md0 presentation: /dev/md0 detected at: Sat Jan 1 09:41:45 2011 system internal: 1 removable: 0 has media: 1 (detected at Sat Jan 1 09:41:45 2011) detects change: 0 detection by polling: 0 detection inhibitable: 0 detection inhibited: 0 is read only: 0 is mounted: 1 mount paths: /mnt/xyz mounted by uid: 0 presentation hide: 0 presentation nopolicy: 1 presentation name: presentation icon: size: 61442621440 block size: 512 job underway: no usage: type: version: uuid: label: linux md: state: clean RAID level: raid0 uuid: e0463bb4:94709776:983398c7:5db4196b home host: name: num comp: 2 version: 0.90 degraded: 0 sync action: idle slaves: /org/freedesktop/UDisks/devices/sdb5 /org/freedesktop/UDisks/devices/sdc1 drive: vendor: Linux model: Software RAID raid0 revision: 0.90 serial: e0463bb4:94709776:983398c7:5db4196b WWN: detachable: 0 can spindown: 0 rotational media: Yes, unknown rate write-cache: unknown ejectable: 0 adapter: Unknown ports: similar devices: media: compat: interface: virtual if speed: (unknown) ATA SMART: not available Reproducible: Always QT 4.7.1 KDE 4.6 RC1 udisks 1.0.2 HAL *not* installed
I tried partitioning one of my raid volumes. Udisks is picking up the new partition (but still no labels etc), and solid is still ignoring it. So, to summarize: I now have two raid disks: md0 which is partioned, and md1 (not shown here, but is not partitioned - i.e. filesystem is directly on the block device). Solid isn't seeing them. Showing information for /org/freedesktop/UDisks/devices/md0p1 native-path: /sys/devices/virtual/block/md0/md0p1 device: 259:0 device-file: /dev/md0p1 presentation: /dev/md0p1 detected at: Sat Jan 1 14:11:10 2011 system internal: 1 removable: 0 has media: 1 (detected at Sat Jan 1 14:11:10 2011) detects change: 0 detection by polling: 0 detection inhibitable: 0 detection inhibited: 0 is read only: 0 is mounted: 1 mount paths: /mnt/xyz mounted by uid: 0 presentation hide: 0 presentation nopolicy: 1 presentation name: presentation icon: size: 61442619392 block size: 512 job underway: no usage: type: version: uuid: label: partition: part of: /org/freedesktop/UDisks/devices/md0 scheme: mbr number: 1 type: 0x83 flags: boot offset: 2048 alignment offset: 63488 size: 61442619392 label: uuid:
Solid "sees" stuff that not only has partitions but also some kind of filesystem on it. From comment #1 it doesn't look like there's one, ie. "usage" and "type" are empty.
OK, I guess what you're saying is the bug is in udisks? Because there's quite clearly filesystems on them... (I have them mounted, it's just that they're not showing up in solid).
Well, it might be that udisks handles them differently; we'll just have to find out how :) I noticed up in the original text, there is something like "slaves" (/org/freedesktop/UDisks/devices/sdb5 and /org/freedesktop/UDisks/devices/sdc1), could you please post the whole "udisks --dump" together with "solid-hardware details <udi>"? Thx
Created attachment 57648 [details] udisks-dump
Created attachment 57649 [details] solid-details
Created attachment 57775 [details] Solid/udisks RAID patch
Please try the above patch; it would also be nice if you could stop by on IRC (#solid @ Freenode) to discuss this further.
(In reply to comment #8) > Please try the above patch; I'll do that as soon as possible. Unfortunately I'm not likely to have any time for that until later this week. > it would also be nice if you could stop by on IRC > (#solid @ Freenode) to discuss this further. I can do that. I'm assuming I need access to the RAID:ed system though, in which case I won't have any time until later this week. If not, I can pop in almost any time, from work.
(In reply to comment #7) > Created an attachment (id=57775) [details] > Solid/udisks RAID patch It now detects the RAID disks, but they are not listed correctly. * It lists the individual members instead of the RAID disk * It doesn't detect the mount status correctly for the RAID partitioned RAID block device (/dev/md0p1). The non-partitioned RAID block device (i.e. the one where the fiilesystem is directly on the block device, /dev/md1) is correctly detected as mounted. * Since solid lists the individual members, I see two disks pointing to the same mount point for /dev/md1. * Labels are not picked up. I.e. I see two "379.9 GiB Hard Drive", and two "28.6 GiB Hard Drive" entries.
Created attachment 57871 [details] updated solid-details
With udisks-1.0.4, and *without* the patch from comment #7, the correct disks are now detected. I.e. I see one disk for each RAID partition, and I don't see any of the individual members making up the array. So all that is good. However, Solid isn't using any informative labels, and simply lists them as "76.3 GiB Hard Drive". Shouldn't it use the label if there is one (there is)?
Created attachment 63693 [details] udisks --dump from udisks-1.0.4
Created attachment 63694 [details] solid-hardware details for one of the RAID volumes
One more datapoint. With *partitioned* RAID volumes, solid sees the volumes, and uses the volume labels as description (with udisks-1.0.4) In other words, solid now sees filesystems on RAID volumes correctly, except that for filesystems put directly on an unpartitioned RAID disk, solid uses the generic "X GB Hard Drive" as description, instead of the volume label. The reason for this, assuming I read the sources correctly, is that such a filesystem can be seen as both a Solid::DeviceInterface::StorageVolume, and a Solid::DeviceInterface::StorageDrive. The volume label is used as description for StorageVolumes. I'm guessing StorageDrives are assumed not to have a label and hence the generic "X GB Hard Drive" description is used. Finally, when generating the description, it *first* checks if it's a StorageDrive, *then* if it's a StorageVolume. So, for a filesystem put directly on an unpartitioned RAID volume, we get the generic StorageDrive description, whereas filesystems on partitioned RAID volumes aren't seen as StorageDrives and hence we get the label as description. I.e. one way to fix this would be to check (in "QString UDisksDevice::description() const") if it's a StorageVolume *before* checking if it's a StorageDrive. Not sure if this would break something else. Also not sure how common it is to have filesystems on an unpartitioned RAID volume. Hope that made some sense.
Is this still happening with 4.10.1 or 4.9.5 ? What about udisk2 ?
Closing the thread for lack of activity. Please, please! if you are still able to reproduce this with KDE 4.10 or 4.11 feel free to reopen the bug! Oh, if you reopen the bug, please provide: -Check if this still happens with UDisk2 -solid-hardware list (output, with udisk2) Thanks !