From: Anand Jain <Anand.Jain@oracle.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Monitoring for disk failures
Date: Tue, 28 Jan 2014 17:15:29 +0800 [thread overview]
Message-ID: <52E77531.9060600@oracle.com> (raw)
In-Reply-To: <pan$2540$a024a2e$1649dd5d$60e61fd@cox.net>
> Without actually trying it here... I believe by default that'd update
> only when there was an I/O error.
>
> Did you try btrfs filesystem show --all-devices? That scans differently.
That will show missing with its own probes but kernel does not
know that disk is missing.
> If that doesn't work try btrfs device scan first as that updates the in-
> kernel list, then filesystem show.
Nope. Scan does not remove the old (missing disk) entries,
I am writing patch(es)..
> Alternatively, monitor the kernel log
> for output as the scanned devices show up there.
Thats the best choice as of now OR btrfs fi show -d will
show missing
Thanks, Anand
next prev parent reply other threads:[~2014-01-28 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 11:43 Monitoring for disk failures Alin Dobre
2014-01-27 13:10 ` Duncan
2014-01-28 9:15 ` Anand Jain [this message]
2014-01-28 9:03 ` Anand Jain
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=52E77531.9060600@oracle.com \
--to=anand.jain@oracle.com \
--cc=1i5t5.duncan@cox.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).