Automounted Volumes mount points change

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still and issue for you? Thanks in advance.

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

I reopened this bugs because there were 3 duplicates.

And now we need the output from: gnome-mount -vnbtd /dev/sdXX (replace XX with the character and the number of your partition)

Requested output (after first unmounting the partition; only difference otherwise is an error message at the end stating device is already mounted):

$ gnome-mount -vnbtd /dev/sde1
gnome-mount 0.8
** (gnome-mount:7011): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2
** (gnome-mount:7011): DEBUG: read default option 'locale=' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:7011): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:7011): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2 with mount_point='Data', fstype='ntfs-3g', num_options=2
** (gnome-mount:7011): DEBUG: option='locale=en_US.UTF-8'
** (gnome-mount:7011): DEBUG: option='exec'
Mounted /dev/sde1 at "/media/Data"

A few things I'd like to add:

- Currently running fully updated 8.04 Beta with 2.6.24-14-generic kernel
- Don't think issue is related to kernel since it's been around for a long time and I now have the same issue booting 2.6.24-12-generic
- Issue did not occur with this install of Hardy Beta until recently (1-2 days ago); possibly broken in an update?
- Issue does not occur when I _manually_ unmount the partition; be it via GUI or commandline
- Issue occurs only when I reboot and the partitions should be unmounted automatically

That looks good. Now, could you please provide the output of the same command when an underscore is appended?

Alright, this is a bit funky. First of all, contents of /media before the reboot (I had manually cleaned it up to look the way it should since it was full of junk directories from previous mount points):

---
$ cd /media
$ ls -l
total 44
drwxrwxrwx 1 root root 8192 2008-03-27 20:12 Archive
lrwxrwxrwx 1 root 999 6 2008-03-29 06:15 cdrom -> cdrom0
drwxr-xr-x 2 root 999 4096 2008-03-29 06:15 cdrom0
drwxrwxrwx 1 root root 16384 2008-03-27 20:12 Data
drwx------ 4 user root 16384 1970-01-01 01:00 disk
drwxr-xr-x 5 user user 104 2008-02-25 17:42 disk-1
---

And now after the reboot:

---
$ ls -l
total 60
drwx------ 2 root root 4096 2008-04-04 21:02 Archive
drwxrwxrwx 1 root root 8192 2008-03-27 20:12 Archive_
lrwxrwxrwx 1 root 999 6 2008-03-29 06:15 cdrom -> cdrom0
drwxr-xr-x 2 root 999 4096 2008-03-29 06:15 cdrom0
drwx------ 2 root root 4096 2008-04-04 21:48 Data
drwxrwxrwx 1 root root 16384 2008-03-27 20:12 Data_
drwx------ 2 root root 4096 2008-04-04 20:48 disk
drwx------ 2 root root 4096 2008-04-04 20:48 disk-1
drwx------ 4 user root 16384 1970-01-01 01:00 disk-2
drwxr-xr-x 5 user user 104 2008-02-25 17:42 disk-3
---

As you can see the old directories from the last session are still there, albeit with changed permissions/ownership, unaccessible to the normal user and with nothing mounted to them. The ones now mounted are Archive_, Data_, disk-2 and disk-3. These are the symptoms of this bug that I initially encountered / was aware of.

Now, trying to run the same gnome-mount command from last time revealed this:

---
$ gnome-mount -vnbtd /dev/sde1
gnome-mount 0.8
** Message: Given device '/dev/sde1' is not a volume or a drive.
---

Weird. fdisk further reveals:

---
$ fdisk -l

Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00013b82

   Device Boot Start End Blocks Id System
/dev/sdc1 1 18156 145838038+ 7 HPFS/NTFS
/dev/sdc2 18157 19456 10442250 f W95 Ext'd (LBA)
/dev/sdc5 18157 19456 10442218+ 4 FAT16 <32M

Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8d399bc0

   Device Boot Start End Blocks Id System
/dev/sdd1 1 54235 435642606 7 HPFS/NTFS
/dev/sdd2 54236 60801 52741395 b W95 FAT32
---

What used to be /dev/sdE1 is now /dev/sdC1 (along with changes to all other device names).

Running gnome-mount on the new device name shows this:

---
$ gnome-mount -vnbtd /dev/sdc1
gnome-mount 0.8
** (gnome-mount:6766): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2
** (gnome-mount:6766): DEBUG: read default option 'locale=' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:6766): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:6766): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2 wit...

It's perfectly alright this way. The problem is that we need the output of an attempt to mount the volume to the *wrong* directory. So please do a "sudo umount /media/Data" and then re-run the command.

