linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Add enospc_debug printing in metadata_reserve_bytes
Date: Fri, 15 Dec 2017 19:36:47 +0800	[thread overview]
Message-ID: <67c2425e-c182-4223-fd04-603fade3bead@gmx.com> (raw)
In-Reply-To: <1513332337-7068-1-git-send-email-nborisov@suse.com>


[-- Attachment #1.1: Type: text/plain, Size: 1392 bytes --]



On 2017年12月15日 18:05, Nikolay Borisov wrote:
> Currently when enoscp_debug mount option is turned on we do not print
> any debug info in case metadata reservation failures happen. Fix this
> by adding the necessary hook in reserve_metadata_bytes.

Reviewed-by: Qu Wenruo <wqu@suse.com>

> 
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
>  fs/btrfs/extent-tree.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 4497f937e8fb..7a281fc97bc5 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -5382,10 +5382,15 @@ static int reserve_metadata_bytes(struct btrfs_root *root,
>  		    !block_rsv_use_bytes(global_rsv, orig_bytes))
>  			ret = 0;
>  	}
> -	if (ret == -ENOSPC)
> +	if (ret == -ENOSPC) {
>  		trace_btrfs_space_reservation(fs_info, "space_info:enospc",
>  					      block_rsv->space_info->flags,
>  					      orig_bytes, 1);

Nothing related to this patch itself.

But btrfs_space_reservation() seems to be abused.
Every type from delalloc to enospc debug will use it.

What about splitting them into different trace events?

Thanks,
Qu

> +
> +		if (btrfs_test_opt(fs_info, ENOSPC_DEBUG))
> +			dump_space_info(fs_info, block_rsv->space_info,
> +					orig_bytes, 0);
> +	}
>  	return ret;
>  }
>  
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]

  reply	other threads:[~2017-12-15 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 10:05 [PATCH] btrfs: Add enospc_debug printing in metadata_reserve_bytes Nikolay Borisov
2017-12-15 11:36 ` Qu Wenruo [this message]
2017-12-15 11:41   ` Nikolay Borisov
2018-02-05 16:20 ` Nikolay Borisov
2018-02-06  1:29   ` Qu Wenruo
2018-02-06  9:18     ` Nikolay Borisov
2018-02-14 13:13       ` 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=67c2425e-c182-4223-fd04-603fade3bead@gmx.com \
    --to=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).