All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: kreijack@inwind.it, dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RFC] btrfs: pick device with lowest devt for show_devname
Date: Wed, 29 Nov 2023 16:38:11 +0300	[thread overview]
Message-ID: <CAA91j0UMvy0rtW8yr__pfq3LVQ9m7yJdkB0X2p86pn73dEgEBw@mail.gmail.com> (raw)
In-Reply-To: <336d54f8-3a27-a7e9-3482-781559fab709@oracle.com>

On Wed, Nov 29, 2023 at 2:28 AM Anand Jain <anand.jain@oracle.com> wrote:
>
>
> The display-devices-list in /proc/self/mounts method simplifies device
> listing, bypassing the need for sysfs or Btrfs-progs and it replaces the
> lowest-devt approach proposed earlier. And, yeah, all multi-device
> filesystems would need a special case handing in libmount.
>
> Udev's /dev/disk/by-uuid, gets updated upon an (over)write sb event. I
> don't know its updater, it is not in util-linux,  I find no rules in

Today it is 60-persistent-storage.rules which is part of systemd.
Currently the logic makes the last device claiming the same symlink
win. There was PR to keep the first created symlink, but it caused
some regression test failure and was reverted.

> /etc/udev either.
>

Packages install rules in /usr/lib/udev (may be /lib/udev on older
distributions).

  reply	other threads:[~2023-11-29 13:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 11:10 [PATCH RFC] btrfs: pick device with lowest devt for show_devname Anand Jain
2023-11-02 20:26 ` David Sterba
2023-11-02 22:55   ` Anand Jain
2023-11-20 14:42     ` David Sterba
2023-11-24 16:19 ` David Sterba
2023-11-25  1:09   ` Anand Jain
2023-11-27 11:48     ` Anand Jain
2023-11-28  8:00       ` Goffredo Baroncelli
2023-11-28 23:28         ` Anand Jain
2023-11-29 13:38           ` Andrei Borzenkov [this message]
2023-11-29 20:54           ` Goffredo Baroncelli
2023-12-05 17:44             ` David Sterba
2023-12-06 19:52               ` Goffredo Baroncelli
2023-12-05 17:43         ` David Sterba
2023-11-29 21:20 ` Goffredo Baroncelli

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=CAA91j0UMvy0rtW8yr__pfq3LVQ9m7yJdkB0X2p86pn73dEgEBw@mail.gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@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.