| To: | "J. Bruce Fields" <bfields@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 14/18] nfsd: pNFS block layout driver |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Tue, 6 Jan 2015 18:39:57 +0100 |
| Cc: | Jeff Layton <jlayton@xxxxxxxxxxxxxxx>, linux-nfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20150106171658.GD12067@xxxxxxxxxxxx> |
| References: | <1420561721-9150-1-git-send-email-hch@xxxxxx> <1420561721-9150-15-git-send-email-hch@xxxxxx> <20150106171658.GD12067@xxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Tue, Jan 06, 2015 at 12:16:58PM -0500, J. Bruce Fields wrote: > > +file system must sit on shared storage (typically iSCSI) that is accessible > > +to the clients as well as the server. The file system needs to either sit > > +directly on the exported volume, or on a RAID 0 using the MD software RAID > > +driver with the version 1 superblock format. If the filesystem uses sits > > +on a RAID 0 device the clients will automatically stripe their I/O over > > +multiple LUNs. > > + > > +On the server pNFS block volume support is automatically if the file system > > s/automatically/automatically enabled/. > > So there's no server-side configuration required at all? The only required configuration is the fencing helper script if you want to be able to fence a non-responding client. For simple test setups everything will just work out of the box. |
| Previous by Date: | Re: a simple and scalable pNFS block layout server, J. Bruce Fields |
|---|---|
| Next by Date: | Re: [PATCH 10/18] nfsd: implement pNFS layout recalls, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH 14/18] nfsd: pNFS block layout driver, J. Bruce Fields |
| Next by Thread: | Re: [PATCH 14/18] nfsd: pNFS block layout driver, J. Bruce Fields |
| Indexes: | [Date] [Thread] [Top] [All Lists] |