Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Device for root volume appears as '/dev/root', 7.3-rc1 regression
Date: Thu, 3 Sep 2026 12:25:42 +0000	[thread overview]
Message-ID: <dfbe1e27-dab8-4d55-8cf3-0b28eeac5df4@gmail.com> (raw)

Hello.

I initially reported this in https://lore.kernel.org/linux-btrfs/018a9738-1d4a-43a0-9352-a56d1e541364@gmail.com/, but haven't got any ack, so assume my message was overlooked.
That patch introduced a regression for me in 7.3-rc1. I'll duplicate full report here.

Device for root volume appears as '/dev/root' now instead of the actual '/dev/sdX' device, but the '/dev/root' path itself doesn't exist.
That causes confusion for userspace applications and leads to variety of problems, like

udisksd[1728]: Error statting /dev/root: No such file or directory

Interesting that the 'mount' command doesn't reflect that, but you can see it in other ways.

$ df
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/root      243931136 3044560 240085792   2% /

$ cat /proc/self/mountinfo
21 1 0:19 /@arch / rw,noatime shared:1 - btrfs /dev/root rw,compress-force=zstd:3,ssd,flushoncommit,discard=async,space_cache=v2,subvolid=256,subvol=/@arch

Reverting this change (mainline commit 108cc873398932af589c295f78c348513b8d70d9) fixes the issue.

$ df
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sda2      243931136 3044336 240085984   2% /

$ cat /proc/self/mountinfo
21 1 0:19 /@arch / rw,noatime shared:1 - btrfs /dev/sda2 rw,compress-force=zstd:3,ssd,flushoncommit,discard=async,space_cache=v2,subvolid=256,subvol=/@arch


             reply	other threads:[~2026-09-03 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 12:25 Hanabishi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-04 15:56 Device for root volume appears as '/dev/root', 7.3-rc1 regression kocelfc
2026-09-04 16:33 ` Hanabishi

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=dfbe1e27-dab8-4d55-8cf3-0b28eeac5df4@gmail.com \
    --to=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox