From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz
Cc: Filipe Manana <fdmanana@kernel.org>,
linux-btrfs@vger.kernel.org, dsterba@suse.com,
aromosan@gmail.com, bernd.feige@gmx.net,
CHECK_1234543212345@protonmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: do not skip re-registration for the mounted device
Date: Fri, 23 Feb 2024 02:37:08 +0530 [thread overview]
Message-ID: <cfbfcc61-deb6-4011-9acb-65fb271b0a61@oracle.com> (raw)
In-Reply-To: <e86a3121-e54c-4975-bcea-507fec8642a8@oracle.com>
>>>> $ ./check btrfs/14[6-9] btrfs/15[8-9]
>>>>
The stale fsid matches the testcase btrfs/146.
Unfortunately, the failure is inconsistent.
I will take another look tomorrow.
Thanks, Anand
>>>> Thanks, with this I can reproduce it and have some ideas what could go
>>>> wrong.
>>>
>>> Thanks indeed.
>>
>> I tested the following, it fixes the fsid problems and has passed full
>> fstests run. The temp-fsid test coverage needs to be done still.
>>
>> @@ -1388,6 +1388,10 @@ struct btrfs_device
>> *btrfs_scan_one_device(const char *path, blk_mode_t flags,
>> if (ret)
>> btrfs_warn(NULL, "lookup bdev failed for path %s: %d",
>> path, ret);
>> + if (devt) {
>> + printk(KERN_ERR "free stale devt (for path %s)\n", path);
>> + btrfs_free_stale_devices(devt, NULL);
>> + }
>
> Right. I had this in mind to check for the stale devices. I'll do.
>
> Anand
next prev parent reply other threads:[~2024-02-22 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 1:13 [PATCH v2] btrfs: do not skip re-registration for the mounted device Anand Jain
2024-02-14 7:16 ` David Sterba
2024-02-20 14:08 ` Filipe Manana
2024-02-20 18:12 ` David Sterba
2024-02-21 16:39 ` Anand Jain
2024-02-21 17:03 ` Anand Jain
2024-02-21 21:49 ` David Sterba
2024-02-22 2:45 ` Anand Jain
2024-02-22 21:07 ` Anand Jain [this message]
2024-03-07 4:13 ` Anand Jain
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=cfbfcc61-deb6-4011-9acb-65fb271b0a61@oracle.com \
--to=anand.jain@oracle.com \
--cc=CHECK_1234543212345@protonmail.com \
--cc=aromosan@gmail.com \
--cc=bernd.feige@gmx.net \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@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