Shell Programming and Scripting

Yes, okay, got that, but I think you've lost me now.

So what exactly isn't working? Can you mount this NFS handle on /mnt?

If so,

Code:

# cd /mnt
# ls

should show you the contents of the share directory on the NAS.

Where are we up to now?

I was talking about the machine I'm cloning, not the clone. I was asking if perhaps the

Code:

<NAS_Name>

it has is the handle, (and not

Code:

/mnt/<dir>/<dir>/<dir>/<share>)

)

Is it?

Also, cd /mnt
ls empty on both machines.

Also, I tried to create a directory in

Code:

/mnt

on the clone and I got

Code:

filed to make directory; Read only file system

which didn't sound good.
Thanks!

As previously stated:

Code:

# showmount -e <NAS ip address>

will tell you what NFS handle(s) are available to mount.

Then:

Code:

# mount <NAS ip addr>:<nfs handle> <local mountpoint>

should mount that (remote) NFS handle.

The showmount output should give you the NFS handle exactly as it is (shared).

Is the mount command still giving you access denied? If so, then (1) perhaps that NAS will only accept one connection to one share and the production box already has it mounted (try dismounting it from original system), or (2) the NAS is refusing an inbound connection request from the ip address you are using on the clone, or (3) another security entry on the NAS needs to be opened up.

So what error if any are you getting when you try to mount?

This shouldn't be difficult; famous last words!

In your post#4 you say that your clone can reach the NAS and mount directories. So what's not working?

Yes, /mnt will be empty on the clone until the mount succeeds.

Sorry I keep bringing up the handle. I thought the

Code:

*

might mean the handle was missing, and that all we were seeing was maybe a path for the handle. Not finding too much info on handles..

Turns out I was misspelling the handle- using an O instead of an 0. So no more permission issue.

But then I was getting an error saying it was busy So I fiddled with it and gave up for the evening.

Tried to reproduce the same issue this morning so I could post it here, and the NAS friggin mounted without issue. The last thing I did yesterday was

Code:

cd a

. Don't know if that did anything.

So I have no idea how that issue went away. I guess it really was super busy.

So now I can see all my NAS files in

Code:

mnt

Most likely cause is......you cannot mount or umount any volume if you are actually on the volume.

So, if you were actually in the /mnt directory, you could not mount something on that mountpoint until you move away from it. As soon as you see 'busy' when mounting or dismounting a volume, that's the first thing you should think of. If you're not on the volume/mountpoint then probably some other user is.

Anyway, very well done!!! You are getting there.