Re: [pnfs] Linux pNFS status meeting 04/29

Re: [pnfs] Linux pNFS status meeting 04/29

[J. Bruce Fields]

On Wed, Apr 28, 2010 at 08:00:36PM -0700, Marc Eshel wrote:
> Meeting on Thursday 04/29/10 at 9:30 AM pacific time (12:30 PM UMICH time)

Rough agenda:

1. upstream status/merge plans (trond, bfields)

2. State of pNFS tree (bhalevy)

3. Mailing list change

4. Client
	4.1. Client pNFS status
	4.2. Client state management design documentation (trond)

5. Server
	5.1. Todo's for minimal 4.1 server (bfields)
		http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues
	5.2. pnfs

6. redhat status

7. bakeathon plans
	- Summer in Ann Arbor
	- Fall in Boston?

8. new business

--b.

Re: [pnfs] Linux pNFS status meeting 04/29

[J. Bruce Fields]

1. upstream status/merge plans (trond, bfields)
	- 2.6.34-rc5
	- server: merged one 2.6.34 bugfix, some more bugfixes/cleanup for
	  2.6.35, no new features merged.
	- client: bunch of bugfixes:
		- writeback code fixes:	
			- race with commit
			- nfs_setup_writeback BUG_ON()
		- other than that, misc. NULL/ERR-mixups.
		- Andy notes he's been seeing bigfile blocked for >= 30
		  seconds; Trond says that's probably due to the commit
		  race above.

2. State of pNFS tree (bhalevy)
	- forwarded-ported to -rc5, released a few minutes ago.  Passes
	  cthon cleanly (thanks to commit race fix).
	- merged some other patches.

3. Mailing list change
	- consolidated pnfs and nfsv4 lists to linux-nfs@vger.kernel.org
	- kernel.org appears to be having trouble; bfields will
	  investigate.

4. Client
	4.1. Client pNFS status
		- Andros sent a bunch of patches that remove
		  non-file-layout stuff from initial submission and add
		  it back in later (but using the generic deviceid
		  cache); latter needs review from object and block
		  developers.
	4.2. Client state management design documentation (trond)
		- nothing to report

5. Server
	5.1. Todo's for minimal 4.1 server (bfields)
		http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues
		- made some updates; things I'm working on are marked.
		  (Note to self: needs some more updates.  Also, I'll
		  need to start moving "done" things into "needs
		  testing" category.
		- testing problems:
			- will probably need pynfs tests to go with
			  server 4.1 changes.
			- 4.1 pynfs doesn't handle DELAY errors, so they
			  fail immediately against current server.  Fred
			  will check if it's easily fixed.
			  I will also make Neil's deferral fix a higher
			  priority to remove need for so many
			  DELAY's.
	5.2. pnfs
		- Sorin notes he's been able to get block server up and
		  running (not bug-free, but it does some IO at least).
		  Hasn't worked out why Jiri Kortus isn't getting that
		  far.

6. Red Hat status
	- Steve will update to latest tag.
	- note to Steve: make sure avoiding commit race.  rc1-rc4-based
	  code had it, latest -rc5 tag should be OK.  Not sure about
	  2.6.33-based code.
	- Documentation:
		- Steve is finding documentation of pnfs setup hard to
		  find.  He will work on tracking down docs and
		  reorganizing wiki.
		- Andy will help Steve with GFS2 setup docs.
		- Sorin & co. should be able to help with block setup
		  docs.
	- Steved eventually wants to do more 4.1 testing.
	- Boaz asked for some pointers on how to get started building
	  rpm's, so he can distribute exofs utilities.  Steved will
	  help.

7. bakeathon plans
	- Summer in Ann Arbor
	- Fall in Boston?:
		- deciding on date.

8. Next meeting:
	- Same time, some place; Marc will be out, so Dean will host.

--b.

Re: [pnfs] Linux pNFS status meeting 04/29

[J. Bruce Fields]

On Thu, Apr 29, 2010 at 01:39:03PM -0400, J. Bruce Fields wrote:
> 1. upstream status/merge plans (trond, bfields)
> 	- 2.6.34-rc5
> 	- server: merged one 2.6.34 bugfix, some more bugfixes/cleanup for
> 	  2.6.35, no new features merged.
> 	- client: bunch of bugfixes:
> 		- writeback code fixes:	
> 			- race with commit
> 			- nfs_setup_writeback BUG_ON()
> 		- other than that, misc. NULL/ERR-mixups.
> 		- Andy notes he's been seeing bigfile blocked for >= 30
> 		  seconds; Trond says that's probably due to the commit
> 		  race above.
> 
> 2. State of pNFS tree (bhalevy)
> 	- forwarded-ported to -rc5, released a few minutes ago.  Passes
> 	  cthon cleanly (thanks to commit race fix).
> 	- merged some other patches.
> 
> 3. Mailing list change
> 	- consolidated pnfs and nfsv4 lists to linux-nfs@vger.kernel.org
> 	- kernel.org appears to be having trouble; bfields will
> 	  investigate.

As far as I can tell, from my mail and from public archives, the
kernel.org mailing lists just aren't working right now.

So for now I'm inclined to assume someobody's already working on it and
hope it'll be fixed soon....

Bad timing with the change, though!

--b.

Re: [pnfs] Linux pNFS status meeting 04/29

[J. Bruce Fields]

On Thu, Apr 29, 2010 at 02:43:11PM -0400, J. Bruce Fields wrote:
> On Thu, Apr 29, 2010 at 01:39:03PM -0400, J. Bruce Fields wrote:
> > 1. upstream status/merge plans (trond, bfields)
> > 	- 2.6.34-rc5
> > 	- server: merged one 2.6.34 bugfix, some more bugfixes/cleanup for
> > 	  2.6.35, no new features merged.
> > 	- client: bunch of bugfixes:
> > 		- writeback code fixes:	
> > 			- race with commit
> > 			- nfs_setup_writeback BUG_ON()
> > 		- other than that, misc. NULL/ERR-mixups.
> > 		- Andy notes he's been seeing bigfile blocked for >= 30
> > 		  seconds; Trond says that's probably due to the commit
> > 		  race above.
> > 
> > 2. State of pNFS tree (bhalevy)
> > 	- forwarded-ported to -rc5, released a few minutes ago.  Passes
> > 	  cthon cleanly (thanks to commit race fix).
> > 	- merged some other patches.
> > 
> > 3. Mailing list change
> > 	- consolidated pnfs and nfsv4 lists to linux-nfs@vger.kernel.org
> > 	- kernel.org appears to be having trouble; bfields will
> > 	  investigate.
> 
> As far as I can tell, from my mail and from public archives, the
> kernel.org mailing lists just aren't working right now.

vger seems to be back, but mail to neither the pnfs nor the nfsv4 lists
is getting forwarded to this list.

All I did was add linux-nfs@vger.kernel.org as a member of each of the
two lists.

I can't find anything useful in linux-nfs logs, but maybe I don't know
what to look for....

--b.