From: "Chris Murphy" <lists@colorremedies.com>
To: "Btrfs BTRFS" <linux-btrfs@vger.kernel.org>,
"Linux Devel" <linux-fsdevel@vger.kernel.org>
Subject: Re: [BUG] 6.17.0, mount: /mnt/0: fsconfig() failed: File exists.
Date: Sun, 28 Sep 2025 02:27:46 -0400 [thread overview]
Message-ID: <00c4be20-09c8-417e-bbae-e966200d87b9@app.fastmail.com> (raw)
In-Reply-To: <cd1ab2d8-35af-4707-8eee-ced3141d1126@app.fastmail.com>
On Sun, Sep 28, 2025, at 1:53 AM, Chris Murphy wrote:
> Downstream bug includes full dmesg attached:
> https://bugzilla.redhat.com/show_bug.cgi?id=2399959
OK so this is a case of two devices with the same fsid. I simply forgot I had plugged in the original device planning to wipe it - its replacement is a new fs using metadata_uuid, with the original fsid.
But the two identical fsid's is the source of all this confusion, both user and I think the kernel is also confused.
I've added more details to the downstream bug report, including strace.
--
Chris Murphy
prev parent reply other threads:[~2025-09-28 6:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 5:53 [BUG] 6.17.0, mount: /mnt/0: fsconfig() failed: File exists Chris Murphy
2025-09-28 6:27 ` Chris Murphy [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=00c4be20-09c8-417e-bbae-e966200d87b9@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--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 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 NNTP newsgroup(s).