Well unbelievable you are right...even though it clearly states linear
raid does not use chunk-size adding it in raidtab allowed it to
mkraid. Thank the lord and thank you for your suggestion :)
> > as I did before? If I use raidstart etc I get same invalid argument
> > error. My raidtab is:
> > raiddev /dev/md0
> > raid-level linear
> > nr-raid-disks 2
> > persistent-superblock 1
> > device /dev/sdb1
> > raid-disk 0
> > device /dev/sdc1
> > raid-disk 1
>
> Counterintuitively, I believe you need a chunk-size line in there, even though
> chunk-size is irrelevant to linear raid. As it's irrelevant, I don't think it
> matters what size you put in, so just go with a typical figure, such as 4. I
> think it just needs to be there so that mkraid can successfully parse
> /etc/raidtab, although there may be some future use planned for it.
>
> Cheers,
>
>
> Bruno Prior [EMAIL PROTECTED]
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > [EMAIL PROTECTED]
> > Sent: 29 September 1999 12:54
> > To: [EMAIL PROTECTED]
> > Subject: /dev/md0: Invalid argument Please help
> >
> >
> > Hello, I've seen this subject in here before but
> > I have yet to find a solution that works for me.
> > I have tried many different combinations including
> > using raidtools-19990824-0.90.tar.gz in combination
> > with kernel 2.2.12. The patch works fine (with one
> > rej that people have mentioned) and kernel compiles
> > wonderfully. On reboot and 'mkraid /dev/md0' I get:
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/sdb1, 8886256kB, raid superblock at 8886144kB
> > /dev/sdb1 appears to contain an ext2 filesystem -- use -f to override
> > mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
> > If I use 'mkraid --force-really /dev/md0' I get:
> > DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/sdb1, 8886256kB, raid superblock at 8886144kB
> > disk 1: /dev/sdc1, 8886256kB, raid superblock at 8886144kB
> > /dev/md0: Invalid argument
> >
> > If I take out the persistant superblock statement in my raidtab
> > I get same as above without the disk 0; etc sequence.
> >
> > I did notice with 'cat /proc/mdstat' I get:
> > [root@cssstpc1 /root]# cat /proc/mdstat
> > Personalities : [linear] [raid0] [raid1] [raid5] [translucent] [hsm]
> > read_ahead not set
> > unused devices: <none>
> >
> > and I know before I had devices show up in there (I was using
> > raidtools .40 before but now I have 10 devices and I get core dump
> > using those (above shows just 2 devices I know but I am just testing).
> > Should I see
> > md0 : inactive
> > md1 : inactive
> > md2 : inactive
> > md3 : inactive
> >
> > as I did before? If I use raidstart etc I get same invalid argument
> > error. My raidtab is:
> > raiddev /dev/md0
> > raid-level linear
> > nr-raid-disks 2
> > persistent-superblock 1
> > device /dev/sdb1
> > raid-disk 0
> > device /dev/sdc1
> > raid-disk 1
> >
> > I have tried with different kernels patches etc to no avail. I did
> > notice in previous posts something to the effect of:
> > "> I use a clean 2.2.12 + patch-2.2.13pre11.gz "
> > and don't know what that is referring to.
> >
> > All help is appreciated..thanks
> >
> > --
> > Douglas Stoun <[EMAIL PROTECTED]>
> > Florida State University - Center for Music Research
> > 904-644-5788 (6100 - Fax)
> > http://www.music.fsu.edu
> >
> >
> >
> >
>
--
Douglas Stoun <[EMAIL PROTECTED]>
Florida State University - Center for Music Research
904-644-5788 (6100 - Fax)
http://www.music.fsu.edu
