From: Anand Jain <anand.jain@oracle.com>
To: Daniel Pocock <daniel@pocock.pro>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com, dsterba@suse.cz
Subject: Re: disk failure but no alert
Date: Thu, 20 Aug 2015 10:59:46 +0800 [thread overview]
Message-ID: <55D542A2.2020309@oracle.com> (raw)
In-Reply-To: <55D44409.40100@pocock.pro>
> is BtrFs failing to alert?
Yes. Btrfs does not do that. as of now.
Only action that it takes is to put FS into readonly mode. That may
be fine for ext4 kind of FS but its not correct from the btrfs Volume
Manager perspective.
A work in progress at my end to fix that.
> [996932.735110] end_request: critical target error, dev sdd, sector
526344
> [996932.735280] md: super_written gets error=-121, uptodate=0
> [996932.735290] md/raid1:md2: Disk failure on sdd2, disabling device.
> md/raid1:md2: Operation continuing on 1 devices.
MD is a complete volume manager, Btrfs isn't yet.
My recent patch (below), is a step towards that. Its not yet
integrated.
[PATCH 3/3] Btrfs: introduce function to handle device offline
HTH, Anand
prev parent reply other threads:[~2015-08-20 3:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 8:53 disk failure but no alert Daniel Pocock
2015-08-20 2:59 ` Anand Jain [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=55D542A2.2020309@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=daniel@pocock.pro \
--cc=dsterba@suse.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;
as well as URLs for NNTP newsgroup(s).