From: Kasper Sandberg <postmaster@metanurb.dk>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Question for Neil/Superblocks
Date: Fri, 27 Nov 2009 23:22:22 +0100 [thread overview]
Message-ID: <1259360542.31633.188.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.2.00.0911271624450.30813@p34.internal.lan>
On Fri, 2009-11-27 at 16:27 -0500, Justin Piszcz wrote:
> Hi Neil,
>
> A couple of things, recently I tried to make a new system (MDADM/latest/SW
> RAID1) and noticed that GRUB & LILO still only support 0.90 superblocks.
> This leads me to my next question.
>
> Will the newer superblocks be supported? I ask this due to my final
> question.
>
> With 0.90 superblocks, I have never seen any array (raid1,raid5,raid6) try
> to correct a read-error, but when I made an array with 1.2 superblocks
> (not the boot volume of course) using VelociRaptors, great for testing
> crap disks that don't work in read, I did see it try to correct read
> errors! I was wondering if that is only applicable to superblocks >=
> 1.x+?
>
> I know you can build yourself an initrd/miniroot so/on/so forth but its
> nice when you can just build a kernel, run lilo and have it auto-detect
> the raid1 volumes and boot accordingly (as you can with 0.90 superblocks).
have a separate boot partition raid1....
>
> Justin.
> --
> 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:[~2009-11-27 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 21:27 Question for Neil/Superblocks Justin Piszcz
2009-11-27 22:22 ` Kasper Sandberg [this message]
2009-11-30 8:48 ` Simon Jackson
2009-11-28 21:17 ` Doug Ledford
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=1259360542.31633.188.camel@localhost \
--to=postmaster@metanurb.dk \
--cc=jpiszcz@lucidpixels.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;
as well as URLs for NNTP newsgroup(s).