All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: Kai Krakow <hurikhan77@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Repair broken btrfs raid6?
Date: Tue, 10 Feb 2015 08:15:19 -0500	[thread overview]
Message-ID: <486ed2b2-3c80-4856-8701-bcd71a212b18@aei.ca> (raw)
In-Reply-To: <ntnoqb-jvq.ln1@hurikhan77.spdns.de>

On Tuesday, February 10, 2015 2:17:43 AM EST, Kai Krakow wrote:
> Tobias Holst <tobby@tobby.eu> schrieb:
>
>> and "btrfs scrub status /[device]" gives me the following output:
>>> "scrub status for [UUID]
>>> scrub started at Mon Feb  9 18:16:38 2015 and was aborted after 2008
>>> seconds total bytes scrubbed: 113.04GiB with 0 errors"
>
> Does not look very correct to me:
>
> Why should a scrub in a six-drivers btrfs array which is probably multi-
> terabytes big (as you state a restore from backup would take 
> days) take only 
> ~2000 seconds? And scrub only ~120 GB worth of data. Either your 6 devices 
> are really small (then why RAID-6), or your data is very sparse (then way 
> does it take so long), or scrub prematurely aborts and never checks the 
> complete devices (I guess this is it).
>
> And that's what it actually says: "aborted after 2008" seconds. I'd expect 
> "finished after XXXX seconds" if I remember my scrub runs 
> correctly (which I 
> currently don't do regularly because it takes long and IO performance sucks 
> during running it).

IO perfermance does suffer during a scrub.  I use the following:

ionice -c 3 btrfs scrub start -Bd -n 19 /<target>

The combo of -n19 and ionice makes it workable here.  

Tobias why do you think btrfsck does not work on raid6?  It runs fine
here on raid5.




  reply	other threads:[~2015-02-10 13:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 22:45 Repair broken btrfs raid6? Tobias Holst
2015-02-10  3:36 ` Duncan
2015-02-10  7:17 ` Kai Krakow
2015-02-10 13:15   ` Ed Tomlinson [this message]
2015-02-13  1:12     ` Kai Krakow
2015-02-10 18:18   ` Tobias Holst
2015-02-11 14:46 ` Tobias Holst
2015-02-12  9:16   ` Liu Bo
2015-02-12 23:22     ` Tobias Holst
2015-02-13  8:06       ` Liu Bo
2015-02-13 18:26         ` Tobias Holst
2015-02-13 21:54           ` Tobias Holst
2015-02-15  3:30             ` Liu Bo
2015-02-15 20:45               ` Tobias Holst

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=486ed2b2-3c80-4856-8701-bcd71a212b18@aei.ca \
    --to=edt@aei.ca \
    --cc=hurikhan77@gmail.com \
    --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 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.