From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Morton <akpm@digeo.com>
Subject: [Fwd: [Bug 136] New: FSID returned from statvfs always 0]
Date: Tue, 03 Dec 2002 15:53:27 -0800
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <3DED43F7.AD396584@digeo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from digeo-nav01.digeo.com (digeo-nav01.digeo.com [192.168.1.233])
	by packet.digeo.com (8.9.3+Sun/8.9.3) with SMTP id PAA25164
	for <linux-fsdevel@vger.kernel.org>; Tue, 3 Dec 2002 15:53:29 -0800 (PST)
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	kernel@whiskerfish.com
List-Id: linux-fsdevel.vger.kernel.org

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?