[pnfs] Per export pnfs data server list
Steve Dickson
SteveD at redhat.com
Tue Jul 7 15:51:40 EDT 2009
On 07/07/2009 03:00 PM, Andy Adamson wrote:
>
> On Jul 7, 2009, at 2:51 PM, J. Bruce Fields wrote:
>
>> On Tue, Jul 07, 2009 at 02:20:41PM -0400, Andy Adamson wrote:
>>> Hi Bruce
>>>
>>> Moving forward with the "Simple File Layout" pNFS server used by GFS2.
>>> The ability to indicate if pnfs is enabled on a per file system
>>> basis, and the ability to write and change a data server list (per
>>> export) are both needed to manage pnfsd/gfs2.
>>>
>>> Here is what I added:
>>> 1) Addition of /etc/exports option "pnfs" to indicate the export is a
>>> file layout pnfs export.
>>>
>>> Should this be changed to "pnfs=file" ?
>>>
>>> 2) Addition of /proc/fs/nfsd/pnfs_ds_list.
>>>
>>> This needs to be per export, and the kernel should notice when it
>>> changes so that the device notify or layoutrecall callback can be
>>> triggered.
>>> Any suggestions on where to put a per-export ds list?
>>
>> Maybe instead of "pnfs" or "pnfs=file" on the exports, have just
>> "pnfs-data-server=server1,server2,..."?
Just curious.... why do pnfs exports have to live in /etc/exports?
I just seems to me that we are completely overloading what is there
today with complexity that people may not use. Plus the administration
such complexity will be come a nightmare, imho.
So why no put all the complexity of the pnfs exports into its own
exports file? /etc/export.pnfs or /etc/pnfs.exports something of
that nature...
How are other server implementations dealing with this??
steved.
More information about the pNFS
mailing list