From: thunder7@xs4all.nl
To: linux-raid@vger.kernel.org
Subject: Re: Can't get md array to shut down cleanly
Date: Thu, 6 Jul 2006 21:29:19 +0200 [thread overview]
Message-ID: <20060706192919.GA19446@amd64.of.nowhere> (raw)
In-Reply-To: <bb145bd20607061018u3bf275ads6b602657867cb07d@mail.gmail.com>
From: Christian Pernegger <pernegger@gmail.com>
Date: Thu, Jul 06, 2006 at 07:18:06PM +0200
> >May be your shutdown script is doing "halt -h"? Halting the disk
> >immediately without letting the RAID to settle to a clean state
> >can be the cause?
>
> I'm using Debian as well and my halt script has the fragment you posted.
> Besides, shouldn't the array be marked clean at this point:
>
> >md: stopping all md devices.
>
> Apparently it isn't ... :
>
> >md: md0 still in use.
>
> If someone thinks it might make a difference I could remove everything
> evms and create a "pure" md array with mdadm. (Directly on the disks
> or on partitions? Which partition type?)
>
> How does a "normal" shutdown look?
>
> Will try 2.6.16 and 2.6.15 now ... the boring part is that I have to
> wait for the resync to complete before the next test ...
>
I get these messages too on Debian Unstable, but since enabling the
bitmaps on my devices, resyncing is so fast that I don't even notice it
on booting. Waiting for resync is not happening here. I'm seeing it on
my raid-1 root partition.
Good luck,
Jurriaan
--
Debian (Unstable) GNU/Linux 2.6.17-rc4-mm3 2815 bogomips load 2.02
next prev parent reply other threads:[~2006-07-06 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 13:48 Can't get md array to shut down cleanly Christian Pernegger
2006-07-06 15:46 ` Niccolo Rigacci
2006-07-06 17:18 ` Christian Pernegger
2006-07-06 19:29 ` thunder7 [this message]
2006-07-06 20:24 ` Christian Pernegger
2006-07-06 22:13 ` Neil Brown
2006-07-07 1:07 ` Christian Pernegger
2006-07-07 7:53 ` Neil Brown
2006-07-07 9:25 ` Christian Pernegger
2006-07-07 20:06 ` Christian Pernegger
2006-07-10 15:27 ` Christian Pernegger
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=20060706192919.GA19446@amd64.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-raid@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.