From: Roman Kapusta <roman.kapusta@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs raid health status
Date: Mon, 2 May 2011 15:13:33 +0200 [thread overview]
Message-ID: <BANLkTimePgK+NGUnBpdgaB+NWGSo8sp3ig@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikkK=Y7yZ5u_mH7AQTkV_sd9u0FiQ@mail.gmail.com>
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?
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
>
next prev parent reply other threads:[~2011-05-02 13:13 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 [this message]
2011-05-02 14:20 ` Arne Jansen
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=BANLkTimePgK+NGUnBpdgaB+NWGSo8sp3ig@mail.gmail.com \
--to=roman.kapusta@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 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).