From: Josef Bacik <jbacik@fb.com>
To: Petr Janecek <janecek@ucw.cz>
Cc: <linux-btrfs@vger.kernel.org>, <dsterba@suse.cz>
Subject: Re: Poll: time to switch skinny-metadata on by default?
Date: Sat, 18 Oct 2014 10:04:51 -0400 [thread overview]
Message-ID: <54427383.6050104@fb.com> (raw)
In-Reply-To: <20141018112121.GB17403@atrey.karlin.mff.cuni.cz>
On 10/18/2014 07:21 AM, Petr Janecek wrote:
> Hello,
>
>>> so far I haven't succeeded running btrfs balance on a large
>>> skinny-metadata fs -- segfault, kernel bug, reproducible. No such
>>> problems on ^skinny-metadata fs (same disks, same data). Tried both
>>> several times on 3.17. More info in comments 10,14 in
>>> https://bugzilla.kernel.org/show_bug.cgi?id=64961
>>
>> I can't reproduce this, how big is your home directory, and are you
>> still seeing corruptions after just rsyncing to a clean fs? Thanks,
>
> as I wrote in comment 10, it has improved since year ago when I
> reported it: I see no corruption at all, neither after rsync, nor after
> balance crash: btrfs check doesn't find anything wrong, files look ok.
> The only problem is that after adding a disk the balance segfaults on a
> kernel bug and the fs gets stuck. When I run balance again after
> reboot, it makes only a very small progress and crashes again the same
> way.
>
> There are some 2.5TB of data in 7.5M files on that fs. And couple
> dozen ro snapshots -- I'm testing 3.17 + revert of 9c3b306e1c9e right
> now, but it takes more than day to copy the data and recreate all the
> snapshots. But a test with ^skinny-metadata showed no problems, so I
> don't thing I got bitten by that bug.
>
> I have btrfs-image of one of previous runs after crashed balance.
> It's 15GB. I can place it somewhere with fast link, are you interested?
>
>
Yup, send me the link and I'll pull it down. Thanks,
Josef
next prev parent reply other threads:[~2014-10-18 14:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 12:30 Poll: time to switch skinny-metadata on by default? Petr Janecek
2014-10-17 18:25 ` Josef Bacik
2014-10-18 11:21 ` Petr Janecek
2014-10-18 14:04 ` Josef Bacik [this message]
2014-10-18 15:52 ` Wang Shilong
2014-10-18 15:53 ` Josef Bacik
2014-10-18 16:01 ` Wang Shilong
-- strict thread matches above, loose matches on Subject: below --
2014-10-16 11:33 David Sterba
2014-10-20 16:34 ` David Sterba
2014-10-21 9:29 ` Duncan
2014-10-21 11:02 ` Austin S Hemmelgarn
2014-10-21 12:35 ` Konstantinos Skarlatos
2014-10-21 16:40 ` Rich Freeman
2014-10-22 2:08 ` Duncan
2014-10-22 12:49 ` Dave
2014-10-23 2:41 ` Duncan
2014-10-23 13:37 ` David Sterba
2014-10-23 14:47 ` Tobias Geerinckx-Rice
2014-10-24 1:33 ` Duncan
2014-10-25 12:24 ` Marc Joliet
2014-10-25 19:58 ` Marc Joliet
2014-10-27 1:30 ` Marc Joliet
2014-10-25 20:33 ` Chris Murphy
2014-10-25 20:35 ` Chris Murphy
2014-10-27 1:24 ` Marc Joliet
2014-10-27 7:50 ` Duncan
2014-10-27 4:39 ` Zygo Blaxell
2014-10-27 7:16 ` Duncan
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=54427383.6050104@fb.com \
--to=jbacik@fb.com \
--cc=dsterba@suse.cz \
--cc=janecek@ucw.cz \
--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