From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: RAID1: system stability
Date: Tue, 26 May 2015 14:23:35 +0300 [thread overview]
Message-ID: <556457b8.e72b980a.ee08.ffffce60@mx.google.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 914 bytes --]
Hi list,
I'm regular on this list and I very like btrfs, I want use it on production server, and I want replace hw raid on it.
Test case: server with N scsi discs
2 SAS disks used for raid 1 root fs
If I just remove one disk physically, all okay, kernel show me write errors and system continue work some time. But after first sync call, example
# sync
# dd if=/Dev/zero of=/zero
Kernel will crush and system freeze.
Yes, after reboot, I can mount with degraded and recovery options, and I can add failed disk again, and btrfs will rebuild array.
But kernel crush and reboot expected in this case, or I can skip it? How?
# mount -o remount, degraded -> kernel crush
Insert failed disk again -> kernel crush
May be I missing something? I just want avoid shutdown time or/and reboot =.=ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±ý»k~ÏâØ^nr¡ö¦zË\x1aëh¨èÚ&£ûàz¿äz¹Þú+Ê+zf£¢·h§~Ûiÿÿïêÿêçz_è®\x0fæj:+v¨þ)ߣøm
next reply other threads:[~2015-05-26 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 11:23 Timofey Titovets [this message]
2015-05-26 19:31 ` RAID1: system stability Timofey Titovets
2015-05-26 19:49 ` Chris Murphy
2015-05-26 19:51 ` Timofey Titovets
2015-06-22 11:35 ` Timofey Titovets
2015-06-22 11:45 ` Timofey Titovets
2015-06-22 16:03 ` Chris Murphy
2015-06-22 16:36 ` Timofey Titovets
2015-06-22 16:52 ` Chris Murphy
2015-07-22 11:00 ` Russell Coker
2015-08-05 17:32 ` Austin S Hemmelgarn
2015-08-05 19:00 ` Martin Steigerwald
-- strict thread matches above, loose matches on Subject: below --
2015-06-17 9:20 Timofey Titovets
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=556457b8.e72b980a.ee08.ffffce60@mx.google.com \
--to=nefelim4ag@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