[gutsy] Nautilus "Places" lists mounted RAID mirrors twice

[Emmet Caulfield]

On gutsy/amd64 (2.6.22-14-generic) with dmraid mirror, Nautilus (2.20.0) lists mounted RAID mirrors twice.

This applies equally to "Places" and the main panel when "Computer" is selected.

It seems like Nautilus is violating layering by looking at the underlying block devices in /dev, not finding them
in /etc/mtab and listing them with the RAID filesystem label.

The Nautilus device listing should, at least, be configurable such that these can be suppressed.

[Emmet Caulfield (emmetcaulfield)]

Attached screenshot.

[Pedro Villavicencio (pedro)]

Thanks for your report, does the command "gnomevfs-ls computer:" display the duplicates too? thanks.

[Emmet Caulfield (emmetcaulfield)]

Yes. Output attached.

Any way of suppressing listing devices? I'm not sure I'd want all unmounted devices listed for all users
even if they were correct.

[Emmet Caulfield (emmetcaulfield)]

This has been marked 'incomplete' for 6 weeks after I thought I'd furnished all requested information.

[Sebastien Bacher (seb128)]

There is thousand of desktop bugs and very few people working on those so it can take time. That looks like a gnome-vfs issue, I've no RAID configuration to work on it, letting the bug for somebody which have the issue and want work to work on it

[ecepez (ecepez)]

I am able to reproduce the bug on my machine with a dmraid mirror.
I am running gutsy/i686 (2.6.22-14-generic)
GNOME nautilus 2.20.0

The output of "gnomevfs-ls computer:" also displays the duplicates.

I would be more than happy to work on this bug. Any ideas of where to start?

[Emmet Caulfield (emmetcaulfield)]

The module providing support for the "computer:" URI prefix seem like a possible starting point (http://tinyurl.com/18r). There seems to be some interesting stuff in the daemon, where the lists of drives and volumes seem to be populated (http://tinyurl.com/2244dq). Interesting things to search for are "device_path", "mountpoint" and "HARDDRIVE".

I checked out the source, but haven't had a chance to poke around much. The current maintainer has wanted to completely redesign it for over a year (http://tinyurl.com/hr37y).

[Emmet Caulfield (emmetcaulfield)]

Eek! Substitute http://tinyurl.com/3aftk6 for http://tinyurl.com/18r

[Pedro Villavicencio (pedro)]

is this still an issue with hardy? if so, may you forward this upstream at bugzilla.gnome.org? for instructions on how to do it, please have a look to https://wiki.ubuntu.com/Bugs/Upstream/GNOME ; leaving this as incomplete until getting a response, thanks.

[Emmet Caulfield (emmetcaulfield)]

Yes, it is still an issue with Hardy. I've reported this upstream as per your request:

    http://bugzilla.gnome.org/show_bug.cgi?id=539399

Emmet.

[Sebastien Bacher (seb128)]

hardy is using gvfs and not gnomevfs so you might want open a bug for this one too

[ecepez (ecepez)]

I can also confirm the existence of this bug in Hardy. I have had absolutely no time to poke around the source...

[Gerhard (mail-gbalthasar)]

I have the same problem here. Both drives are shown in places, but are not even mountable. The raid mirror is mounted via fstab in /mnt/raid

Using: Intrepid Ibex Alpha up-to-date

[David Morgado (dcrmorgado)]

Hello I think this problem is not related to gnome-vfs or gvfs or anything of gnome.
The issue here might be related with hal and lvm. Dmraid volumes are not known to hal or lvm so they freak out when they scan your hard disks. In case of raid 1 (mirrors) it makes sense to apear in duplicate, same thing happens to me with Debian Lenny, you basicly have 2 hard disks with the very same layout / partitions, see the pattern here? With raid0 those volume don't even show up but the boot process complains a lot about "seek past the end of the drive" and stuff.

Until hal and lvm start looking at the "dmraid metadata" we have to make them ignore those hard disks part of the dmraid volume, see this:
http://www.redhat.com/archives/ataraid-list/2005-December/msg00011.html
Haven't tested it yet, just looking around and all this occurred to me.

Unless someone has a better idea where to fix this, good luck to us all ;)

[Spoilerhead (spoilerhead)]

also appears in 9.10 for me :(