Bug 198317

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).