On Tue, May 06, 2003 at 02:50:53PM +0200, Trond Myklebust wrote:
> >>>>> " " == Mike Fedyk <firstname.lastname@example.org> writes:
> > Might that cause this too:
> > May 5 15:32:10 fileserver kernel: lockd: can't encode
> > arguments: 5
> > 2.4.21-rc1-rmap15g is giving the above error, and
> > 2.4.20-rmap15e is not. I'll leave it on 2.4.20-rmap15e for now
> > and let you know if there are any errors on that one too.
> I'm confused. Are the rmap patches making changes to lockd?
> I certainly don't see the above errors in standard 2.4.21-rc1.
Oh, one more thing.
This is output from a server running 2.4.19-freeswan mounting an nfs export
from a reiserfs based 112GB export using 2.4.21-rc1-freeswan-rmap. When the
112GBs are exported from 2.4.20-freeswan-rmap, there is no error.
I will retest, but I hope this isn't a bug making it through the pre & rc
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 07 2003 - 22:00:32 EST