GNOME Bugzilla – Bug 605719
Corrupts HFS+ RAID sets
Last modified: 2012-11-12 21:19:38 UTC
If you attach a multi-disk HFS+ formatted RAID set via an external interface (e.g. USB or Firewire), Gnome (it seems) causes it to be automounted. It is mounted read-write, however only the first member of the RAID set is mounted as if it were a single-disk HFS+ filesystem. The member is then over-written and the whole set becomes unreadable / unmountable on a Mac machine. Disabling all the automount options in "File Management Preferences" appears to have no effect: automounting continues.
I fail to see how this is related to the servers maintained by GNOME. --> nautilus
Apologies if I have misdirected this bug report. Do you know who maintains the automounter so I can report it to them? I have set all my settings in "File Management Preferences" not to automount any externally mounted media, with no effect.
Which exact distribution and version is this about? Also see https://bugzilla.gnome.org/page.cgi?id=bug-writing.html
Fedora 12 (Constantine) Kernel Linux 2.6.31.9-174.fc12.i686 GNOME 2.28.0 I had set up the System->Preferences->File Management->Media: Never prompt or start programs on media insertion. The auto-mounting continued. I have now disabled auto-mounting by executing gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set /apps/nautilus/preferences/media_automount false Perhaps this functionality is as intended. However, I had understood the GUI as meaning it would disable auto-mounting. I would have found it useful if it was easier to disable automounting (e.g. either for the above checkbox to do so, or for there to be another checkbox to do the same, or at least for the command line version to be documented better - I struggled to find out how to do it). Re. filesystem corruption it seems that the disk has 2 bad sectors which it must have developed immediately after I disconnected it from my Linux box (since SMART reported 0 bad sectors at the time it was connected to it). Very strange timing. So that's perhaps the reason Apple won't mount it any more. I've been able to stitch the two disks together manually using dmsetup on Linux and get the data off.
tom10256@hotmail.com, if I understand you correctly what you'd like is a checkbox to enable/disable automounting in the Media tab of "File Management Preferences" window. Cosimoc, good or bad idea? If good, any suggestion for wording?
(In reply to comment #5) > tom10256@hotmail.com, if I understand you correctly what you'd like is a > checkbox to enable/disable automounting in the Media tab of "File Management > Preferences" window. > > Cosimoc, good or bad idea? If good, any suggestion for wording? I think this is a bad idea, and we should try to fix the real bug (the one described in comment #0) at the right level of the platform. Let's move this down to gnome-disk-utility for now.
The way to fix this is to teach libblkid about it so it doesn't cause udev/systemd to set ID_FS_USAGE to "filesystem". So this is a libblkid / util-linux bug, please file it there. Thanks. Thanks for taking the time to report this bug. However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome. If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other. Thanks in advance!