linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Matthias Bodenbinder <matthias@bodenbinder.de>,
	linux-btrfs@vger.kernel.org
Subject: Re: Question: raid1 behaviour on failure
Date: Wed, 20 Apr 2016 21:32:15 +0800	[thread overview]
Message-ID: <571784DF.3060800@oracle.com> (raw)
In-Reply-To: <nf73cv$7vh$1@ger.gmane.org>



> 1. mount the raid1 (2 disc with different size)

> 2. unplug the biggest drive (hotplug)

   Btrfs won't know that you have plugged-out a disk.
   Though it experiences IO failures, it won't close the bdev.

> 3. try to copy something to the degraded raid1

   This will work as long as you do _not_ run unmount/mount.

   However once you umount/mount you won't be able to mount
   even with -o degraded option. (there are some workaround
   patches in the ML)

> 4. plugin the device again (hotplug)

   This is a bad test case.

   - Since btrfs didn't close the device, at #2 above, the block
   layer will create a new device instance and path when you plug-in
   the device.

   And when btrfs will promptly scan the device and update its
   records. But note that its still using the old bdev. And
   you will continue to see the IO errors. And no IO will go
   to the new device instance.

   There are patches in the ML under tests which will force
   close the device upon loosing access to the device. As a
   first step.



  parent reply	other threads:[~2016-04-20 13:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  5:06 Question: raid1 behaviour on failure Matthias Bodenbinder
2016-04-18  7:22 ` Qu Wenruo
2016-04-20  5:17   ` Matthias Bodenbinder
2016-04-20  7:25     ` Qu Wenruo
2016-04-21  5:22       ` Matthias Bodenbinder
2016-04-21  5:43         ` Qu Wenruo
2016-04-21  6:02           ` Liu Bo
2016-04-21  6:09             ` Qu Wenruo
2016-04-21 17:40           ` Matthias Bodenbinder
2016-04-22  6:02             ` Qu Wenruo
2016-04-23  7:07               ` Matthias Bodenbinder
2016-04-23  7:17                 ` Matthias Bodenbinder
2016-04-26  8:17                 ` Satoru Takeuchi
2016-04-26 15:16                 ` Henk Slager
2016-04-20 13:32     ` Anand Jain [this message]
2016-04-21  5:15       ` Matthias Bodenbinder
2016-04-21  7:19         ` Anand Jain
2016-04-21  6:23     ` Satoru Takeuchi
2016-04-21 11:09       ` Austin S. Hemmelgarn
2016-04-21 11:28       ` Henk Slager
2016-04-21 17:27         ` Matthias Bodenbinder
2016-04-26 16:19           ` Henk Slager
2016-04-26 16:42             ` Holger Hoffstätte
2016-04-28  5:12               ` Matthias Bodenbinder
2016-04-28  5:24                 ` Gareth Pye
2016-04-28  8:08                   ` Duncan
2016-04-28  5:09             ` Matthias Bodenbinder
2016-04-28 19:14               ` Henk Slager
     [not found]       ` <57188534.1070408@jp.fujitsu.com>
2016-04-21 11:58         ` Qu Wenruo
2016-04-22  2:21           ` Satoru Takeuchi
2016-04-22  5:32             ` Qu Wenruo
2016-04-22  6:17               ` Satoru Takeuchi

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=571784DF.3060800@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=matthias@bodenbinder.de \
    /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).