From: Petr Vyskocil <petr@anime.cz>
To: linux-raid@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.17 and RAID5 Grow Problem (critical section backup)
Date: Tue, 11 Jul 2006 11:05:59 +0200 [thread overview]
Message-ID: <e8vplt$fgv$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0607110950450.30961@yvahk01.tjqt.qr>
>>> Hm, what's superblock 0.91? It is not mentioned in mdadm.8.
>>>
>> Not sure, the block version perhaps?
>>
> Well yes of course, but what characteristics? The manual only lists
> 0, 0.90, default
> 1, 1.0, 1.1, 1.2
> No 0.91 :(
AFAICR superblock version gets raised by 0.01 for the duration of
reshape, so that non-reshape aware kernels do not try to assemble it
(and cause data corruption).
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vyskocil <petr@anime.cz>
To: linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Subject: Re: Kernel 2.6.17 and RAID5 Grow Problem (critical section backup)
Date: Tue, 11 Jul 2006 11:05:59 +0200 [thread overview]
Message-ID: <e8vplt$fgv$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0607110950450.30961@yvahk01.tjqt.qr>
>>> Hm, what's superblock 0.91? It is not mentioned in mdadm.8.
>>>
>> Not sure, the block version perhaps?
>>
> Well yes of course, but what characteristics? The manual only lists
> 0, 0.90, default
> 1, 1.0, 1.1, 1.2
> No 0.91 :(
AFAICR superblock version gets raised by 0.01 for the duration of
reshape, so that non-reshape aware kernels do not try to assemble it
(and cause data corruption).
Petr
next prev parent reply other threads:[~2006-07-11 9:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 12:38 Kernel 2.6.17 and RAID5 Grow Problem (critical section backup) Justin Piszcz
2006-07-07 12:46 ` Justin Piszcz
2006-07-07 12:49 ` Justin Piszcz
2006-07-07 12:49 ` Justin Piszcz
2006-07-07 14:37 ` Justin Piszcz
2006-07-07 19:04 ` Justin Piszcz
2006-07-07 19:42 ` Justin Piszcz
2006-07-07 22:00 ` Neil Brown
2006-07-07 22:15 ` Justin Piszcz
2006-07-07 22:31 ` Neil Brown
2006-07-07 22:35 ` Justin Piszcz
2006-07-07 22:38 ` Neil Brown
2006-07-07 22:39 ` Justin Piszcz
2006-07-10 21:47 ` Justin Piszcz
2006-07-10 22:27 ` Jan Engelhardt
2006-07-10 22:30 ` Justin Piszcz
2006-07-11 7:52 ` Jan Engelhardt
2006-07-11 9:05 ` Petr Vyskocil [this message]
2006-07-11 9:05 ` Petr Vyskocil
2006-07-18 0:16 ` Neil Brown
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='e8vplt$fgv$1@sea.gmane.org' \
--to=petr@anime.cz \
--cc=linux-kernel@vger.kernel.org \
--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.