Perhaps a dumb question, but aren't you supposed to use the 0.90 raidtools
with the "new" RAID md driver? In other words, I don't think you can mix
the stock md kernel driver with the newer raidtools.
Initially, I did the same thing -- I used the mkraid tool that came with
RedHat, which is version 0.90. After applying the RAID kernel patch from
Mingo to bring the kernel md driver up to a matching version
(http://people.redhat.com/mingo/raid-patches/ for the latest patches,
ftp://ftp.kernel.org/pub/linux/daemons/raid/alpha/ for older snapshots),
things were much happier.
In particular, this:
>[root@sadia rc.d]# cat /proc/mdstat
>Personalities : [3 raid1]
>read_ahead not set
>md0 : inactive
>md1 : inactive
>md2 : inactive
>md3 : inactive
...indicates that you are indeed running the stock md in the
kernel. Output for new RAID from /proc/mdstat does not list each inactive
md device separately (sorry, don't have a sample of the newer /proc/mdstat
handy).
I'm glad you're using SCSI devices; I've had nothing but trouble with my
60Gig Maxtor drives on a Promise Ultra66 controller card.
At 04:58 PM 9/11/00, you wrote:
>Hello,
>
>I'm having trouble running mkraid with the above setup. I'm not on the
>list, please be sure to email [EMAIL PROTECTED] on responses. Thanks!
>
>Here's a bunch of diag info, feel free to ask for more:
>
>[root@sadia rc.d]# mkraid /dev/md0
>handling MD device /dev/md0
>analyzing super-block
>disk 0: /dev/sdb1, 36081958kB, raid superblock at 36081856kB
>/dev/sdb1 appears to contain an ext2 filesystem -- use -f to override
>mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
>*** so, I run:
>
>[root@sadia rc.d]# mkraid --really-force /dev/md0
>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, 36081958kB, raid superblock at 36081856kB
>disk 1: /dev/sdc1, 36081958kB, raid superblock at 36081856kB
>mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
>*** here's /proc/mdstat, immediately after running mkraid above:
>
>[root@sadia rc.d]# cat /proc/mdstat
>Personalities : [3 raid1]
>read_ahead not set
>md0 : inactive
>md1 : inactive
>md2 : inactive
>md3 : inactive
>
>*** here are the contents of /etc/raidtab:
>
>[root@sadia rc.d]# cat /etc/raidtab
>raiddev /dev/md0
> raid-level 1
> nr-raid-disks 2
> nr-spare-disks 0
> chunk-size 4
> persistent-superblock 1
>
> device /dev/sdb1
> raid-disk 0
>
> device /dev/sdc1
> raid-disk 1
>
>*** here are the relevant disks
>
>[root@sadia rc.d]# fdisk -ul /dev/sdb
>
>Disk /dev/sdb: 255 heads, 63 sectors, 4492 cylinders
>Units = sectors of 1 * 512 bytes
>
> Device Boot Start End Blocks Id System
>/dev/sdb1 63 72163979 36081958+ 83 Linux
>[root@sadia rc.d]# fdisk -ul /dev/sdc
>
>Disk /dev/sdc: 255 heads, 63 sectors, 4492 cylinders
>Units = sectors of 1 * 512 bytes
>
> Device Boot Start End Blocks Id System
>/dev/sdc1 63 72163979 36081958+ 83 Linux
>
>*** I intermittently get these kinds of messgaes logged to syslog when
> trying to run mkraid:
>
>Sep 11 10:21:23 sadia kernel: SCSI device sdb: hdwr sector= 512 bytes.
>Sectors= 72170879 [35239 MB] [35.2 GB]
>Sep 11 10:21:23 sadia kernel: sdb: sdb1
>Sep 11 10:21:43 sadia kernel: SCSI device sdc: hdwr sector= 512 bytes.
>Sectors= 72170879 [35239 MB] [35.2 GB]
>Sep 11 10:21:43 sadia kernel: sdc: sdc1
>
>*** Here's the relevant output of an strace of "mkraid --really-force
> /dev/md0" Notice the ioctl failure:
>
>open("/dev/sdc1", O_RDONLY) = 4
>ioctl(4, BLKGETSIZE, 0xbffffa50) = 0
>open("/etc/mtab", O_RDONLY) = 5
>fstat(5, {st_mode=S_IFREG|0644, st_size=145, ...}) = 0
>old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
>0) = 0x40017000
>read(5, "/dev/sda1 / ext2 rw 0 0\nnone /pr"..., 4096) = 145
>read(5, "", 4096) = 0
>close(5) = 0
>munmap(0x40017000, 4096) = 0
>close(4) = 0
>open("/dev/md0", O_RDONLY) = 4
>ioctl(4, 0x40480923, 0x804fcd8) = -1 EINVAL (Invalid argument)
>write(2, "mkraid: aborted, see the syslog "..., 70mkraid: aborted, see the
>syslog and /proc/mdstat for potential clues.
>) = 70
>close(3) = 0
>munmap(0x40015000, 4096) = 0
>munmap(0x40016000, 4096) = 0
>_exit(1) = ?
>
>*** here's the proof of version numbers
>[root@sadia rc.d]# uname -a
>Linux sadia 2.2.17 #1 SMP Mon Sep 11 09:19:29 PDT 2000 i686 unknown
>[root@sadia rc.d]# mkraid -V
>mkraid version 0.90.0
>[root@sadia rc.d]# dmesg | grep md
>md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
>
>Josh Beck - [EMAIL PROTECTED]
>
>MP3.com - The Premier Music Service Provider
>Put your CD Collection Online in Minutes!
>http://my.mp3.com
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
