mysterious directory

[kray]

I have disks mounted under /Volumes with the following names:

disk0
disk1
disk2

The other day I noticed a forth disk (beats the heck out of me where it came from) with the name disk1 1

Here is the output of ls -la:

truffula:/Volumes admin$ ls -la
total 8
drwxrwxrwt 6 root admin 204 Jul 19 14:00 .
drwxrwxr-t 34 root admin 1258 Jul 18 10:28 ..
lrwxr-xr-x 1 root admin 1 Jul 18 10:28 disk0 -> /
drwxr-xr-x 3 admin staff 102 Jul 14 10:31 disk1
drwxr-xr-x 14 admin staff 510 Jul 15 09:17 disk1 1
drwxr-xr-x 16 admin staff 578 Jul 8 09:33 disk2

I can’t seem to be able to ‘cd’into it, or run a ‘du’ or ‘df’ on it.

Any one ever seen this before? btw, I’m running 10.4.2 Server.

[Ross]

I have seen this when a drive doesn’t mount that contains User Home Directories and someone tires to login. It will create a new directory in /Volumes and start putting the home directories in there.

So if your Home directory share was /Raid/Users/

And your RAID was not mounted and a user tried to login, it would create a folder in your Volumes called RAID and start storing the home directory in there. When you RAID volume comes backup its renamed RAID 1.

You have to delete the directory In Volumes and reboot… Then you should be back to normal. Of course if its been like this a while you may have many user files in there. I have seen clients use this for months before realizing it.

[kray]

You’re right it. I traced the trouble down to a portable home directory issue. Now how to fix it?

It looks like the trouble is that disk1 is mounted on /Volumes/disk1 1, instead of /Volumes/disk1 (where is should be).

I can actually cd into /Volumes/disk1 and see that all the files are there. However, opening disk1 in the finder indicates that the directory is empty. I

[Ross]

Go to folder “/Volumes/”

Just move the directory that is a folder (not sure what its called on your box) out of the “/Volumes”…. then reboot the server. The server will fix itself… on boot it will change (volumename 1) back to (volumename).

Then figure out what files need to be migrated from the directory you just moved.

[kray]

Here is the directory structure in /Volumes:

truffula:/Volumes admin$ ls -l
total 8
lrwxr-xr-x 1 root admin 1 Jul 25 09:27 disk0 -> /
drwx—— 3 admin admin 102 Jul 25 09:26 disk1
drwxr-xr-x 3 admin staff 136 Jul 25 09:33 disk1 1
drwxr-xr-x 16 admin staff 578 Jul 21 14:31 disk2

If I try and move the directory disk1 1, I get a message that says “cannot reneme a mount point”. If I try and delete it with rm, I get a message that says “resource bussey”

If I try and use the finder to move the directory disk1\ 1, it says I don’t have sufficient previlages, even if I log in as root.

What the heck is going on here?

[Ross]

Disk1 1 is the right one… You don’t want to delete that. Read my post again… What happens a directory gets created in Volumes (Disk1) then when your volume comes up it gets renamed (disk1 1) If you remove (just move) (disk1) which should be a directory and reboot it will automatically get named back to disk1.

[kray]

ahhh… I missunderstood your post. I got rid of disk1, rebooted and your were right, disk1 1 came back up as disk1. Now however, I find that Disk Utility can not unmount disk1.

on the command line, ‘mount’ shows:
truffula:~ admin$ mount
/dev/disk1s9 on / (local, journaled)
devfs on /dev (local)
fdesc on /dev (union)
on /.vol
automount -nsl [180] on /Network (automounted)
automount -fstab [229] on /automount/Servers (automounted)
automount -static [229] on /automount/static (automounted)
/dev/disk0s9 on /Volumes/disk1 (local)
/dev/disk2s6 on /Volumes/disk2 (local)
truffula:~ admin$

Correct me if I’m wrong, but it appears that disk1 does not have it’s own mount point, even though Disk Utility shows disk1 to be mounted on /Volumes/disk1.

Any ideas what I’ve messed up now?

[Author]

Posts