From: Arne Jansen <sensille@gmx.net>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs raid health status
Date: Mon, 02 May 2011 16:20:51 +0200 [thread overview]
Message-ID: <4DBEBDC3.1080003@gmx.net> (raw)
In-Reply-To: <BANLkTimePgK+NGUnBpdgaB+NWGSo8sp3ig@mail.gmail.com>
On 02.05.2011 15:13, Roman Kapusta wrote:
> I have unmounted and again mounted btrfs filesystem, now I can see
> errors in dmesg.
> Is there also some error/health summary, like in btrfs fi show?
There is no error accounting or reparing yet, but you can check out the
scrub patches. They'll read and repair (if there's a second copy
available) all on-disk data. You can pull it here:
git://git.kernel.org/pub/scm/linux/kernel/git/arne/btrfs-unstable-arne.git
scrub
and
git://git.kernel.org/pub/scm/linux/kernel/git/arne/btrfs-progs-unstable-arne.git
scrub
-Arne
>
> On Mon, May 2, 2011 at 15:07, Roman Kapusta <roman.kapusta@gmail.com> wrote:
>> I'm playing with mkfs.btrfs -m raid1 -d raid1. I put som data there
>> and now I write random data on one of physical disks directly.
>>
>> Filesystem and file contents looks fine but I cannot see any errors,
>> is there any way to see that one disk from raid1 is failing?
>>
>> Thanks
>>
>> Roman Kapusta
>>
> --
> 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
prev parent reply other threads:[~2011-05-02 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 13:07 btrfs raid health status Roman Kapusta
2011-05-02 13:13 ` Roman Kapusta
2011-05-02 14:20 ` Arne Jansen [this message]
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=4DBEBDC3.1080003@gmx.net \
--to=sensille@gmx.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).