From: thunder7@xs4all.nl
To: Chris Fanning <christopher.fanning@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: not resyncing after power cut.
Date: Mon, 21 May 2007 22:03:25 +0200 [thread overview]
Message-ID: <20070521200324.GB21027@amd64.of.nowhere> (raw)
In-Reply-To: <215ff4410705210808g779ba32dhee018f0bd81382d8@mail.gmail.com>
From: Chris Fanning <christopher.fanning@gmail.com>
Date: Mon, May 21, 2007 at 05:08:47PM +0200
> Hi,
>
> I've got a couple of doubts.
>
> Since more than a year ago I setup mdadm raid1 on new instalations
> (thanks for your work).
> On the older machines, mdadm -D shows them in a dirty state. I know
> that this is/was as expected. If there is a power cut, the machine
> boots and a dirty array is resynced, ¿right?
>
> On newer installations, mdadm -D shows arrays in a clean state. I had
> always thought that this was ok becuase I'd read somewhere that the
> term 'dirty' was causing confusion and it got changed.
> So, state: clean, is what I should expect?
>
If the newer machines have bitmaps on, the resync is generally faster
than finishing booting - so when you can log in, the array is clean
again.
Do they use bitmaps?
Kind regards,
Jurriaan
--
Look - either dualism sucks, or it doesn't.
Debian (Unstable) GNU/Linux 2.6.21-mm2 2x4021 bogomips load load 3.73
the Jack Vance Integral Edition: http://www.integralarchive.org
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-05-21 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 15:08 not resyncing after power cut Chris Fanning
2007-05-21 20:03 ` thunder7 [this message]
2007-05-22 9:10 ` Neil Brown
2007-05-22 10:21 ` Chris Fanning
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=20070521200324.GB21027@amd64.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=christopher.fanning@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox