Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: raid56: do extra dumping for CONFIG_BTRFS_ASSERT
Date: Wed, 15 May 2024 17:53:55 +0200	[thread overview]
Message-ID: <20240515155355.GN4449@twin.jikos.cz> (raw)
In-Reply-To: <9841445a77c4721b7f5c92e642f7e1abf8689d8a.1715744555.git.wqu@suse.com>

On Wed, May 15, 2024 at 01:14:01PM +0930, Qu Wenruo wrote:
> There are several hard-to-hit ASSERT()s hit inside raid56.
> Unfortunately the ASSERT() expression is a little complex, and except
> the ASSERT(), there is nothing to provide any clue.
> 
> Considering if race is involved, it's pretty hard to reproduce.
> Meanwhile sometimes the dump of the rbio structure can provide some
> pretty good clues, it's worthy to do the extra multi-line dump for
> btrfs raid56 related code.
> 
> The dump looks like this:
> 
>  BTRFS critical (device dm-3): bioc logical=4598530048 full_stripe=4598530048 size=0 map_type=0x81 mirror=0 replace_nr_stripes=0 replace_stripe_src=-1 num_stripes=5
>  BTRFS critical (device dm-3):     nr=0 devid=1 physical=1166147584
>  BTRFS critical (device dm-3):     nr=1 devid=2 physical=1145176064
>  BTRFS critical (device dm-3):     nr=2 devid=4 physical=1145176064
>  BTRFS critical (device dm-3):     nr=3 devid=5 physical=1145176064
>  BTRFS critical (device dm-3):     nr=4 devid=3 physical=1145176064
>  BTRFS critical (device dm-3): rbio flags=0x0 nr_sectors=80 nr_data=4 real_stripes=5 stripe_nsectors=16 scrubp=0 dbitmap=0x0
>  BTRFS critical (device dm-3): logical=4598530048
>  assertion failed: orig_logical >= full_stripe_start && orig_logical + orig_len <= full_stripe_start + rbio->nr_data * BTRFS_STRIPE_LEN, in fs/btrfs/raid56.c:1702
>  ------------[ cut here ]------------
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>

Please add the patch to for-next so we can start getting more info from
the crashes, thanks.

  parent reply	other threads:[~2024-05-15 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  3:44 [PATCH v2] btrfs: raid56: do extra dumping for CONFIG_BTRFS_ASSERT Qu Wenruo
2024-05-15  9:59 ` Filipe Manana
2024-05-15 15:53 ` David Sterba [this message]
2024-05-15 18: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=20240515155355.GN4449@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --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