From: NeilBrown <neilb@suse.de>
To: Ram Ramesh <rramesh2400@gmail.com>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Is it safe to shutdown while mdadm --grow is in progress.
Date: Sun, 12 Oct 2014 19:35:55 +1100 [thread overview]
Message-ID: <20141012193555.69907c13@notabene.brown> (raw)
In-Reply-To: <543A15A6.5010508@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
On Sun, 12 Oct 2014 00:46:14 -0500 Ram Ramesh <rramesh2400@gmail.com> wrote:
> I googled this topic and got differing answers. Some old ones report
> horror stories and others suggest rebuild continues after reboot
> normally. My array is rebuilding and it will take about 6 days to
> complete. I am expecting bad weather in a couple of days and would like
> to proactively shutdown the machine and reboot. Is this safe?
>
> If the information is already available in a clear manner, please let me
> know.
>
> uname: Linux xxx 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> mdadm - v3.2.5 - 18th May 2012
>
> Thanks for your help
>
It is certainly designed to be safe and my experience is that it is.
However it is difficult to test all corner cases so it is not impossible that
someone what quite work right.
If something does go wrong:
1/ don't panic
2/ don't try to --create the array to fix it
3/ report all details to this list and I'm 99.9% sure I can get your array
running again with all your data safe.
But I suspect it won't come to that.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-10-12 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 5:46 Is it safe to shutdown while mdadm --grow is in progress Ram Ramesh
2014-10-12 8:35 ` NeilBrown [this message]
2014-10-12 16:00 ` Ram Ramesh
2014-10-12 22:15 ` NeilBrown
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=20141012193555.69907c13@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=rramesh2400@gmail.com \
/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.