Hi,
This should be an easy one but it's got me stumped.
Last week I had to resize the /usr/users partition
on one of the clusters; it's an AdvFS drive mounted
as an ASE NFS service shared between the
two members of the cluster (AS500 and AS800,
running 4.0E/TCR 1.5 pk3). So I made the new
disk, made an AdvFS domain, added to to ASE
as an NFS service, mounted the old and the new
services to temporary mount points and copied the
entire contents from the old to the new (using cp -pR).
Here's where I think I made a boo-boo although
I don't see why it's a problem; I didn't copy from
one NFS service to the other service (i.e., from
/tmpmountpointforolddevice to
/tmpmountpointfornewdevice) but from the
root of the old ASE domain to the root of
the other (i.e. from /usr/var/ase/mnt/oldnfsservice/olddir
to /usr/var/ase/mnt/newnfsservice/newdir).
Is this a bad thing to do?
Boot up the new service and looks dandy; users
can read/write from both hosts and all the files are
there, so i hop in a cab and go home. The next day,
users are happily doing their stuff but I discover
there is a problem; root can't write to the new
service, even though the users can write to their
directories just fine. The ownerships/permissions
are identical to the old service (and to other services
that root can write to). For instance (as root):
# cd /usr/users
# touch newfile
touch: newfile cannot create
The reason I think it's to do with the way I copied
it is that if I go to the ASE domain root I can
write to it.
# cd /usr/var/ase/mnt/newnfsservice/newdir
# touch newfile
[it works!]
#
What have I done and how can I make it OK again
(preferably without dismounting the system/
restarting ASE etc) ?
Thanks! I will summarize
John
Received on Mon Feb 14 2000 - 15:33:43 NZDT