fdisk after another reboot:

---
$ fdisk -l

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8d399bc0

   Device Boot Start End Blocks Id System
/dev/sdc1 1 54235 435642606 7 HPFS/NTFS
/dev/sdc2 54236 60801 52741395 b W95 FAT32

Disk /dev/sde: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00013b82

   Device Boot Start End Blocks Id System
/dev/sde1 1 18156 145838038+ 7 HPFS/NTFS
/dev/sde2 18157 19456 10442250 f W95 Ext'd (LBA)
/dev/sde5 18157 19456 10442218+ 4 FAT16 <32M
---

That partition changed back to /dev/sdE1. This isn't normal behavior, is it? I never noticed device names changing like that...

And, of course, /media now contains the "dead" mount points from the last two sessions as well as the new, once again changed, ones:

---
$ cd /media
$ ls -l
total 76
drwx------ 2 root root 4096 2008-04-04 21:02 Archive
drwx------ 2 root root 4096 2008-04-04 22:27 Archive_
drwxrwxrwx 1 root root 8192 2008-03-27 20:12 Archive__
lrwxrwxrwx 1 root 999 6 2008-03-29 06:15 cdrom -> cdrom0
drwxr-xr-x 2 root 999 4096 2008-03-29 06:15 cdrom0
drwx------ 2 root root 4096 2008-04-04 21:48 Data
drwx------ 2 root root 4096 2008-04-04 22:27 Data_
drwxrwxrwx 1 root root 16384 2008-03-27 20:12 Data__
drwx------ 2 root root 4096 2008-04-04 20:48 disk
drwx------ 2 root root 4096 2008-04-04 20:48 disk-1
drwx------ 2 root root 4096 2008-04-04 22:27 disk-2
drwx------ 2 root root 4096 2008-04-04 22:27 disk-3
drwx------ 4 user root 16384 1970-01-01 01:00 disk-4
drwxr-xr-x 5 user user 104 2008-02-25 17:42 disk-5
---

Also weird is the difference in ownerships/permissions of the four partitions. The real ones here are:

drwxrwxrwx 1 root root 8192 2008-03-27 20:12 Archive__
drwxrwxrwx 1 root root 16384 2008-03-27 20:12 Data__
drwx------ 4 user root 16384 1970-01-01 01:00 disk-4
drwxr-xr-x 5 user user 104 2008-02-25 17:42 disk-5

They map to /dev/sdc1, /dev/sde1, /dev/sdc2 and /dev/sde5 respectively in the above fdisk output. Note how some are owned by root and others by the user, as well as the very different permissions. Is this normal?

>So please do a "sudo umount /media/Data" and then re-run the command.

Well, there's nothing mounted to that directory, it's just dead/empty. As if it was unmounted but the directory remained. The partition is now mounted to Data__. So I'm not sure what exactly you mean...

Attempt to umount anyway:

$ sudo umount /media/Data
umount: /media/Data: not mounted

Attempt to mount to /media/Data via gnome-mount:

$ gnome-mount -vnbtd /dev/sde1 -m Data
gnome-mount 0.8
** (gnome-mount:6627): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2
** (gnome-mount:6627): DEBUG: read default option 'locale=' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:6627): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:6627): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2 with mount_point='Data', fstype='ntfs-3g', num_options=2
** (gnome-mount:6627): DEBUG: option='locale=en_US.UTF-8'
** (gnome-mount:6627): DEBUG: option='exec'
** Message: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2
org.freedesktop.Hal.Device.Volume.AlreadyMounted : Device /dev/sde1 is already mounted.

Attempt to umount /media/Data__ and gnome-mount to Data:

$ sudo umount /media/Data__
$ gnome-mount -vnbtd /dev/sde1 -m Data
gnome-mount 0.8
** (gnome-mount:6644): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2
** (gnome-mount:6644): DEBUG: read default option 'locale=' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:6644): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options
** (gnome-mount:6644): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2 with mount_point='Data', fstype='ntfs-3g', num_options=2
** (gnome-mount:6644): DEBUG: option='locale=en_US.UTF-8'
** (gnome-mount:6644): DEBUG: option='exec'
** Message: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2
org.freedesktop.Hal.Device.Volume.MountPointNotAvailable : The mount point '/media/Data' is already occupied

** Message: Given mount point name 'Data' is unavailable, trying with 'Data_'...
** (gnome-mount:6644): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2 with mount_point='Data_', fstype='ntfs-3g', num_options=2
** (gnome-mount:6644): DEBUG: option='locale=en_US.UTF-8'
** (gnome-mount:6644): DEBUG: option='exec'
** Message: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2
org.freedesktop.Hal.Device.Volume.MountPointNotAvailable : The mount point '/media/Data_' is already occupied

