All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>, Andries Brouwer <aebr@win.tue.nl>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [Fwd: [Bug 136] New: FSID returned from statvfs always 0]
Date: Wed, 18 Dec 2002 12:18:59 -0800	[thread overview]
Message-ID: <3E00D833.7070700@zytor.com> (raw)
In-Reply-To: <OF58D9AD29.61FD1057-ON87256C93.005990BD-88256C93.005A2605@us.ibm.com>

Bryan Henderson wrote:
> 
> To have _any_ value would be an overstatement.  Today's FSID (always zero)
> has no value.  An FSID that works only in machines where the disks never
> move would have more value than that.
> 
> But as long as we're talking about designs that solve the entire problem,
> don't forget this aspect too:  A perfect FSID must be stable as the
> filesystem is moved from one disk to another while the disks stay put.
> And, more importantly, must change when you replace the contents of a disk
> with a new or different filesystem.
>

I.e. it's the UUID of the filesystem (if one exists.)

	-hpa


      reply	other threads:[~2002-12-18 20:18 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
2002-12-18 16:25         ` Bryan Henderson
2002-12-18 20:18           ` H. Peter Anvin [this message]

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=3E00D833.7070700@zytor.com \
    --to=hpa@zytor.com \
    --cc=aebr@win.tue.nl \
    --cc=akpm@digeo.com \
    --cc=hbryan@us.ibm.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.