From: Oleg Drokin <green@linuxhacker.ru>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: FS-specified FSID for non-device based filesystems?
Date: Fri, 14 Apr 2006 23:45:43 +0300 [thread overview]
Message-ID: <20060414204543.GE10907@linuxhacker.ru> (raw)
In-Reply-To: <OFE1D40E00.75DD4A97-ON88257150.006E4E2D-88257150.006FEAAC@us.ibm.com>
Hello!
On Fri, Apr 14, 2006 at 01:22:14PM -0700, Bryan Henderson wrote:
> When Linux added the export ID, at a time when other operating systems
> were addressing the problem with the kind of fsid you're proposing, I
> believe the point was that in Linux you can have multiple incompatible
> exports of the same filesystem -- to give a client the right data, you'd
> need to know from which export, not just which filesystem, a given
> filehandle came.
Well, I do not see how there is a difference.
>From my reading of the code it seems that fsid is composed of device's
minor/major and export point's inode ino.
I propose to replace (if supported by fs) device's minor/major by
some unique number returned by fs itself.
Should be no worse than what we have now.
Bye,
Oleg
next prev parent reply other threads:[~2006-04-14 20:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 11:10 FS-specified FSID for non-device based filesystems? Oleg Drokin
2006-04-14 20:22 ` Bryan Henderson
2006-04-14 20:45 ` Oleg Drokin [this message]
2006-04-14 20:59 ` J. Bruce Fields
2006-04-14 21:32 ` Bryan Henderson
2006-04-14 21:41 ` Oleg Drokin
2006-04-17 0:54 ` Neil Brown
2006-04-17 3:50 ` Greg KH
2006-04-17 4:32 ` Neil Brown
2006-04-18 18:07 ` Greg KH
2006-04-19 12:15 ` Miklos Szeredi
2006-04-20 11:35 ` Al Viro
2006-04-20 11:58 ` Miklos Szeredi
2006-04-20 12:30 ` Al Viro
2006-04-20 12:43 ` Miklos Szeredi
2006-04-17 8:00 ` Anton Altaparmakov
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=20060414204543.GE10907@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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