linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/relocation.c:2255!
Date: Wed, 9 Oct 2013 12:01:27 -0400	[thread overview]
Message-ID: <20131009160127.GF16461@localhost.localdomain> (raw)
In-Reply-To: <20131009155323.GA11404@dhcp-13-216.nay.redhat.com>

On Wed, Oct 09, 2013 at 11:53:23PM +0800, Eryu Guan wrote:
> Hi all,
> 
> I hit a BUG_ON while playing with btrfs balance. Kernel is
> 3.12-rc4.
> 
> The reproducer is a script doing subvolume create/mount/umount/delete
> in loop at back ground and do balance at the same time.
> 
> It's reproducable everytime. And seems like this is a regression, I
> cannot reproduce it on 3.10 kernel. (I'll write a test case for
> xfstests.)
> 
> Reproducer:
> 
> # cat test.sh
> #!/bin/bash
> 
> btrfs_dev=$1
> btrfs_mnt=$2
> pid=$$
> subvol_mnt=/mnt/subvol_$pid
> 
> mkdir -p $subvol_mnt
> 
> trap "umount $subvol_mnt; btrfs sub del $btrfs_mnt/sub_$pid; rmdir $subvol_mnt; exit 0" 0 1 2 3 15
> 
> while true;do
>         btrfs subvolume create $btrfs_mnt/sub_$pid
>         mount -o subvol=sub_$pid $btrfs_dev $subvol_mnt
>         umount $subvol_mnt
>         btrfs subvolume delete $btrfs_mnt/sub_$pid
> done
> 
> and do
> 
> # mkfs -t btrfs -f /dev/loop0 /dev/loop1
> # mount /dev/loop0 /mnt/btrfs
> # ./test.sh /dev/loop0 /mnt/btrfs >/dev/null &
> # btrfs fi balance /mnt/btrfs
> 

Fixed by Miao's patches in btrfs-next.  Thanks,

Josef

      reply	other threads:[~2013-10-09 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 15:53 kernel BUG at fs/btrfs/relocation.c:2255! Eryu Guan
2013-10-09 16:01 ` Josef Bacik [this message]

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=20131009160127.GF16461@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=guaneryu@gmail.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;
as well as URLs for NNTP newsgroup(s).