From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: include device major and minor numbers in the device scan notice
Date: Sun, 25 Feb 2024 12:03:21 +0530 [thread overview]
Message-ID: <a8ded855-c4a0-4357-aeaf-70c6f137ae16@oracle.com> (raw)
In-Reply-To: <7f2d1ad7-3c5c-41e9-a797-895e2ec76ed6@gmx.com>
On 2/24/24 01:27, Qu Wenruo wrote:
>
>
> 在 2024/2/23 21:56, Anand Jain 写道:
>> To better debug issues surrounding device scans, include the device's
>> major and minor numbers in the device scan notice for btrfs.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>
> Reviewed-by: Qu Wenruo <wqu@suse.com>
>
> Maybe you want to expand the device number to all other device name output?
>
> Especially considering the recent device name problem, device
> major/minor looks a much better supplement.
Yeah.. added to all scan related messages.
Thanks, Anand
>
> Thanks,
> Qu
>> ---
>> fs/btrfs/volumes.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index 32312f0de2bb..6db37615a3e5 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -824,13 +824,15 @@ static noinline struct btrfs_device
>> *device_list_add(const char *path,
>>
>> if (disk_super->label[0])
>> pr_info(
>> - "BTRFS: device label %s devid %llu transid %llu %s scanned by %s
>> (%d)\n",
>> +"BTRFS: device label %s devid %llu transid %llu %s(%d:%d) scanned by
>> %s (%d)\n",
>> disk_super->label, devid, found_transid, path,
>> + MAJOR(path_devt), MINOR(path_devt),
>> current->comm, task_pid_nr(current));
>> else
>> pr_info(
>> - "BTRFS: device fsid %pU devid %llu transid %llu %s scanned by %s
>> (%d)\n",
>> +"BTRFS: device fsid %pU devid %llu transid %llu %s(%d:%d) scanned by
>> %s (%d)\n",
>> disk_super->fsid, devid, found_transid, path,
>> + MAJOR(path_devt), MINOR(path_devt),
>> current->comm, task_pid_nr(current));
>>
>> } else if (!device->name || strcmp(device->name->str, path)) {
prev parent reply other threads:[~2024-02-25 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 11:26 [PATCH] btrfs: include device major and minor numbers in the device scan notice Anand Jain
2024-02-23 15:46 ` Filipe Manana
2024-02-25 5:29 ` Anand Jain
2024-02-23 16:12 ` Sweet Tea Dorminy
2024-02-23 16:15 ` Anand Jain
2024-02-23 19:57 ` Qu Wenruo
2024-02-25 6:33 ` Anand Jain [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=a8ded855-c4a0-4357-aeaf-70c6f137ae16@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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