From: Dan Goetzman <dan_goetzman@bmc.com>
To: nfs@lists.sourceforge.net
Subject: NFS "Not a directory" problem
Date: Wed, 31 Jan 2007 15:53:38 -0600 [thread overview]
Message-ID: <45C10FE2.9060606@bmc.com> (raw)
Linux client = 2.6.19-1.2895.fc6
NFS server = Tru64 5.1B-2 (aka 5.1 + PK4)
NFS mount is NFSV3 over UDP or TCP. NFSV2 works OK, NFSV3 has the
following problem;
$ cd /mnt/
$ cd fvance
$ cd src
returns "*Not a directory*" error message.
src is simply a directory under "fvance". Normally a umount/mount cycle
will remove the problem and then all is well.
Turning debug on with "*rpcdebug -m nfs -s all*" and I get the following
in messages;
*When it works;*
> Jan 31 15:30:40 rds-icap kernel: NFS:
> nfs_updatepage(HISTFILES/.sh_history-rds-icap.bmc.com 8@1542)
> Jan 31 15:30:40 rds-icap kernel: NFS: nfs_updatepage returns 0
> (isize 1550)
> Jan 31 15:30:40 rds-icap kernel: NFS: permission(0:25/8), mask=0x1, res=0
> Jan 31 15:30:40 rds-icap kernel: NFS: revalidating (0:25/656353)
> Jan 31 15:30:40 rds-icap kernel: NFS call getattr
> Jan 31 15:30:40 rds-icap kernel: NFS reply getattr: 0
> Jan 31 15:30:40 rds-icap kernel: NFS: nfs_update_inode(0:25/656353
> ct=1 info=0x6)
> Jan 31 15:30:40 rds-icap kernel: NFS: (0:25/656353) revalidation complete
> Jan 31 15:30:40 rds-icap kernel: NFS:
> nfs_lookup_revalidate(fvance/src) is valid
> Jan 31 15:30:40 rds-icap kernel: NFS: permission(0:25/656353),
> mask=0x1, res=0
*When it fails;*
> Jan 31 15:25:31 rds-icap kernel: NFS:
> nfs_updatepage(HISTFILES/.sh_history-rds-icap.bmc.com 8@1454)
> Jan 31 15:25:31 rds-icap kernel: NFS: nfs_updatepage returns 0
> (isize 1462)
> Jan 31 15:25:31 rds-icap kernel: NFS call access
> Jan 31 15:25:31 rds-icap kernel: NFS: nfs_update_inode(0:26/8 ct=1
> info=0x6)
> Jan 31 15:25:31 rds-icap kernel: NFS reply access: 0
> Jan 31 15:25:31 rds-icap kernel: NFS: permission(0:26/8), mask=0x1, res=0
> Jan 31 15:25:31 rds-icap kernel: NFS:
> nfs_lookup_revalidate(fvance/src) is valid
> Jan 31 15:25:31 rds-icap kernel: NFS call lookup src
> Jan 31 15:25:31 rds-icap kernel: NFS reply lookup: 0
> Jan 31 15:25:31 rds-icap kernel: --> nfs_xdev_get_sb()
> Jan 31 15:25:31 rds-icap kernel: -->
> nfs_clone_server(,ffffffffcc98e21e:0,)
> Jan 31 15:25:31 rds-icap kernel: --> nfs_probe_fsinfo()
> Jan 31 15:25:31 rds-icap kernel: NFS call fsinfo
> Jan 31 15:25:31 rds-icap kernel: NFS reply fsinfo: 0
> Jan 31 15:25:31 rds-icap kernel: NFS call pathconf
> Jan 31 15:25:31 rds-icap kernel: NFS reply pathconf: 0
> Jan 31 15:25:31 rds-icap kernel: <-- nfs_probe_fsinfo() = 0
> Jan 31 15:25:31 rds-icap kernel: Cloned FSID: ffffffffcc98e21e:0
> Jan 31 15:25:31 rds-icap kernel: <-- nfs_clone_server() = db5db8c0
> Jan 31 15:25:31 rds-icap kernel: --> nfs_free_server()
> Jan 31 15:25:31 rds-icap kernel: --> nfs_put_client({3})
> Jan 31 15:25:31 rds-icap kernel: <-- nfs_free_server()
> Jan 31 15:25:31 rds-icap kernel: do_proc_get_root: call fsinfo
> Jan 31 15:25:31 rds-icap kernel: do_proc_get_root: reply fsinfo: 0
> Jan 31 15:25:31 rds-icap kernel: NFS: nfs_update_inode(0:26/656353
> ct=2 info=0x6)
> Jan 31 15:25:31 rds-icap kernel: NFS: nfs_fhget(0:26/656353 ct=2)
> Jan 31 15:25:31 rds-icap kernel: <-- nfs_xdev_get_sb() = 0
Note,
inode for parent of fvance = 2
inode for fvance is 8
inode for src is 656353
Anyone help me figure out what is going wrong here?
-Dan Goetzman
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-01-31 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 21:53 Dan Goetzman [this message]
2007-02-01 4:31 ` NFS "Not a directory" problem Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45C10FE2.9060606@bmc.com \
--to=dan_goetzman@bmc.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.