From: "NeilBrown" <neilb@suse.de>
To: "Josef Bacik" <josef@toxicpanda.com>
Cc: "Chris Mason" <clm@fb.com>, "David Sterba" <dsterba@suse.com>,
linux-fsdevel@vger.kernel.org,
"Linux NFS list" <linux-nfs@vger.kernel.org>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH/RFC 0/4] Attempt to make progress with btrfs dev number strangeness.
Date: Fri, 13 Aug 2021 08:35:51 +1000 [thread overview]
Message-ID: <162880775121.15074.3288255136681201159@noble.neil.brown.name> (raw)
In-Reply-To: <6571d3fb-34ea-0f22-4fbe-995e5568e044@toxicpanda.com>
On Thu, 12 Aug 2021, Josef Bacik wrote:
> On 8/11/21 6:13 PM, NeilBrown wrote:
> > On Wed, 11 Aug 2021, Josef Bacik wrote:
> >>
> >> I think this is a step in the right direction, but I want to figure out a way to
> >> accomplish this without magical mount points that users must be aware of.
> >
> > magic mount *options* ???
> >
> >>
> >> I think the stat() st_dev ship as sailed, we're stuck with that. However
> >> Christoph does have a valid point where it breaks the various info spit out by
> >> /proc. You've done a good job with the treeid here, but it still makes it
> >> impossible for somebody to map the st_dev back to the correct mount.
> >
> > The ship might have sailed, but it is not water tight. And as the world
> > it round, it can still come back to bite us from behind.
> > Anything can be transitioned away from, whether it is devfs or 32-bit
> > time or giving different device numbers to different file-trees.
> >
> > The linkage between device number and and filesystem is quite strong.
> > We could modified all of /proc and /sys/ and audit and whatever else to
> > report the fake device number, but we cannot get the fake device number
> > into the mount table (without making the mount table unmanageablely
> > large).
> > And if subtrees aren't in the mount-table for the NFS server, I don't
> > think they should be in the mount-table of the NFS client. So we cannot
> > export them to NFS.
> >
> > I understand your dislike for mount options. An alternative with
> > different costs and benefits would be to introduce a new filesystem type
> > - btrfs2 or maybe betrfs. This would provide numdevs=1 semantics and do
> > whatever we decided was best with inode numbers. How much would you
> > hate that?
> >
>
> A lot more ;).
>
> >>
> >> I think we aren't going to solve that problem, at least not with stat(). I
> >> think with statx() spitting out treeid we have given userspace a way to
> >> differentiate subvolumes, and so we should fix statx() to spit out the the super
> >> block device, that way new userspace things can do their appropriate lookup if
> >> they so choose.
> >
> > I don't think we should normalize having multiple devnums per filesystem
> > by encoding it in statx(). It *would* make sense to add a btrfs ioctl
> > which reports the real device number of a file. Tools that really need
> > to work with btrfs could use that, but it would always be obvious that
> > it was an exception.
>
> That's not what I'm saying. I'm saying that stat() continues to behave the way
> it currently does, for legacy users.
>
> And then for statx() it returns the correct devnum like any other file system,
> with the augmentation of the treeid so that future userspace programs can use
> the treeid to decide if they want to wander into a subvolume.
Yes, that is what I thought you were saying. It implies that the
possibility of a file having two different device numbers becomes
normalised in the API - one returned by stat(), the other by statx()
(presumably in a new field - the FS cannot tell what libc call the
application made). I don't like that.
>
> This way moving forward we have a way to map back to a mount point because
> statx() will return the actual devnum for the mountpoint, and then we can use
> the treeid to be smart about when we wander into a subvolume.
We already have a way to map back to a mountpoint. statx reports a
mnt_id with result flag STATX_MNT_ID. This is the number at the start
of the line in mountinfo. Hmmm, this isn't in the manpage. It has been
in the kernel since Linux 5.8. I'll send a patch for the manpage.
So we could pursue a path where the device-id no longer defines the
filesystem (or mount), but instead it defines some arbitrary grouping of
objects within a filesystem. So instead of my proposed
dev-id / subtree-id / inode-number
we would have
dev-id-in-mountinfo / mnt_id / dev-id-in-stat / inode-number
In some ways this would be a smoother path forward - no change to statx,
no new concepts, just formalizing some de-facto concepts.
In other ways it might be rougher - we would need to convince the
community to use the stat() dev-id in all those proc files etc.
I think having the two meanings for a device-id would cause confusion for
quite some years..... but then any change will probably cause confusion.
>
> And if we're going to add a treeid, I would actually like to add a parent_treeid
> as well so we could tell if we're a snapshot or just a normal subvolume.
Is this a well-defined concept? Isn't "snapshot" just one possible
use-case for the btrfs functionality of creating a reflink to a subtree?
What happens to the "parent_treeid" reference when that "parent" gets
deleted?
I understand the desire to track this sort of connection, but I wonder
if the filesystem is really the right place to track it. Maybe having
the tools track it would be better.
>
> >
> >>
> >> This leaves the problem of nfsd. Can you just integrate this new treeid into
> >> nfsd, and use that to either change the ino within nfsd itself, or do something
> >> similar to what your first patchset did and generate a fsid based on the treeid?
> >
> > I would only want nfsd to change the inode number. I no longer think it
> > is acceptable for nfsd to report different device number (as I mention
> > above).
> > I would want the new inode number to be explicitly provided by the
> > filesystem. Whether that is a new export_operation or a new field in
> > 'struct kstat' doesn't really bother me. I'd *prefer* it to be st_ino,
> > but I can live without that.
> >
>
> Right, I'm not saying nfsd has to propagate our dev_t thing, I'm saying that you
> could accomplish the same behavior without the mount options. We add either a
> new SB_I_HAS_TREEID or FS_HAS_TREEID, depending on if you prefer to tag the sb
> or the fs_type, and then NFS does the inode number magic transformation
> automatically and we are good to go.
I really don't want nfsd to do the magic transformations. I want the
filesystem to do those if they need to be done. I could cope with nfsd
xor-ing some provided number with i_ino, but I wouldn't like nfsd to
have the responsibility of doing the swab64().
>
> > On the topic of inode numbers.... I've recently learned that btrfs
> > never reuses inode (objectid) numbers (except possibly after an
> > unmount). Equally it doesn't re-use subvol numbers. How much does this
> > contribute to the 64 bits not being enough for subtree+inode?
> >
> > It would be nice if we could be comfortable limiting the objectid number
> > to 40 bits and the root.objectid (filetree) number to 24 bits, and
> > combine them into a 64bit inode number.
> >
> > If we added a inode number reuse scheme that was suitably performant,
> > would that make this possible? That would remove the need for a treeid,
> > and allow us to use project-id to identify subtrees.
> >
>
> We had a resuse scheme, we deprecated and deleted it. I don't want to
> arbitrarily limit objectid's to work around this issue.
These are computers we are working with. There are always arbitrary
limits.
The syscall interface places an arbitrary limit of 64bits on the
identity of any object in a filesystem. btrfs clearly doesn't like that
arbitrary limit, and plays games with device number to increase it to a
new arbitrary limit of 84 bits (sort-of).
I'm fully open to the possibility that last year's arbitrary limits are
no longer comfortable and that we might need to push the boundaries.
But I'd rather the justification was a bit stronger than "we cannot be
bothered reusing old inode numbers".
Are you at all aware of any site coming anywhere vaguely close to one trillion
concurrent inodes - maybe even 16 billion?
Or anything close to 16 million concurrent subvolumes?
>
> >>
> >> Mount options are messy, and are just going to lead to distro's turning them on
> >> without understanding what's going on and then we have to support them forever.
> >> I want to get this fixed in a way that we all hate the least with as little
> >> opportunity for confused users to make bad decisions. Thanks,
> >
> > Hence my question: how much do you hate creating a new filesystem type
> > to fix the problems?
> >
>
> I'm still not convinced we can't solve this without adding new options or
> fstypes. I think flags to indicate that we're special and to use a treeid that
> we stuff into the inode would be a reasonable solution. That being said I'm a
> little sleep deprived so I could be missing why my plan is a bad one, so I'm
> willing to be convinced that mount options are the solution to this, but I want
> to make sure we're damned certain that's the best way forward. Thanks,
I don't think "best way forward" is the appropriate goal - impossible to
assess.
What we need is a chosen way forward. Someone - and ultimately that
someone needs to be the BTRFS maintainer team - needs to decide what
breakage they are willing to bear the cost of, and what breakage is
unacceptable to them, and to choose a way to move forward. I cannot
make that decision for you because I'm just an interested bystander. Al
Viro and Linus cannot either, though they are in a position to veto some
decisions.
The current choice appears to be "ignore the problem and hope it goes
away", though I appreciate that appearances can be deceiving.
You appear very keen to preserve as much of the status quo as possible.
Given that, I think you really need to push to get all the procfs files
changed to use the same device number as stat - so push the patch which
SUSE has that add inode_get_dev().
https://github.com/SUSE/kernel-source/blob/master/patches.suse/vfs-add-super_operations-get_inode_dev
(though the change to show_mountinfo() in that patch would need careful consideration).
If that lands, you have a clear way forward, and we can find some
solution for NFSd (and other network filesystems), and for user-space to
use mnt_id.
If you cannot overcome the pushback, then you know you will have to
find another path - make a 64bit inode number unique, or add more bits
to the effective inode number. Or something.
NeilBrown
prev parent reply other threads:[~2021-08-12 22:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 3:55 [PATCH/RFC 0/4] Attempt to make progress with btrfs dev number strangeness NeilBrown
2021-08-09 3:55 ` [PATCH 2/4] btrfs: add numdevs= mount option NeilBrown
2021-08-09 7:50 ` kernel test robot
2021-08-09 3:55 ` [PATCH 1/4] btrfs: include subvol identifier in inode number if -o inumbits= NeilBrown
2021-08-09 3:55 ` [PATCH 4/4] Add "tree" number to "inode" number in various /proc files NeilBrown
2021-08-09 3:55 ` [PATCH 3/4] VFS/btrfs: add STATX_TREE_ID NeilBrown
2021-08-10 20:51 ` [PATCH/RFC 0/4] Attempt to make progress with btrfs dev number strangeness Josef Bacik
2021-08-11 22:13 ` NeilBrown
2021-08-12 13:54 ` Josef Bacik
2021-08-12 14:06 ` Hugo Mills
2021-08-12 22:35 ` NeilBrown [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=162880775121.15074.3288255136681201159@noble.neil.brown.name \
--to=neilb@suse.de \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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 read-only IMAP folder(s) and NNTP newsgroup(s).