[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080905200455.GH22796@merfinllc.com>
Date: Fri, 5 Sep 2008 13:04:55 -0700
From: Aaron Straus <aaron@...finllc.com>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: Neil Brown <neilb@...e.de>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
Trond Myklebust <trond.myklebust@....uio.no>,
LKML Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [NFS] blocks of zeros (NULLs) in NFS files in kernels >= 2.6.20
Hi,
On Sep 05 03:56 PM, Chuck Lever wrote:
> [ replacing cc: nfs@...net with linux-nfs@...r.kernel.org, and neil's
> old address with his current one ]
Sorry I probably grabbed an old MAINTAINERS file.
> On Sep 5, 2008, at Sep 5, 2008, 3:19 PM, Aaron Straus wrote:
> > Writer_Version Outcome:
> > <= 2.6.19 OK
> > >= 2.6.20 BAD
>
> Up to which kernel? Recent ones may address this issue already.
BAD up to 2.6.27-rc?
I have to see exactly which is the last rc version I tested.
> > I can try to bisect between 2.6.19 <-> 2.6.20.
>
> That's a good start.
OK will try to bisect.
> Comparing a wire trace with strace output, starting with the writing
> client, might also be illuminating. We prefer wireshark as it uses
> good default trace settings, parses the wire bytes and displays them
> coherently, and allows you to sort the frames in various useful ways.
OK. Could you also try to reproduce on your side using those python
programs? I want to make sure it's not something specific with our
mounts, etc.
Thanks!
=a=
--
===================
Aaron Straus
aaron@...finllc.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists