From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [PATCH 14/18] nfsd: pNFS block layout driver Date: Tue, 6 Jan 2015 14:39:49 -0500 Message-ID: <20150106193949.GD28003@fieldses.org> References: <1420561721-9150-1-git-send-email-hch@lst.de> <1420561721-9150-15-git-send-email-hch@lst.de> <20150106171658.GD12067@fieldses.org> <20150106173957.GA16200@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org, Jeff Layton , xfs@oss.sgi.com To: Christoph Hellwig Return-path: Content-Disposition: inline In-Reply-To: <20150106173957.GA16200@lst.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org On Tue, Jan 06, 2015 at 06:39:57PM +0100, Christoph Hellwig wrote: > 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. I think we want at a minimum some kind of server-side "off" switch. If nothing else it'd be handy for troubleshooting. ("Server crashing? Could you turn off pnfs blocks and try again?") --b. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from fieldses.org ([174.143.236.118]:37110 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338AbbAFTjw (ORCPT ); Tue, 6 Jan 2015 14:39:52 -0500 Date: Tue, 6 Jan 2015 14:39:49 -0500 From: "J. Bruce Fields" To: Christoph Hellwig Cc: Jeff Layton , linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: [PATCH 14/18] nfsd: pNFS block layout driver Message-ID: <20150106193949.GD28003@fieldses.org> References: <1420561721-9150-1-git-send-email-hch@lst.de> <1420561721-9150-15-git-send-email-hch@lst.de> <20150106171658.GD12067@fieldses.org> <20150106173957.GA16200@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20150106173957.GA16200@lst.de> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Jan 06, 2015 at 06:39:57PM +0100, Christoph Hellwig wrote: > 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. I think we want at a minimum some kind of server-side "off" switch. If nothing else it'd be handy for troubleshooting. ("Server crashing? Could you turn off pnfs blocks and try again?") --b.