Shell Programming and Scripting

Reading MadeInGermany's post#5 I can see that he has a different perception of this problem than Jim and I.

So, questions:

Are both node 1 and node 2 both mounting the filesystem(s) on the NAS via NFS???

What type of NAS is this? Make/model?

Is this NAS intelligent enough to share NFS handles for filesystems AND control all file locking, file read/write, and file contention? If so, the NAS is itself acting as node 1 and your Solaris 9 machines are NFS clients node 2 and node 3, both mounting via NFS which is okay.

Question then is: When the filesystem(s) need checking/correcting, how is that done? Is the NAS capable of creating and formatting filesystem(s) itself, and running integrity checks?

Sorry for all the questions but MadeInGermany's post#5 has got me thinking that Jim and I have perhaps not comprehended the problem from your post#1 due to lack of detail.

Awaiting answers........

Thanks- I checked machine 1 only (since I have 2 shut down right now)

Code:

/etc/mttab

shows nfs for the NAS mounts.

Its an Iomega StorCenter ix4-200d

I don't know if its intelligent enough to share handles, but I can say, that most users uids on machine 2 had already been made to match those of machine 1. I create accounts locally on each machine.

I know I can log in to the NAS via a browser and create shares and typically, users generally create directories from the windows machines.

Does this help?

------ Post updated at 10:02 AM ------

Even though I moved the files off of Box 1 and on to the NAS?

Physically mounted? Box 1, Box 2, and the NAS are all connected through the switch. Box 1 and box 2 mount the NAS in exactly the same way as far as I can tell.

Does this change anything?

How are filesystems from the former server which acted like a NAS exported ?
Is the same or similar configuration used during export from new NAS storage ?
Are some firewalls (ipfilter, ipnat) localy configured on solaris boxes (or any other clients to former solaris NAS box ) ?

Can you show output from following commands, issued from one of the solaris boxes.

Code:

showmount -e <your working acting NAS solaris box which you wish to migrate>
showmount -e <your NAS storage ip address>

When NAS storage is up, does it work on other operating systems like centos, or exhibits the similar behavior as on solaris boxes ?

What is the actual error when user tries to, for instance, ssh to a box ?

In most cases, for home directories automount is used on Solaris.

This is a nice article about automount :
Less known Solaris Features: /export/home? /home? autofs? - c0t0d0s0.org

Regards
Peasant.

Your post#9 confirmed that my assumption in post#5 is right, and you should try my suggestion in post#3 to alter file ownership.
I forgot to mention that the "chown" requires "root=" permission on the NAS box (in the NFS exports), otherwise it will fail with error "Not owner".

So,

To change user jsmith from being user 67123 to 1012:

Code:

usermod -u 1012 jsmith
  find /home/jsmith -user 67123 -exec chown -h 1012 {} +

I think I like this (find) one because it sounds completely reversible to me.

If I were to do a recursive change, if files and directories owned by someone else happen to be in there, they would get changed, but then I would never know how to change back, not knowing who they had belonged to.
What does {} + do?

While {} \; runs a chmod for each file, the {} + collects the filenames and, when long enough, runs a chmod with the collected argument list.
Fewer invocations of chmod => greater speed.

Just to confirm- is this the best way to change someone's uid? (what I said in #12) I don't want to break the account.