Description of problem: Sometimes I see two different partitions on the same external IEEE1394 [Firewire] harddrive get automounted on the same mount point: ----- $ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda12 8123168 3877696 3826180 51% / tmpfs 517748 0 517748 0% /dev/shm /dev/sda2 288198304 90500516 194769864 32% /media/disk /dev/sda1 288198304 90500516 194769864 32% /media/disk ----- Notice that /media/disk is both /dev/sda2 and /dev/sda1. (When I see this, then I turn off the power on the external drive, to try to avoid scrambled filesystems.) Version-Release number of selected component (if applicable): udev-084-13 nautilus-2.14.1-1.fc5.1 gnome-desktop-2.14.2-1 initscripts-8.31.5-1 kernel-2.6.17-1.2145_FC5 How reproducible: always Steps to Reproduce: 1. boot system, attach external 1394 [Firewire] harddrive with 2 ext3 partitions 2. turn on harddrive, wait for automounting 3. Actual results: /dev/sda2 288198304 90500516 194769864 32% /media/disk /dev/sda1 288198304 90500516 194769864 32% /media/disk Expected results: /dev/sda1 288198304 90500516 194769864 32% /media/disk /dev/sda2 116661 4173 111284 4% /media/disk-1 Additional info: The external harddrive also has a USB-2.0 interface. If I boot the system, attach the external harddrive via the USB-2.0 interface, then the two partitions get mounted correctly on distinct mount points. Then, I can unmount both partitions, turn off the harddrive, disconnect the USB-2.0 cable, connect the 1394 cable, turn on the harddrive, and see both partitions mounted correctly on distinct mount points. So there is something special about getting automounted for the first time after boot using the 1394 interface. I will attach portions of /var/log/messages for both failure (mounted first by 1394 after boot) and for success (mounted first by USB-2.0, then by 1394).
Created attachment 132215 [details] /var/log/messages for failure boot system, connect harddrive via IEEE-1394 interface, turn on harddrive, wait for automounting.
Created attachment 132216 [details] /var/log/messages for success boot system, connect external harddrive via USB-2.0 interface, turn on harddrive, wait for automounting; verify distinct mount points for the two partitions. unmount both partitions manually, turn off harddrive, disconnect USB-2.0 cable, connect IEEE-1394 cable, turn on harddrive, wait for automounting; verify distinct mount points for the two partitions.
Created attachment 132217 [details] lspci output: plain, -n, -v /sbin/lspci; /sbin/lspci -n; /sbin/lspci -v
hal-0.5.7-3.fc5.2 avahi-0.6.10-1.FC5 dbus-0.61-3.fc5.1
udev does not automount
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This problem has disappeared; I do not see it in Fedora 9 Beta.