From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: Add chunk allocation ENOSPC debug message for enospc_debug mount option
Date: Mon, 22 Jan 2018 10:11:44 +0200 [thread overview]
Message-ID: <3e152104-2a67-5677-dea5-4863de26aa78@suse.com> (raw)
In-Reply-To: <20180122055054.7933-1-wqu@suse.com>
On 22.01.2018 07:50, Qu Wenruo wrote:
> Enospc_debug makes extent allocator to print more debug messages,
> however for chunk allocation, there is no debug message for enospc_debug
> at all.
>
> This patch will add message for the following parts of chunk allocator:
>
> 1) No rw device at all
> Quite rare, but at least output one message for this case.
>
> 2) No enough space for some device
> This debug message is quite handy for unbalanced disks with stripe
> based profiles (RAID0/10/5/6).
>
> 3) Not enough free devices
> This debug message should tell us if current chunk allocator is
> working correctly on minimal device requirement.
>
> Although under most case, we will hit other ENOSPC before we even hit a
> chunk allocator ENOSPC, but such debug info won't help.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> v2:
> Unify all message level to btrfs_debug().
> More meaningful message if we don't have enough device.
> ---
> fs/btrfs/volumes.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index a25684287501..86cae6a15b1e 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -4622,8 +4622,11 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
>
> BUG_ON(!alloc_profile_is_valid(type, 0));
>
> - if (list_empty(&fs_devices->alloc_list))
> + if (list_empty(&fs_devices->alloc_list)) {
> + if (btrfs_test_opt(info, ENOSPC_DEBUG))
> + btrfs_debug(info, "%s: No writable device", __func__);
> return -ENOSPC;
> + }
>
> index = __get_raid_index(type);
>
> @@ -4705,8 +4708,14 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
> if (ret == 0)
> max_avail = max_stripe_size * dev_stripes;
>
> - if (max_avail < BTRFS_STRIPE_LEN * dev_stripes)
> + if (max_avail < BTRFS_STRIPE_LEN * dev_stripes) {
> + if (btrfs_test_opt(info, ENOSPC_DEBUG))
> + btrfs_debug(info,
> + "%s: devid %llu has no free space, have=%llu want=%u",
> + __func__, device->devid, max_avail,
> + BTRFS_STRIPE_LEN * dev_stripes);
> continue;
> + }
>
> if (ndevs == fs_devices->rw_devices) {
> WARN(1, "%s: found more than %llu devices\n",
> @@ -4731,6 +4740,12 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
>
> if (ndevs < devs_increment * sub_stripes || ndevs < devs_min) {
> ret = -ENOSPC;
> + if (btrfs_test_opt(info, ENOSPC_DEBUG)) {
> + btrfs_debug(info,
> + "%s: not enough devices with free space: have=%d minimal required=%d",
nit: s/minimal/minimum
But there is no point in resending just for that, I guess David could
fix it while merging.
> + __func__, ndevs, min(devs_min,
> + devs_increment * sub_stripes));
> + }
> goto error;
> }
>
>
next prev parent reply other threads:[~2018-01-22 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 6:13 [PATCH] btrfs: Add chunk allocation ENOSPC debug message for enospc_debug mount option Qu Wenruo
2018-01-16 13:47 ` Nikolay Borisov
2018-01-17 0:52 ` Qu Wenruo
2018-01-17 16:13 ` Nikolay Borisov
2018-01-22 5:50 ` [PATCH v2] " Qu Wenruo
2018-01-22 8:11 ` Nikolay Borisov [this message]
2018-01-30 13:48 ` 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=3e152104-2a67-5677-dea5-4863de26aa78@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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;
as well as URLs for NNTP newsgroup(s).