On February 27, [EMAIL PROTECTED] wrote:
> Quoting Neil Brown <[EMAIL PROTECTED]>:
>
> > On February 26, [EMAIL PROTECTED] wrote:
> > > I'm currently running a standard v2.2.17 kernel w/ the 'accompanying'
> > > raid system (linear).
> >
> > Given this, you should be able to run mkraid with complete safety as
> > is doesn't actually write anything to any drive.
>
> Hmmm, 'should be'... I'm not sure i liked that sentence... :)
"should be" because:
- I haven't tried it
- I didn't write the code
- I have poured over the code in detail
but
- it makes sense, because I cannot think of any
way that data could get corrupted, especially if you
"fsck -N" before actually using the array, but to make sure that
it was assembled properly.
- I believe that the person who did write the code was very cautious
about making it hard to accidentally corrupt data. So especially
if you use "raid0run" there should be no problems.
>
> > > And this is what cfdisk tells me about the partitions:
> > > sdb1 Primary Linux raid autodetect 6310.74
> > > sdc1 Primary Linux raid autodetect 1059.07
> > > sdd10 Logical Linux raid autodetect 2549.84
> > > sde1 Primary Linux raid autodetect 9138.29
> > > sdf1 Primary Linux raid autodetect 18350.60
> > > sdg1 Primary Linux raid autodetect 16697.32
> > >
> >
> > Autodetect cannot work with old-style arrays that don't have
> > superblocks. If you want autodetect, you will need to copy the data
> > somewhere, create a new array, and copy it all back.
>
> Oki, what exactly does that mean/tell me?
>
> Should I set the FS type to 83 again?
The linux kernel doesn't treat any partition type specially except
FD. So if you are only using Linux, it doesn't matter what you set it
to. 83 would probably be a good choice though.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
