Re: nfs4.1 pseudo filesystem

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

 



On Oct 11, 2013, at 4:58 PM, "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote:

> On Fri, Oct 11, 2013 at 02:29:42PM -0400, J. Bruce Fields wrote:
>> On Fri, Oct 11, 2013 at 04:51:29PM +0000, Ming Lei wrote:
>>> I want to cherry-pick a few subdirectories under say /root, but I don't want to specifies all these mount directories one by one just like NFSv2/3.
>> 
>> Well, you're kind of stuck enumerating them whether as exports or bind
>> mounts.
>> 
>>> Does pseudo filesystem in kernel v3.11 work well enough?
>> 
>> But it should work anyway, yes.
>> 
>> Oh, wait, I see the problem: it doesn't work well if you're exporting
>> subdirectories and not full filesystems.  Unless you do something
>> special at the export points  (e.g. mount --bind them over themselves),
>> knfsd doesn't know when you've crossed an export point.
> 
> I wonder if exportfs should be taught to mark export points as
> junctions.  That might fix this kind of problem?

A junction is always an unreadable directory.

We'd be better off with a generic "please upcall" bit for directories.  Then mountd could sort out what are junctions and what are legitimate exports, and the kernel would leave all the other directories in an export alone.

> It might mean creating junctions never get cleaned up, which is ugly
> though perhaps unlikely to be a serious problem in practice.

-- 
Chuck Lever
chuck[dot]lever[at]oracle[dot]com




--
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