All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Anand Jain <anand.jain@oracle.com>,
	"erpo41@gmail.com" <erpo41@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: RAID1 storage server won't boot with one disk missing
Date: Thu, 17 Sep 2015 19:00:08 +0200	[thread overview]
Message-ID: <55FAF198.2060106@libero.it> (raw)
In-Reply-To: <55FAD9CC.5060206@oracle.com>

Hi Anand,


On 2015-09-17 17:18, Anand Jain wrote:
>  it looks like -o degraded is going to be a very obvious feature,
>  I have plans of making it a default feature, and provide -o
>  nodegraded feature instead. Thanks for comments if any.
> 
> Thanks, Anand

I am not sure if there is a "good" default for this kind of problem; there are several aspects:

- remote machine:
for a remote machine, I think that the root filesystem should be mounted anyway. For a secondary filesystem (home ?), may be that an user intervention could be better (but without home, how an user could log?).

- spare:
in case of a degraded filesystem, the system could insert a spare disk; or a reshaping could be started (raid5->raid1, raid6->raid5)

- initramfs:
this is the most complicated things: currently most initramfs don't mount the filesystem if all the volumes aren't available. Allowing a degraded root filesystem means:
	a) wait for the disks until a timeout
	b) if the timeout expires, mount in degraded mode (inserting a spare disk if available ?)
	c) otherwise mount the filesystem as usual

- degraded:
I think that there are different level of degraded. For example, in case of raid6 a missing device could be acceptable; however in case of a raid5, this should be not allowed; and an user intervention may be preferred.


In the past I suggested the use of an helper, mount.btrfs [1], which could handle all these cases better without a kernel intervention:
- wait for the devices to appear
- verifying if all the needed devices are present 
- mounting the filesystem passing
     - all the devices to the kernel (without relying to udev and btrfs dev scan...)
     - allowing the degraded mode or not                     (policy)
     - starting an insertion of the spare                    (policy)

G.Baroncelli

[1] http://www.spinics.net/lists/linux-btrfs/msg39706.html


-- 
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  parent reply	other threads:[~2015-09-17 17:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 23:56 RAID1 storage server won't boot with one disk missing erpo41
2015-09-17 15:18 ` Anand Jain
2015-09-17 15:42   ` Chris Murphy
2015-09-17 17:00   ` Goffredo Baroncelli [this message]
2015-09-17 19:02     ` Roman Mamedov
2015-09-17 20:18       ` Chris Murphy
2015-09-18 13:29         ` Austin S Hemmelgarn
2015-09-21 20:00     ` Erkki Seppala
2015-09-18  1:36   ` Duncan
2015-09-18  3:02     ` Gareth Pye
2015-09-21 20:35       ` Erkki Seppala
2015-09-22  5:12         ` Duncan
2015-09-22 11:32         ` Austin S Hemmelgarn
2015-09-22 12:51           ` Qu Wenruo
2015-09-22 13:21             ` Austin S Hemmelgarn
2015-09-22 18:35               ` Chris Murphy
2015-09-22 19:45                 ` Austin S Hemmelgarn
2015-09-17 15:26 ` Chris Murphy

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=55FAF198.2060106@libero.it \
    --to=kreijack@libero.it \
    --cc=anand.jain@oracle.com \
    --cc=erpo41@gmail.com \
    --cc=kreijack@inwind.it \
    --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.