[Techtalk] NFS mounted dir - strange behavior
shirrell at pstat.com
Tue Sep 11 02:09:45 UTC 2007
Meryll Larkin wrote:
> I'd like to describe what is happening and then ask why.
> I have 2 *nix boxes, one is solaris (client), one linux (host).
> Linux1:/r1 is mounted onto
> so that Solaris1 (which has insufficient hard drive space and can't be
> upgraded for reasons outside this topic) can make use of the space on Linux1
> for extra file storage. The reason behind mounting it is for the ease of a
> cron job which copies and moves files from a directory on Solaris1 to
> I had been having difficulty with copying and deleting files on the mounted
> dir from a cron job running on Solaris1.
we have 4 solaris boxes in an NFS network with 2 PC's running Linux and
XP. Samba works fine moving things between solaris and Linux or XP. We
have had trouble with permissions when copying files from one Solaris box
to another as a low level backup and then trying to see or to restore them.
There seems to be a difference between me as a user on box1 and me as a user on
box2 even though the NFS master server serves for both box1 and box2.
This has been most apparent with files that were created with read permission
for the owner only. To change permissions for such a file seems to require
that the user be logged onto the originating computer or, if that computer no
longer exists, su on the nfs master may be required.
I too would like to know just what these hierarchical rules are.
shirrell at pstat.com
> When I investigated further, I discovered that when logged in as myself (as
> a user and not as root) I could cd into /r1/twodeep/threedeep/ but not into
> /r1/twodeep/threedeep/fourdeep. I was logged into Solaris1. I could ls in
> /r1/twodeep/threedeep/ and see fourdeep, but when I tried to cd into it I
> got a message that there was "no such file or directory" (not a spelling
> problem). As root on Solaris1, I didn't have this trouble. As myself on
> Linux1 I didn't have this problem. All directories on the mount path have
> 777 permissions (all open).
> Well, if I guessed correctly, what I did was created mkdir the fourdeep dir
> when I was logged in as root on Linux1.
> I think this is why I was having trouble with the crons. I'll know in a
> week because I've remade the dir from Solaris1. Can anyone explain this
> behavior to me?
> Meryll Larkin
> Techtalk mailing list
> Techtalk at linuxchix.org
More information about the Techtalk