From: Andrew Morton <akpm@digeo.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [Fwd: [Bug 136] New: FSID returned from statvfs always 0]
Date: Tue, 17 Dec 2002 21:15:00 -0800 [thread overview]
Message-ID: <3E000454.F791294@digeo.com> (raw)
In-Reply-To: 20021209230418.GA9444@win.tue.nl
Andries Brouwer wrote:
>
> On Mon, Dec 09, 2002 at 02:15:12PM -0800, H. Peter Anvin wrote:
>
> > > The general idea is that f_fsid contains some random stuff such that
> > > the pair (f_fsid,ino) uniquely determines a file.
>
> > This, of course, is the exact POSIX definition of the st_dev part of
> > struct stat: (st_dev, st_ino) uniquely identifies the file.
>
> Yes, but the difference is that (st_dev, st_ino) only identifies
> the file within a single machine, and may stop working when you
> have NFS mounts.
>
> The traditional implementations use st_dev and NFS filehandles
> and a hash of the filesystem type.
>
If this feature is to have any value, should not the fsid remain stable
as the disk gets moved around the machine?
I'm not sure I saw sufficient solidity in this discussion to be able to
generate&justify a patch.
next prev parent reply other threads:[~2002-12-18 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 23:53 [Fwd: [Bug 136] New: FSID returned from statvfs always 0] Andrew Morton
2002-12-04 3:11 ` 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 [this message]
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=3E000454.F791294@digeo.com \
--to=akpm@digeo.com \
--cc=aebr@win.tue.nl \
--cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.