From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at linux-4.2.0/fs/btrfs/extent-tree.c:1833 on rebalance
Date: Wed, 16 Sep 2015 20:18:56 +0000 (UTC) [thread overview]
Message-ID: <pan$5599c$cb01bfb8$910004c8$d38ea6b6@cox.net> (raw)
In-Reply-To: 0973de930ee87e102c533c719807b748@all.all
Stéphane Lesimple posted on Wed, 16 Sep 2015 15:04:20 +0200 as excerpted:
> Le 2015-09-16 12:46, Holger Hoffstätte a écrit :
>>
>> In that case the "crossing stripe boundary" messages are false
>> positives in btrfs-progs-4.2:
>> http://www.spinics.net/lists/linux-btrfs/msg47059.html
>>
>> This should be fixed in the next release.
Thanks for reminding me of that, Holger. I think I was too sleepy when I
read it on-list, and forgot about it...
> Out of curiosity I compiled the btrfs-progs-4.2 release patched with the
> diff you're referencing to fix the off-by-one error, and ran a btrfsck
> again.
> Indeed those errors disappear and my filesystem seems clean in this
> regard. I also disabled quota because it has almost for sure nothing to
> do with the bug, and now btrsfck is 100% happy:
Yes. Quotas have been a continuing issue on btrfs. AFAIK, they're on
the third rewrite now, and still have some bugs to work out. So what
I've been recommending is unless you're (a) directly and specifically
working with the devs to find and fix the quota issues (in which case
please keep at it! =:^), either you (b) really depend on quotas working
and btrfs isn't appropriate for you at this time, since they're known to
be buggy, so use a more mature filesystem where they're known to work, or
(c) you don't actually need quotas at all, so disable them and remove the
quota tracking metadata, thus avoiding the bugs in the feature entirely.
=:^)
(Agreed with your conclusions and nothing to add to the rest of your
message, so omitted here.)
--
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
next prev parent reply other threads:[~2015-09-16 20:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 11:46 kernel BUG at linux-4.2.0/fs/btrfs/extent-tree.c:1833 on rebalance Stéphane Lesimple
2015-09-15 14:47 ` Stéphane Lesimple
2015-09-15 14:56 ` Josef Bacik
2015-09-15 21:47 ` Stéphane Lesimple
2015-09-16 5:02 ` Duncan
2015-09-16 10:28 ` Stéphane Lesimple
2015-09-16 10:46 ` Holger Hoffstätte
2015-09-16 13:04 ` Stéphane Lesimple
2015-09-16 20:18 ` Duncan [this message]
2015-09-16 20:41 ` Stéphane Lesimple
2015-09-17 3:03 ` Qu Wenruo
2015-09-17 6:11 ` Stéphane Lesimple
2015-09-17 6:42 ` Qu Wenruo
2015-09-17 8:02 ` Stéphane Lesimple
2015-09-17 8:11 ` Qu Wenruo
2015-09-17 10:08 ` Stéphane Lesimple
2015-09-17 10:41 ` Qu Wenruo
2015-09-17 18:47 ` Stéphane Lesimple
2015-09-18 0:59 ` Qu Wenruo
2015-09-18 7:36 ` Stéphane Lesimple
2015-09-18 10:15 ` Stéphane Lesimple
2015-09-18 10:26 ` Stéphane Lesimple
2015-09-20 1:22 ` Qu Wenruo
2015-09-20 10:35 ` Stéphane Lesimple
2015-09-20 10:51 ` Qu Wenruo
2015-09-20 11:14 ` Stéphane Lesimple
2015-09-22 1:30 ` Stéphane Lesimple
2015-09-22 1:37 ` Qu Wenruo
2015-09-22 7:34 ` Stéphane Lesimple
2015-09-22 8:40 ` Qu Wenruo
2015-09-22 8:51 ` Qu Wenruo
2015-09-22 14:31 ` Stéphane Lesimple
2015-09-23 7:03 ` Qu Wenruo
2015-09-23 9:40 ` Stéphane Lesimple
2015-09-23 10:13 ` Qu Wenruo
2015-09-17 6:29 ` Stéphane Lesimple
2015-09-17 7:54 ` Stéphane Lesimple
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$5599c$cb01bfb8$910004c8$d38ea6b6@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).