[OpenAFS-devel] Anyone have i386_linux24/2.4.5-x working w/ c urrent cvs?

[Neulinger, Nathan]

A patch was just committed to cvs that seems to have corrected the problems
I was having. All working again now! 
 
-- Nathan

> -----Original Message-----
> From: Herbert Huber [mailto:Herbert.Huber@lrz-muenchen.de]
> Sent: Wednesday, July 11, 2001 3:42 AM
> To: Neulinger, Nathan
> Cc: 'openafs-devel@openafs.org'
> Subject: Re: [OpenAFS-devel] Anyone have i386_linux24/2.4.5-x 
> working w/
> c urrent cvs?
> 
> 
> "Neulinger, Nathan" wrote:
> 
> > Fyi - I just tried and don't have this problem on 
> i386_linux22 built against
> > current.
> >
> > I'm going to try cleaning up this system and building 
> again, just in case I
> > have a kernel source/headers/something or other mismatch 
> that is causing
> > goofiness, but I'd still appreciate a heads up if anyone 
> else is running ok
> > with 24 and current cvs.
> >
> > -- Nathan
> >
> > > -----Original Message-----
> > > From: Neulinger, Nathan [mailto:nneul@umr.edu]
> > > Sent: Tuesday, July 10, 2001 2:03 PM
> > > To: 'openafs-devel@openafs.org'
> > > Subject: RE: [OpenAFS-devel] Anyone have i386_linux24/2.4.5-x
> > > working w/
> > > c urrent cvs?
> > >
> > >
> > > I'm getting some very strange symptoms... Last time I had a
> > > working build
> > > was before June 28th or so (before I left on vacation and 
> all the full
> > > autoconf stuff was done).
> > >
> > > Sometimes afsd starts ok, and looks like it started up ok,
> > > but /afs seems to
> > > point to / and claims not to be mounted. Other times, I'm
> > > getting two oops's
> > > after the mount. Both are bad refCount messages with the
> > > refCount being a
> > > large (but not near any overflow) negative number like
> > > -923429898. The first
> > > of the two oopses has a "failed to store file (19)", which
> > > corresponds to
> > > ENODEV.
> > >
> > > In either case if I do a 'df -i' it hangs.
> > >
> > > I've recreated the afscache filesystem, everything is from a
> > > clean build
> > > from current with kgcc on rh71.
> > >
> > > The trace from the oops isn't particularly useful either but
> > > I can get it if
> > > needed. All oops's have been in osi_iput, 
> afs_shared_mmap_ops, calling
> > > osi_Panic.
> > >
> > > -- Nathan
> > >
> > > > -----Original Message-----
> > > > From: Neulinger, Nathan [mailto:nneul@umr.edu]
> > > > Sent: Tuesday, July 10, 2001 9:09 AM
> > > > To: 'openafs-devel@openafs.org'
> > > > Subject: [OpenAFS-devel] Anyone have 
> i386_linux24/2.4.5-x working w/
> > > > current cvs?
> > > >
> > > >
> > > > I am currently unable to get a working build. The compile
> > > > completes just
> > > > fine (well, except for kdump not getting the kernel version,
> > > > but that's a
> > > > minor issue), but I get an oops every time I start afsd. Only
> > > > changes from
> > > > the base are to force use of kgcc for everything.
> > > >
> > > > -- Nathan
> > > >
> > > > ------------------------------------------------------------
> > > > Nathan Neulinger                       EMail:  nneul@umr.edu
> > > > University of Missouri - Rolla         Phone: (573) 341-4841
> > > > Computing Services                       Fax: (573) 341-4216
> > > > _______________________________________________
> > > > OpenAFS-devel mailing list
> > > > OpenAFS-devel@openafs.org
> > > > https://lists.openafs.org/mailman/listinfo/openafs-devel
> > > >
> > > _______________________________________________
> > > OpenAFS-devel mailing list
> > > OpenAFS-devel@openafs.org
> > > https://lists.openafs.org/mailman/listinfo/openafs-devel
> > >
> > _______________________________________________
> > OpenAFS-devel mailing list
> > OpenAFS-devel@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-devel
> 
> We are running openafs cvs from 20.6.2001 on single and dual 
> nodes with a high
> memory enabled  2.4.5 since 2.7.2001 without any problems . I 
> have to say that
> we use SuSE 6.4 on our cluster nodes (libc-2.1.3-155)!
> 
> Regards
> 
> /Herbert
>