Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: Petr Janecek <janecek@ucw.cz>, <linux-btrfs@vger.kernel.org>
Cc: <dsterba@suse.cz>
Subject: Re: Poll: time to switch skinny-metadata on by default?
Date: Fri, 17 Oct 2014 14:25:32 -0400	[thread overview]
Message-ID: <54415F1C.1060902@fb.com> (raw)
In-Reply-To: <20141017123036.GA8052@atrey.karlin.mff.cuni.cz>

On 10/17/2014 08:30 AM, Petr Janecek wrote:
> Hello,
>
>> the core of skinny-metadata feature has been merged in 3.10 (Jun 2013)
>> and has been reportedly used by many people. No major bugs were reported
>> lately unless I missed them.
>
>    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://urldefense.proofpoint.com/v1/url?u=https://bugzilla.kernel.org/show_bug.cgi?id%3D64961&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cKCbChRKsMpTX8ybrSkonQ%3D%3D%0A&m=3qxE39iiu%2BoZB%2F05dE7hnGHZojWhjjijrtjNYki0NFg%3D%0A&s=b262347a1ad2505ebdcb21dcc9f0944a14c174a1dcf447746ce196faddd99092
>
>

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,

Josef


  reply	other threads:[~2014-10-17 18:25 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 [this message]
2014-10-18 11:21   ` Petr Janecek
2014-10-18 14:04     ` Josef Bacik
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=54415F1C.1060902@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