linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: hitting BUG_ON on troublesome FS
Date: Tue, 4 Feb 2014 06:21:11 +0000 (UTC)	[thread overview]
Message-ID: <pan$e1dcf$78ef7ada$46bc0f01$840ccb1c@cox.net> (raw)
In-Reply-To: CCAC08D7-4639-40F4-85DD-459E6D795DAD@yerf-it.com

Remco Hosman - Yerf-it.com posted on Mon, 03 Feb 2014 21:51:26 +0100 as
excerpted:

> Anything i can do to resolve / debug the issue?

I see from the trace you're running kernel 3.13.0.  (FWIW 3.13.1 is out, 
but there weren't any btrfs commits therein, as they weren't upstream in 
3.14-pre yet at that time.)

You might try kernel 3.14-rc1 now that it's out.  There's a big btrfs git 
pull in that, including a number of btrfs send/receive fixes.  FWIW, 
btrfs send/receive seems to be a big focus right now, and I see a lot of 
patches floating by on the list even after that pull, so there's more 
where those came from.

I'm not a dev (just another btrfs user and list regular for several 
kernel cycles now) and haven't followed the patches closely enough to 
know if your particular balance problem is covered in one of them, but as 
I said, since 3.14-rc1 is out now, you might as well try it...

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-02-04  6:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 20:51 hitting BUG_ON on troublesome FS Remco Hosman - Yerf-it.com
2014-02-04  6:21 ` Duncan [this message]
2014-02-04 19:12 ` Remco Hosman - Yerf-it.com
2014-02-04 21:48 ` Josef Bacik
2014-02-05  6:35   ` Remco Hosman - Yerf-it.com
     [not found]   ` <50C9BA7F-4988-4765-963C-20B241A13C84@yerf-it.com>
2014-02-05 14:22     ` Josef Bacik

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='pan$e1dcf$78ef7ada$46bc0f01$840ccb1c@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).