Mount points changing with reboots after last updates

[Dean Moreton]

Been running Hardy for weeks without this prob but pulled down lots of updates tonight which I'm pretty sure had a kernel update. Running 2.6.24-14-generic #1 SMP Thu Apr 3 04:49:29 UTC 2008 i686 GNU/Linux

Seems my partition mount points are duplicating each reboot as I noticed my data partition is mounted to /media/Data__

Reboot before that was /media/Data_ and for the last few weeks was just consistently /media/Data

Seems a user was experiencing the same behaviour in this old bug report in Feisty in bug 101845 but thought I'd open another one since that is over a year old. Please mark as dupe if this was the wrong thing to do.

Heres the relevant output of a mount and ls -l before a reboot

/dev/sda5 on /media/Data__ type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)

lrwxrwxrwx 1 root 999 6 2008-03-24 15:53 cdrom -> cdrom0
drwxr-xr-x 2 root 999 4096 2008-03-24 15:53 cdrom0
drwx------ 2 root root 4096 2008-04-03 20:20 Data
drwx------ 2 root root 4096 2008-04-03 21:08 Data_
drwxrwxrwx 1 root root 4096 2008-04-03 21:18 Data__
lrwxrwxrwx 1 root 999 7 2008-03-24 15:54 floppy -> floppy0
drwxr-xr-x 2 root 999 4096 2008-03-24 15:54 floppy0

and after a reboot

/dev/sda5 on /media/Data___ type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)

total 24
lrwxrwxrwx 1 root 999 6 2008-03-24 15:53 cdrom -> cdrom0
drwxr-xr-x 2 root 999 4096 2008-03-24 15:53 cdrom0
drwx------ 2 root root 4096 2008-04-03 20:20 Data
drwx------ 2 root root 4096 2008-04-03 21:08 Data_
drwx------ 2 root root 4096 2008-04-03 21:28 Data__
drwxrwxrwx 1 root root 4096 2008-04-03 21:18 Data___
lrwxrwxrwx 1 root 999 7 2008-03-24 15:54 floppy -> floppy0
drwxr-xr-x 2 root 999 4096 2008-03-24 15:54 floppy0

[Fred (eldmannen+launchpad)]

I have the same problem.

[Tribes (tribes)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 101845, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.