From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Lord Subject: Re: [Fwd: [Bug 136] New: FSID returned from statvfs always 0] Date: 03 Dec 2002 21:11:46 -0600 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1038971510.1921.28.camel@localhost.localdomain> References: <3DED43F7.AD396584@digeo.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: "linux-fsdevel@vger.kernel.org" , kernel@whiskerfish.com Return-path: To: Andrew Morton In-Reply-To: <3DED43F7.AD396584@digeo.com> List-Id: linux-fsdevel.vger.kernel.org On Tue, 2002-12-03 at 17:53, Andrew Morton wrote: > I've been hit with a bugzilla record alleging that statfs > is failing to initialise the statfs.f_fsid field. > > This is that case in both 2.4 and 2.5. It seems that XFS > puts something in there. > > Can anyone suggest whether we should be putting something in > there and if so, what? > > The submitter suggests using part of the UUID. > > What is is used for? Not totally sure, rpc.mountd.c copies it around. XFS actually puts a dev_t in it, I do not off the top of my head (or cscopes head for that matter) see any consumers of it, but I think it should at least be unique among filesystems on a host. Steve