From: Anand Jain <anand.jain@oracle.com>
To: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: init device stats for seed devices
Date: Thu, 6 Aug 2020 00:43:54 +0800 [thread overview]
Message-ID: <ccab0e74-196c-2bb9-253e-a7a3af74cd11@oracle.com> (raw)
In-Reply-To: <20200803192308.17977-1-josef@toxicpanda.com>
On 4/8/20 3:23 am, Josef Bacik wrote:
> We recently started recording device stats across the fleet, and noticed
> a large increase in messages such as this
>
> BTRFS warning (device dm-0): get dev_stats failed, not yet valid
>
> on our tiers that use seed devices for their root devices. This is
> because we do not initialize the device stats for any seed devices if we
> have a sprout device and mount using that sprout device.
Thanks for spotting and the fix.
> The basic
> steps for reproducing are
>
> mkfs seed device
> mount seed device
> fill seed device
> umount seed device
> btrfstune -S 1 seed device
> mount seed device
> btrfs device add -f sprout device /mnt/wherever
> umount /mnt/wherever
> mount sprout device /mnt/wherever
> btrfs device stats /mnt/wherever
>
> This will fail with the above message in dmesg.
>
> Fix this by iterating over the fs_devices->seed if they exist in
> btrfs_init_dev_stats. This fixed the problem and properly reports the
> stats for both devices.
>
Also btrfs_run_dev_stats() should be updated to write seed's dev stat
to ondisk.
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
> fs/btrfs/volumes.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index d7670e2a9f39..dab295880117 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -7225,7 +7225,7 @@ int btrfs_init_dev_stats(struct btrfs_fs_info *fs_info)
> path = btrfs_alloc_path();
> if (!path)
> return -ENOMEM;
> -
> +again:
> mutex_lock(&fs_devices->device_list_mutex);
> list_for_each_entry(device, &fs_devices->devices, dev_list) {
> int item_size;
> @@ -7263,6 +7263,12 @@ int btrfs_init_dev_stats(struct btrfs_fs_info *fs_info)
> }
> mutex_unlock(&fs_devices->device_list_mutex);
As we loop through the seed fs_devices. %fs_devices which was
pointing to the sprout fs_devices above, shall point to the seed
fs_devices and so will be holding the seed::device_list_mutex. But
our threads which update the seed device such as replace and delete
are using the sprout::device_list_mutex.
So it should be sprout::device_list_mutex
(fs_info->fs_devices->device_list_mutex).
The loops in btrfs_init_devices_late() and __reada_start_machine()
which are read only, also holds the seed device_list_mutex, I am
sending a patch to fix, after which there isn't any thread which
shall be holding the seed::device_list_mutex when sprout is mounted.
Thanks, Anand
>
> + /* If we have seed devices we need to init those stats as well. */
> + if (fs_devices->seed) {
> + fs_devices = fs_devices->seed;
> + goto again;
> + }
> +
> btrfs_free_path(path);
> return ret < 0 ? ret : 0;
> }
>
next prev parent reply other threads:[~2020-08-05 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 19:23 [PATCH] btrfs: init device stats for seed devices Josef Bacik
2020-08-05 7:45 ` Nikolay Borisov
2020-08-05 16:43 ` Anand Jain [this message]
2020-09-17 15:31 ` 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=ccab0e74-196c-2bb9-253e-a7a3af74cd11@oracle.com \
--to=anand.jain@oracle.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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