All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Holst <tobby@tobby.eu>
To: Kai Krakow <hurikhan77@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Repair broken btrfs raid6?
Date: Tue, 10 Feb 2015 19:18:28 +0100	[thread overview]
Message-ID: <CAGwxe4hVkLKDWWeTVLdZuWNYt8px-CyPMzYiX-Bfs3Sx03mnmQ@mail.gmail.com> (raw)
In-Reply-To: <ntnoqb-jvq.ln1@hurikhan77.spdns.de>

2015-02-10 8:17 GMT+01:00 Kai Krakow <hurikhan77@gmail.com>:
> 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).

Yes, sorry, I didn't post an output of "btrfs filesystem show" - but here it is:

Label: 'tobby-btrfs'  uuid: b689ab76-7ff5-434c-a2c6-03efb45faa46
        Total devices 6 FS bytes used 13.13TiB
        devid    1 size 3.64TiB used 3.28TiB path /dev/mapper/sde_crypt
        devid    2 size 3.64TiB used 3.28TiB path /dev/mapper/sdd_crypt
        devid    3 size 3.64TiB used 3.28TiB path /dev/mapper/sdf_crypt
        devid    4 size 3.64TiB used 3.28TiB path /dev/mapper/sda_crypt
        devid    5 size 3.64TiB used 3.28TiB path /dev/mapper/sdb_crypt
        devid    6 size 3.64TiB used 3.28TiB path /dev/mapper/sdc_crypt
btrfs-progs v3.19-rc2

So there are ~13TiB of data on this raid6 - but like it says it was
"aborted" after 2008 seconds (about half an hour) and ~120GB of data.
Then a "parent transid verify failed" happened, the volume got
unreadable and the scrub was aborted. Until a remount of the btrfs -
and until it happens again...

>
> 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).
>
> --
> Replies to list only preferred.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-02-10 18:18 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
2015-02-13  1:12     ` Kai Krakow
2015-02-10 18:18   ` Tobias Holst [this message]
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=CAGwxe4hVkLKDWWeTVLdZuWNYt8px-CyPMzYiX-Bfs3Sx03mnmQ@mail.gmail.com \
    --to=tobby@tobby.eu \
    --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.