All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 4.14 balance: kernel BUG at /home/kernel/COD/linux/fs/btrfs/ctree.c:1856!
Date: Sat, 18 Nov 2017 13:29:45 +0100	[thread overview]
Message-ID: <909afcf3-3eff-52eb-c679-4e300dd61bda@mendix.com> (raw)
In-Reply-To: <2cbd136b-4fa7-fcee-7472-0941efa97047@mendix.com>

On 11/18/2017 12:48 PM, Hans van Kranenburg wrote:
> 
> So, who wants to help?
> 
> 1. Find a test system that you can crash.
> 2. Create a test filesystem with some data.
> 3. Run with 4.14? (makes the most sense I think)
> 4. Continuously feed the data to balance and send everything to /dev/null
> 5. Collect stack traces and borken filesystem images.

Ok, what I just did:

-# mkfs.btrfs --nodiscard /dev/xvdb
-# mount -o noatime /dev/xvdb /btrfs
-# cd btrfs/
-# btrfs sub create usr
-# rsync -av /usr/ usr/
-# btrfs sub snap -r usr/ usro

And then, both at the same time:

-# while true; do btrfs send usro/ > /dev/null; date; echo 3 >
/proc/sys/vm/drop_caches; done

and

-# while true; do btrfs balance start --full-balance /btrfs; done

After a few minutes we have the first error:


[ 1605.484627] BTRFS error (device xvdb): did not find backref in
send_root. inode=4260, offset=0, disk_byte=130793844736 found
extent=130793844736

Sat Nov 18 13:25:28 CET 2017
At subvol usro/
ERROR: send ioctl failed with -5: Input/output error

No big stack trace this time.

-- 
Hans van Kranenburg

  reply	other threads:[~2017-11-18 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18  0:49 4.14 balance: kernel BUG at /home/kernel/COD/linux/fs/btrfs/ctree.c:1856! Tomasz Chmielewski
2017-11-18  1:08 ` Hans van Kranenburg
2017-11-18  1:15   ` Tomasz Chmielewski
2017-11-18  9:40   ` Roman Mamedov
2017-11-18 10:41     ` waxhead
2017-11-18 11:48     ` Hans van Kranenburg
2017-11-18 12:29       ` Hans van Kranenburg [this message]
2017-11-18 19:11       ` Hans van Kranenburg

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=909afcf3-3eff-52eb-c679-4e300dd61bda@mendix.com \
    --to=hans.van.kranenburg@mendix.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    --cc=rm@romanrm.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.