From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Monitoring for disk failures
Date: Mon, 27 Jan 2014 13:10:53 +0000 (UTC) [thread overview]
Message-ID: <pan$2540$a024a2e$1649dd5d$60e61fd@cox.net> (raw)
In-Reply-To: 52E64665.5020109@elastichosts.com
Alin Dobre posted on Mon, 27 Jan 2014 11:43:33 +0000 as excerpted:
> I am trying to create a very simple script that would alert in case of
> disk failures from a RAID Btrfs.
>
> Digging into the code, I have noticed that the "btrfs fi sh" command
> should display a warning if there is a missing disk. However, testing in
> a Qemu, I used "drive_del" via QMP to remove a "live" SCSI drive,
> already mounted as part of a RAID10 array, the "fi sh" command still
> gave no indication that the drive is missing. Then, I tried removing a
> scsi disk from the host via "echo 1 >/sys/block/sdX/device/delete" to
> actually make the kernel SCSI host forget about it, and "fi sh" still
> doesn't show anything.
>
> I have tested using btrfs-progs v3.12 and kernel 3.13.0.
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.
If that doesn't work try btrfs device scan first as that updates the in-
kernel list, then filesystem show. Alternatively, monitor the kernel log
for output as the scanned devices show up there.
And if /that/ doesn't work, try show, followed by a probe of all the
devices listed by show. But I strongly suspect a device scan will force
the update you're looking for.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-01-27 13:11 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 [this message]
2014-01-28 9:15 ` Anand Jain
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='pan$2540$a024a2e$1649dd5d$60e61fd@cox.net' \
--to=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 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.