From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: improve messages when devices rescanned
Date: Thu, 3 Sep 2020 12:10:15 +0200 [thread overview]
Message-ID: <20200903101015.GP28318@twin.jikos.cz> (raw)
In-Reply-To: <7d811665-5033-782a-881d-7731f60fecc4@suse.com>
On Thu, Sep 03, 2020 at 12:42:09PM +0300, Nikolay Borisov wrote:
>
>
> On 3.09.20 г. 12:41 ч., Anand Jain wrote:
> > On 3/9/20 4:16 pm, Nikolay Borisov wrote:
> >>
> >>
> >> On 3.09.20 г. 10:27 ч., Anand Jain wrote:
> >>> Systems booting without the initramfs seems to scan an unusual kind
> >>> of device path. And at a later time, the device is updated to the
> >>> correct path. We generally print the process name and PID of the process
> >>> scanning the device but we don't capture the same information if the
> >>> device path is rescanned with a different pathname.
> >>>
> >>> But the current message is too long, so drop the unwanted words and add
> >>> process name and PID.
> >>>
> >>> While at this also update the duplicate device warning to include the
> >>> process name and PID.
> >>>
> >>> Reported-by: https://bugzilla.kernel.org/show_bug.cgi?id=89721
> >>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> >>> ---
> >>> fs/btrfs/volumes.c | 14 ++++++++------
> >>> 1 file changed, 8 insertions(+), 6 deletions(-)
> >>>
> >>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> >>> index dc81646b13c0..c386ad722ae1 100644
> >>> --- a/fs/btrfs/volumes.c
> >>> +++ b/fs/btrfs/volumes.c
> >>> @@ -942,16 +942,18 @@ static noinline struct btrfs_device
> >>> *device_list_add(const char *path,
> >>> bdput(path_bdev);
> >>> mutex_unlock(&fs_devices->device_list_mutex);
> >>> btrfs_warn_in_rcu(device->fs_info,
> >>> - "duplicate device fsid:devid for %pU:%llu old:%s new:%s",
> >>> - disk_super->fsid, devid,
> >>> - rcu_str_deref(device->name), path);
> >>> + "duplicate device %s devid %llu generation %llu scanned by %s
> >>> (%d)",
> >>> + path, devid, found_transid,
> >>> + current->comm,
> >>> + task_pid_nr(current));
> >>> return ERR_PTR(-EEXIST);
> >>> }
> >>> bdput(path_bdev);
> >>> btrfs_info_in_rcu(device->fs_info,
> >>> - "device fsid %pU devid %llu moved old:%s new:%s",
> >>> - disk_super->fsid, devid,
> >>> - rcu_str_deref(device->name), path);
> >>> + "device path %s changed to %s by %s (pid %d)",
> >>> + rcu_str_deref(device->name),
> >>> + path, current->comm,
> >>> + task_pid_nr(current));
> >>
> >> This 2nd messages is misleading, it's not the process calling
> >> device_list_add which have changed the path per-se but rather it sees
> >> the changed path. It's not possible to know why it changed in this
> >> context. The idea here is "
> >>
> >> "Process %pid saw different dev path %new_dev_path for dev %old_path"
> >
> > Hm. How about we stick to the usual scanned by. That is..
> >
> > "device path %s changed to %s scanned by %s (pid %d)",
>
> works for me.
The device id should still be there, the filesystem is referred to by
the device name as printed by btrfs_info* so its uuid can be dropped
from the message itself.
next prev parent reply other threads:[~2020-09-03 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 7:27 [PATCH] btrfs: improve messages when devices rescanned Anand Jain
2020-09-03 8:16 ` Nikolay Borisov
2020-09-03 9:41 ` Anand Jain
2020-09-03 9:42 ` Nikolay Borisov
2020-09-03 10:10 ` David Sterba [this message]
2020-09-03 13:30 ` [PATCH v2] " Anand Jain
2020-09-07 19:39 ` David Sterba
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=20200903101015.GP28318@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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