[Techtalk] NFS mounted dir - strange behavior
alwanza at oz.net
Mon Sep 10 16:34:25 UTC 2007
One more detail: both Linux1 and Solaris1 get their logins from a 3rd
server through NIS. So logins on both boxes have the same authentication.
From: Meryll Larkin [mailto:alwanza at oz.net]
Sent: Monday, September 10, 2007 9:26 AM
Subject: NFS mounted dir - strange behavior
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.
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?
More information about the Techtalk