From: Nathan Neulinger <nneul@umr.edu>
To: linux-kernel@vger.kernel.org
Subject: Changes between 2.4.21 and 2.4.22-pre1 affecting filesystem mounts?
Date: Fri, 14 Nov 2003 13:34:16 -0600 [thread overview]
Message-ID: <1068838455.2770.7.camel@infinity.cc.umr.edu> (raw)
In-Reply-To: <1068831962.2668.5.camel@infinity.cc.umr.edu>
Sorry for the resend if you've already seen this, I had addr wrong...
Any ideas?
On Fri, 2003-11-14 at 11:46, Nathan Neulinger wrote:
> Narrowed this down to it breaking between 2.4.21 release and
> 2.4.22-pre1. (2.4.21 works fine, 22-pre1 does not.) I read over the
> detailed 2.4.22 ChangeLog and sure don't see anything that jumps out at
> me as a likely cause... Any ideas?
>
> Basically, client looks like it starts up just fine, but there's nothing
> there. /afs is definately mounted, but the mount is non-functional and
> complains about not being a directory.
>
> -- Nathan
>
> On Fri, 2003-11-14 at 07:50, Nathan Neulinger wrote:
> > I haven't dug into this in depth yet, but figured I'd ask in case the
> > answer was obvious to any kernel developers - tried updating to
> > 2.4.23-rc1 w/ openafs, and the filesystem mounts, but every traversal
> > attempt results in ENOTDIR. Is there something that changed in kernel
> > structures/functions/interfaces that needs to be addressed in openafs
> > src to fix this? Pointers to change info appreciated.
> >
> > -- Nathan
> >
> > ------------------------------------------------------------
> > Nathan Neulinger EMail: nneul@umr.edu
> > University of Missouri - Rolla Phone: (573) 341-4841
> > UMR Information Technology Fax: (573) 341-4216
--
------------------------------------------------------------
Nathan Neulinger EMail: nneul@umr.edu
University of Missouri - Rolla Phone: (573) 341-6679
UMR Information Technology Fax: (573) 341-4216
parent reply other threads:[~2003-11-14 19:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1068831962.2668.5.camel@infinity.cc.umr.edu>]
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=1068838455.2770.7.camel@infinity.cc.umr.edu \
--to=nneul@umr.edu \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®