From: NeilBrown <neilb@suse.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Hello,Re: GPT Table broken on a Raid1
Date: Thu, 27 Sep 2012 12:43:04 +1000 [thread overview]
Message-ID: <20120927124304.2db38a82@notabene.brown> (raw)
In-Reply-To: <F2C9D196-A5AC-4F35-9177-FDFCA755FB2B@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
On Wed, 26 Sep 2012 13:33:49 -0600 Chris Murphy <lists@colorremedies.com>
wrote:
>
> On Sep 26, 2012, at 6:17 AM, Günther J. Niederwimmer wrote:
> >>
> >> dirty state.
> >
> > OK, I run the Intel Tool in windows two times with the last Tool I found.
> >
> > The Tool don't found any Problem (?) and don't repair, but mdadm….
>
> I'm going to trim this down:
>
> >
> > /dev/sda:
> > [Volume0]:
> > UUID : ec120401:b6ed52e6:3814fac4:48fcf4fc
> > Map State : normal
> > Dirty State : clean
> >
> >
> > /dev/sdb:
> > [Volume0]:
> > UUID : ec120401:b6ed52e6:3814fac4:48fcf4fc
> > Map State : normal
> > Dirty State : dirty
> > °°°°°°°
>
> I don't understand this UI. Are there two Volume0's?
>
> I can see how the dirty state would apply independently among physical devices /dev/sda and /dev/sdb. But the virtual device, the array volume, "Volume0" seems like it would have only one instance. So I don't understand how it can be clean in one case and dirty in another.
>
It just means that when looking at the metadata on /dev/sda, we see it marked
'clean', and when looking at the metadata on /dev/sdb, we see that it is
marked 'dirty'.
Possibly something wrote to Volume0 between these two events, so the volume
got marked 'dirty' so the write could happen. Wait a few seconds and it
should get marked 'clean' again.
Or possibly there is a bug somewhere.
I would open two windows. In one run
watch -d mdadm -E /dev/sda
and in the other run
watch -d mdadm -E /dev/sdb
then access the array, or maybe leave it alone, and see how the metadata
changes with time.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-09-27 2:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 11:03 GPT Table broken on a Raid1 Günther J. Niederwimmer
2012-09-20 2:39 ` Chris Murphy
2012-09-20 11:05 ` Günther J. Niederwimmer
2012-09-20 17:34 ` Chris Murphy
2012-09-21 11:42 ` Günther J. Niederwimmer
2012-09-21 19:35 ` Chris Murphy
2012-09-21 22:43 ` Chris Murphy
2012-09-22 8:37 ` Günther J. Niederwimmer
2012-09-22 18:30 ` Chris Murphy
2012-09-23 6:47 ` Hello,Re: " Günther J. Niederwimmer
2012-09-23 7:17 ` Chris Murphy
2012-09-24 7:28 ` Günther J. Niederwimmer
2012-09-24 17:21 ` Chris Murphy
2012-09-24 19:06 ` Günther J. Niederwimmer
2012-09-24 20:18 ` Chris Murphy
2012-09-24 21:06 ` Günther J. Niederwimmer
2012-09-24 21:12 ` Chris Murphy
2012-09-25 8:27 ` Günther J. Niederwimmer
2012-09-25 9:28 ` John Robinson
2012-09-25 16:55 ` Chris Murphy
2012-09-26 12:17 ` Günther J. Niederwimmer
2012-09-26 19:33 ` Chris Murphy
2012-09-27 2:43 ` NeilBrown [this message]
2012-09-22 15:31 ` John Robinson
2012-09-22 18:45 ` Chris Murphy
2012-09-22 21:58 ` NeilBrown
2012-09-22 22:07 ` John Robinson
2012-09-22 22:30 ` Chris Murphy
2012-09-23 12:00 ` John Robinson
2012-09-23 17:44 ` Chris Murphy
2012-09-23 18:53 ` Chris Murphy
2012-09-24 9:37 ` John Robinson
2012-09-24 17:35 ` Chris Murphy
2012-09-24 18:17 ` Roberto Spadim
[not found] ` <CABYL=ToFtzXv95At54=jSCaD0QVSB+bdxbssda1AMw5gNBqvhg@mail.gmail.com>
2012-09-24 18:55 ` Chris Murphy
2012-09-25 7:33 ` Miquel van Smoorenburg
2012-09-21 21:30 ` Chris Murphy
2012-09-21 21:49 ` 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=20120927124304.2db38a82@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.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 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).