Re: [PATCH 0/4] 2.6.21-rc7 NFS writes: fix a series of issues

Trond Myklebust
2007-04-18T03:54:48Z

On Tue, 2007-04-17 at 22:30 -0500, Florin Iucha wrote:
> On Tue, Apr 17, 2007 at 11:06:05PM -0400, Trond Myklebust wrote:
> > > > I've split the issues introduced by the 2.6.21-rcX write code up into 4
> > > > subproblems.
> > > >
> > > > The first patch is just a cleanup in order to ease review.
> > > >
> > > > Patch number 2 ensures that we never release the PG_writeback flag until
> > > > _after_ we've either discarded the unstable request altogether, or put it
> > > > on the nfs_inode's commit or dirty lists.
> > > >
> > > > Patch number 3 fixes the 'desynchronized value of nfs_i.ncommit' error. It
> > > > uses the PG_NEED_COMMIT flag as an indicator for whether or not the request
> > > > may be redirtied.
> > > >
> > > > Patch number 4 protects the NFS '.set_page_dirty' address_space operation
> > > > against races with nfs_inode_add_request.
> > >
> > > For 2.6.21, yes?
> >
> > Right. A couple of nasty regressions have been sighted. This series
> > attempts to deal with them all.
>
> The good news is that the Gnome session log-in progresses to the point
> where both top and bottom bars are painted (gray) and the bottom bar
> is populated with icons (2.6.21-rc7 vanilla stops after displaying the
> splash). The bad news is that it stops there.
>
> Big-copy fails as well, after 2.5G transferred.
>
> The process traces are at:
>
> http://iucha.net/nfs/21-rc7-nfs1/gnome-session
> http://iucha.net/nfs/21-rc7-nfs1/big-copy
>
> Regards,
> florin

Could you tell us a bit more about what happens when these hangs occur?
Does the networking stop too, or just NFS? How about CIFS?

Cheers
Trond