Re: Weird exportfs behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 19, 2010 at 03:59:33PM -0500, David P. Quigley wrote:
> On Tue, 2010-01-19 at 15:48 -0500, J. Bruce Fields wrote:
> > Looks like you have to modify both support/nfs/exports.c:putexportent()
> > and utils/exportfs/exportfs.c:dump(), in addition to parseopts().
> > (Which is really confusing.  Someone should fix that..) Maybe you're
> > forgetting one of those?
> > 
> > --b.
> 
> I'm almost certain I am. I'll look over my patches again to take a look
> at that. I also need to look over my update code for the kernel export
> function because I was getting the labelloc entry in /var/lib/nfs/etab
> on initial daemon start but subsequent exportfs options seem to make it
> go away.

You might have been missing code to parse it or store it in an export,
so it got lost before it wrote the entry back out again?  I don't know.

If you're feeling community-minded, that business with having two
entirely separate bits of code to write out an etab entry seems silly.
(Maybe there are two different formats, I'm forgetting, but if so
couldn't they at least share common code to lookup the string names of
the options?)

--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux