NTFS local mount of remote drives problem

[Mark Stewart]

Hello! I have about 4 drives that are basically shared between machines on a small LAN. Each workstation has one drive and it is connected to the other machines via NTFS. Well, a couple days ago the power went down and came back on (graceful shutdowns occured), but one one of the workstations came back up the mount of the remote drive was messed up. Instead of it being mounted and appearing as a directory, it is showing up as a link that links to nothing. The ls -l looks as follows:

lrwxrwxrwx 1 root root 20 Jul 30 10:22 ads1
lrwxrwxrwx 1 root root 20 Jul 30 10:22 j6000_data

My question is, how do I remove this broken link? unlink /ads1 says the device is busy, and of course it can't be unmounted because it's not showing up as a mounted disk. Any help? Thanks!

[Massimo Bianchi]

Hi,
i think that before removing the link you have to shudown all nfs related services:
/sbin/init.d/nfs.client stop

Massimo

[doug mielke]

I'm assuming you mean NFS.
If you
bdf
You'll see the mounted drives on the client
servername:/volname /filesystemname.
the link could just be how that directory appears when there is no mount.
You can safly try mountall, in case the NFS mounts have been automated.

If you umount /filesystemname , it should give a descriptive message abouint the states.

If busy, make sure you are not in that dir, or it's link.
then try fuser dirname to see what processes are using it.

[Brian Bergstrand · Accepted solution]

I've seen this exact same error occur before when using automount. Are you using automount? The drive would be mounted under /tmp_mnt, but the link automount created on the actual mount point would point to nothing. I could never figure out the cause, so I just turned automount off and switched to a static mount. No problem since.