From: Andrew Morton <akpm@digeo.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
kernel@whiskerfish.com
Subject: [Fwd: [Bug 136] New: FSID returned from statvfs always 0]
Date: Tue, 03 Dec 2002 15:53:27 -0800 [thread overview]
Message-ID: <3DED43F7.AD396584@digeo.com> (raw)
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?
next reply other threads:[~2002-12-03 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 23:53 Andrew Morton [this message]
2002-12-04 3:11 ` [Fwd: [Bug 136] New: FSID returned from statvfs always 0] Stephen Lord
2002-12-04 3:25 ` Andries Brouwer
2002-12-04 4:09 ` Andrew Morton
2002-12-04 18:00 ` Bryan Henderson
2002-12-09 22:15 ` H. Peter Anvin
2002-12-09 23:04 ` Andries Brouwer
2002-12-18 5:15 ` Andrew Morton
2002-12-18 16:25 ` Bryan Henderson
2002-12-18 20:18 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DED43F7.AD396584@digeo.com \
--to=akpm@digeo.com \
--cc=kernel@whiskerfish.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).