** Message: Given mount point name 'Data_' is unavailable, trying with 'Data__'...
** (gnome-mount:6644): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_F09C547A9C543CF2 with mount_point='Data__', fstype='ntfs-3g', num_options=2
** (gnome-mount:6644): DEBUG: option='locale=en_US.UTF-8'
** (gnome-mount:6644): DEBUG: option='exec'
Mounted /dev/sde1 at "/media/Data__"

Is this last one what you were after...

I confirm that's a problem occuring the last 1 or 2 day's. Having 3 USB Harddrives (around 1 TB of music, photo's and comic books) and 4 reboots later (update and trials) i'm having 12 entry's in the /media folder. The problem is not only the iPod but also Rhythmbox, Amorak, Digikam, MythTV and Comix. They can't find the media files anymore.

I have this problem too...

I too am experiencing the same issue. Anyone know of any workaround/fix?

Can confirm that problem, it is relevant for any program that needs a certain attached drive. My automated backups stopped working as they now try to backup to a drive that doesn't exist or better, is not available for access.

I'll set the packgage to gnome-mount as I think he problem lies there, but I'm not sure. Feel free to change this if you have any objections.

There's a thread about this on ubuntuforums.org: http://ubuntuforums.org/showthread.php?t=744469

I posted a temporary workaround there, it's on page 2.

This is happening for me, but only started when I started using an NTFS drive.

for me, it started with the update on friday (april 4rth), running hardy beta, before it was fine

I have the same problems with Hardy beta as well. Both my external drives, formatted FAT32 and my iPod are creating duplicate entries. I didn't have this problem with Gutsy at all and is now playing havoc with my backups and the syncing of my iPod with Rhythmbox. The only things that seem to be fine are my USB Flash Drives and my USB card reader.

A temporary (windows like :P ) solution I use is:
unmount the drive/partition
delete the wanted folders in /media/
remount partition (or doubleclick the partition icon on left, in nautilus)

On Mon, Apr 7, 2008 at 1:42 PM, richard <email address hidden> wrote:
> I have the same problems with Hardy beta as well. Both my external
> drives, formatted FAT32 and my iPod are creating duplicate entries. I
> didn't have this problem with Gutsy at all and is now playing havoc with
> my backups and the syncing of my iPod with Rhythmbox. The only things
> that seem to be fine are my USB Flash Drives and my USB card reader.
>
>
>
> --
> Automounted Volumes mount points change
> https://bugs.launchpad.net/bugs/101845
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Source Package "gnome-mount" in Ubuntu: Confirmed
>
> Bug description:
> Whenever a removable volume is mounted, then unmounted, the mount point isn't deleted from /media, so when it is mounted again, a directory with a _ appended to the end is created.
>
> My 2 main examples:
>
> When I mount my ipod, it only ended up in /media/ipod the first time. The next time it ended up in /media/ipod_, then the next time /media/ipod__ . This is particularly frustrating because programs, namely gtkpod, look to /media/ipod for it.
>
> Same behavior when I mount and unmount my portable drive called "xbox". First it ends up in /media/xbox, then /media/xbox_ , etc.
>
> I can manually fix this by temporarily unmounting the device, deleting the directory, and remounting, but what fun is that?
>
> Using Feisty with all updates as of 4/2
>

--
e-mail: <email address hidden> | msn: <email address hidden>

I would delete them if I could but every time I try and do it using the following from with in the media dir the system just hangs and i have to hard reboot.

sudo rmdir EXTERNAL_

try sudo nautilus

On Mon, Apr 7, 2008 at 3:38 PM, richard <email address hidden> wrote:
> I would delete them if I could but every time I try and do it using the
> following from with in the media dir the system just hangs and i have to
> hard reboot.
>
> sudo rmdir EXTERNAL_
>
> --
>
>
> Automounted Volumes mount points change
> https://bugs.launchpad.net/bugs/101845
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Source Package "gnome-mount" in Ubuntu: Confirmed
>
> Bug description:
> Whenever a removable volume is mounted, then unmounted, the mount point isn't deleted from /media, so when it is mounted again, a directory with a _ appended to the end is created.
>
> My 2 main examples:
>
> When I mount my ipod, it only ended up in /media/ipod the first time. The next time it ended up in /media/ipod_, then the next time /media/ipod__ . This is particularly frustrating because programs, namely gtkpod, look to /media/ipod for it.
>
> Same behavior when I mount and unmount my portable drive called "xbox". First it ends up in /media/xbox, then /media/xbox_ , etc.
>
> I can manually fix this by temporarily unmounting the device, deleting the directory, and remounting, but what fun is that?
>
> Using Feisty with all updates as of 4/2
>

--
e-mail: <email address hidden> | msn: <email address hidden>

I used the releases of Feisty and Gutsy happily for a while without this bug, but I installed the latest release of Hardy with all the updates current as of today (4/7/08), and the problem has returned.

It's a Fat32 external HD, still called "Xbox", and I am now getting the same Xbox_, Xbox__, etc.

I know I can delete them and have it return to the same mount point as before, but it's frustrating/annoying none the less. And for programs like gtkpod that look for an absolute path, it can be especially frustrating to have delete the folder, unmount and remount your iPod, just because gnome-mount isn't working properly.

Even though I didn't respond initially, thanks for following up recently. It's good to know someone reads these things.

Same problem for me.
I don't remember when this started, but today with last updates I have the same behavior

merlos@merlos-lap:~$ ls -l /media/
[...]
drwx------ 2 root root 4096 2008-04-07 10:02 merlos
drwx------ 2 root root 4096 2008-04-07 11:06 merlos_
drwx------ 2 root root 4096 2008-04-08 09:03 merlos__
drwx------ 2 root root 4096 2008-04-08 09:53 merlos___
drwx------ 17 merlos root 16384 1970-01-01 01:00 merlos____
[...]
merlos@merlos-lap:~$ uname -a
Linux merlos-lap 2.6.24-15-generic #1 SMP Tue Apr 8 00:33:51 UTC 2008 i686 GNU/Linux
merlos@merlos-lap:~$

I have this problem with USB drives, but also with local harddrives not in /etc/fstab. They are remounted as /media/disk-1, /media/disk-2, etc. whenever I select them from the Places menu.

I also am experiencing this problem with an ntfs drive, a fat drive and even with usb drives, first it is drive, then drive_, then drive__ and so on.

I am also experiencing this with a ntfs partition and a fat32 external HD

I'm pretty sure this got better with today's updates, and I can't reproduce it by mounting/unmounting the USB drive.

But it's still not deleting the mount points on system shutdown. So every time I restart with a USB drive mounted, it's mounted at a different mount point after boot.

I'll look at this ASAP.

I did the morning updates.
The problem is still here :(

>and I can't reproduce it by mounting/unmounting the USB drive.

You have to reboot whit your drive attached to reproduce this bug; I noticed that when you mount and umount by hand everything is ok

This particular problem struck me this morning when I updated the computer (morning as in GMT+1). I didn't have the problem before, but had heard of others having it. I did however lack write properties to my external hard drive and I have posted a bug report about it here: https://bugs.launchpad.net/ubuntu/+bug/214615

That problem still remain after the update, but this problem appeared first this morning.

confirming: with latest updates as of now, manually (using disk mount applet) unmounting devices removes mountpoints, but rebooting while devices are mounted does not, duplicate /media/disk___ type entries are created.

This is due to hal not reusing empty directories in /media as mountpoints. See bug 95368, which is a duplicate of all of those.

Confirming on an updated gutsy computer..

When I mount my usb disk during bootup it creates multiple directories as below

/media/crucial
/media/crucial_
/media/crucial__

and the drive is mounted at: /media/crucial__

TIA

Bhavani Shankar.

I can also confirm the same problem as listed above on i386 Gutsy install on a Toshiba Satellite.

Hardy, not Gutsy. Sorry. Too many animals. Heron, not Gibbon!

Please note that launchpad ist not a forum; the bug is marked as "in progress", so it will propably be fixed in hardy soon, there is no need to re-confirm it again. Thanks.

I reverted the sysvinit change which caused this bug. To clean this up locally on your system, please remove empty unused mount points in /media manually (no way to do it automatically in a safe fashion, sorry).

Package uploaded, awaiting RM approval.

This bug was fixed in the package sysvinit - 2.86.ds1-14.1ubuntu44

---------------
sysvinit (2.86.ds1-14.1ubuntu44) hardy; urgency=low

  * debian/initscripts/etc/init.d/mtab.sh: Revert previous change of cleaning
    /media/.hal-mtab, since hal does not (and cannot easily) remove mount
    point directories on shutdown, but also considers already existing mount
    points as not usable for dynamic mounts (since they potentially conflict
    with fstab). Patching hal properly is too intrusive at this point.
    (LP: #101845, LP: #95368)

 -- Martin Pitt <email address hidden> Mon, 14 Apr 2008 11:53:21 +0200

Sysvinit is not installed by default? I have Upstart instead. is that ok?

if i install sysvinit , this package removes a lot of importants packages ( ubuntu-minimal , upstart, upstart-compat-sysv, startup-tasks, friendly-revovery, system-services, upstart-logd ..)

should i accept this ? is it safe ?

As far as I can tell, sysvinit does not need to be installed to grab the update as other sysv packages are already installed and subsequently updated.

Thank you - it seems to be fixed now! I didn't installed the binary package "sysvinit".

tech0007 [2008-04-14 17:53 -0000]:
> Sysvinit is not installed by default? I have Upstart instead. is that
> ok?

Sysvinit is the source package. The affected script is in package
'initscripts'.

Hello, I've updated both the sysvinit and initscripts packages via synaptic, and am running a fully updated version of hardy 8.04, yet am still having this problem. Any advice would be appreciated.

I can confirm with last updades the problem is solved

Tks a lot :)

I can also confirm this problem fixed. THIS: (https://bugs.launchpad.net/ubuntu/+bug/214615) problem still remain though which is quite irritating.

I can confirm this problem fixed. ;)

I installed the Release Candidate on a new hard drive. The mount points were detected wrong for the cd drives in fstab and the cd's were then mounted to /media/CdTitle. I changed the cd lines in fstab from
/dev/scd0
/dev/scd1
to
/dev/hdc
/dev/hdd
and the cd's are now mounted to /media/cdrom and /media/cdrom1

I'm still experiencing this bug exactly as described, despite having current updates.

You can reboot with all 'problem' devices disconnected, and then with

>sudo nautilus

delete all references to these devices in /media/

if some wo'nt get deleted, delete the others and reboot again. and then delete the remaining

Then connect the devices again, and all should be well...

I did just that, except I used terminal for delete. Had no extra folders in media. First time after reboot it mounted nicely, but after first hibernate/resume Dolphin tells me that mount point is already occupied. I have it set to mount my device to a certain place every time. Having current updates for Kubuntu 8.04 and no Sysvinit.

I had the same problem for a long time. For me it was not necessarily happening for USB devices, but I did find that IDE and SATA hard disks were doing this. Eventually I found that I had manually updated the /etc/fstab file incorrectly. The entry I had that was causing the problem was:

/dev/sdb1 /media/Backup/ ntfs-3g defaults,locale=en_US.UTF-8 0 0

but the correct line should be:

/dev/sdb1 /media/Backup ntfs-3g defaults,locale=en_US.UTF-8 0 0

I had an extra slash on the end of the mount directory!

Hope this helps someone.

I realize this thread/report is a little old but it's closest thing I can find to a resolution of this issue. I am experiencing this exact problem of a new mount folder being generated with an underscore(_) appended for my external USB NTFS drive. I think it happens after unplanned power cycles. My machine is headless and the power in my area is flaky. I have a UPS but that doesn't help. I recently installed Xubuntu 9.04 but the problem did not go away it was present with the previous release.
The Launnchpad documentation seems to indicate that this is fixed but it's unclear what that fix is and how I should get it. Any assistance or re-direction gratefully recieved.

Like dcwandj, I've just been hit with this problem and I'm using the latest Ubuntu 9.1 (2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010). It may or may not be relevant that the problem appeared shortly after I had a system crash.

I also started seeing this recently again with 10.04. Wish I could remember what update triggered it though.

I'm also now having this problem with 10.10. One thing to note is that this did not happen with an "older" drive. I used to have an 80gb drive attached. Now I have a 1.5tb drive attached. I've only had this issue with the 1.5tb drive. If I can provide anything that might be helpful in diagnosing, please let me know.

I'm also seeing this problem in 10.10. I use a 400GB Western Digital USB drive (ATA WDC WD5000AAKS-65YGA0 with firmware 12.01C20, according to Disk Utility) for my backups. It is formatted as ext4v1.0 . I use LuckyBackup (a front end to rsync) to perform nightly / weekly / monthly backpus via a cron job (set up by LuckyBackup.)

The volume is named "backups" and is normally mounted under /media as /media/backups. I have noticed that when my machine is restored from hibernation (I mostly hibernate my machine following a backup), the USB drive is mounted under /media/backups_ . If I do not catch the backup operation in time, the backup will be performed under /media/backups - with /media/backups now being a directory under the main partition of my PC's HDD.

I have a few backups being made to the wrong place as a result with my primary HDD nearing full capacity at times and totally messing up my backup regime.