I recently installed RH 6.0, and built several raid0 and 1 raid1 devices, with this kernel. I then upgraded to RH's new kerenl : 2.2.5-15. I have no problems with this configuration. 2.2.5-15 dmesg (long, but see below, this is after an unsuccessful 2.2.11 boot) (read) sda2's sb offset: 512960 [events: 00000023] (read) sdb1's sb offset: 513984 [events: 00000023] autorun ... considering sdb1 ... adding sdb1 ... adding sda2 ... created md0 bind<sda2,1> bind<sdb1,2> running: <sdb1><sda2> now! sdb1's event counter: 00000023 sda2's event counter: 00000023 raid0 personality registered mask ffffffe0 rdev->size: 513984 masked rdev->size: 513984 new md_size: 513984 rdev->size: 512960 masked rdev->size: 512960 new md_size: 1026944 md0: max total readahead window set to 256k md0: 2 data-disks, max readahead per data-disk: 128k raid0: looking at sda2 raid0: comparing sda2(512960) with sda2(512960) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sdb1 raid0: comparing sdb1(513984) with sda2(512960) raid0: NOT EQUAL raid0: comparing sdb1(513984) with sdb1(513984) raid0: END raid0: ==> UNIQUE raid0: 2 zones raid0: FINAL 2 zones zone 0 checking sda2 ... contained as device 0 (512960) is smallest!. checking sdb1 ... contained as device 1 zone->nb_dev: 2, size: 1025920 current zone offset: 512960 zone 1 checking sda2 ... nope. checking sdb1 ... contained as device 0 (513984) is smallest!. zone->nb_dev: 1, size: 1024 current zone offset: 513984 done. raid0 : md_size is 1026944 blocks. raid0 : conf->smallest->size is 1024 blocks. raid0 : nb_zone is 1003. raid0 : Allocating 8024 bytes for hash. md: updating md0 RAID superblock on device sdb1 [events: 00000024](write) sdb1's sb offset: 513984 sda2 [events: 00000024](write) sda2's sb offset: 512960 . ... autorun DONE. (read) hda2's sb offset: 3216960 [events: 00000022] (read) hdc2's sb offset: 3216960 [events: 00000022] autorun ... considering hdc2 ... adding hdc2 ... adding hda2 ... created md1 bind<hda2,1> bind<hdc2,2> running: <hdc2><hda2> now! hdc2's event counter: 00000022 hda2's event counter: 00000022 mask ffffffc0 rdev->size: 3216960 masked rdev->size: 3216960 new md_size: 3216960 rdev->size: 3216960 masked rdev->size: 3216960 new md_size: 6433920 md1: max total readahead window set to 512k md1: 2 data-disks, max readahead per data-disk: 256k raid0: looking at hda2 raid0: comparing hda2(3216960) with hda2(3216960) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at hdc2 raid0: comparing hdc2(3216960) with hda2(3216960) raid0: EQUAL raid0: FINAL 1 zones zone 0 checking hda2 ... contained as device 0 (3216960) is smallest!. checking hdc2 ... contained as device 1 zone->nb_dev: 2, size: 6433920 current zone offset: 3216960 done. raid0 : md_size is 6433920 blocks. raid0 : conf->smallest->size is 6433920 blocks. raid0 : nb_zone is 1. raid0 : Allocating 8 bytes for hash. md: updating md1 RAID superblock on device hdc2 [events: 00000023](write) hdc2's sb offset: 3216960 hda2 [events: 00000023](write) hda2's sb offset: 3216960 . ... autorun DONE. (read) sda3's sb offset: 392128 [events: 00000023] (read) sdb2's sb offset: 393472 [events: 00000023] autorun ... considering sdb2 ... adding sdb2 ... adding sda3 ... created md2 bind<sda3,1> bind<sdb2,2> running: <sdb2><sda3> now! sdb2's event counter: 00000023 sda3's event counter: 00000023 mask fffffff0 rdev->size: 393472 masked rdev->size: 393472 new md_size: 393472 rdev->size: 392128 masked rdev->size: 392128 new md_size: 785600 md2: max total readahead window set to 256k md2: 2 data-disks, max readahead per data-disk: 128k raid0: looking at sda3 raid0: comparing sda3(392128) with sda3(392128) raid0: END raid0: ==> UNIQUE raid0: 1 zones raid0: looking at sdb2 raid0: comparing sdb2(393472) with sda3(392128) raid0: NOT EQUAL raid0: comparing sdb2(393472) with sdb2(393472) raid0: END raid0: ==> UNIQUE raid0: 2 zones raid0: FINAL 2 zones zone 0 checking sda3 ... contained as device 0 (392128) is smallest!. checking sdb2 ... contained as device 1 zone->nb_dev: 2, size: 784256 current zone offset: 392128 zone 1 checking sda3 ... nope. checking sdb2 ... contained as device 0 (393472) is smallest!. zone->nb_dev: 1, size: 1344 current zone offset: 393472 done. raid0 : md_size is 785600 blocks. raid0 : conf->smallest->size is 1344 blocks. raid0 : nb_zone is 585. raid0 : Allocating 4680 bytes for hash. md: updating md2 RAID superblock on device sdb2 [events: 00000024](write) sdb2's sb offset: 393472 sda3 [events: 00000024](write) sda3's sb offset: 392128 . ... autorun DONE. (read) hda1's sb offset: 5039872 [events: 00000023] (read) hdc1's sb offset: 5039872 [events: 00000023] autorun ... considering hdc1 ... adding hdc1 ... adding hda1 ... created md3 bind<hda1,1> bind<hdc1,2> running: <hdc1><hda1> now! hdc1's event counter: 00000023 hda1's event counter: 00000023 raid1 personality registered md3: max total readahead window set to 128k md3: 1 data-disks, max readahead per data-disk: 128k raid1: device hdc1 operational as mirror 1 raid1: device hda1 operational as mirror 0 (checking disk 0) (really checking disk 0) (checking disk 1) (really checking disk 1) (checking disk 2) (checking disk 3) (checking disk 4) (checking disk 5) (checking disk 6) (checking disk 7) (checking disk 8) (checking disk 9) (checking disk 10) (checking disk 11) raid1: raid set md3 active with 2 out of 2 mirrors md: updating md3 RAID superblock on device hdc1 [events: 00000024](write) hdc1's sb offset: 5039872 hda1 [events: 00000024](write) hda1's sb offset: 5039872 . ... autorun DONE. ============================================================= /proc/mdstat from 2.2.5: Personalities : [raid0] [raid1] read_ahead 1024 sectors md3 : active raid1 hdc1[1] hda1[0] 5039872 blocks [2/2] [UU] md2 : active raid0 sdb2[1] sda3[0] 785600 blocks 16k chunks md1 : active raid0 hdc2[1] hda2[0] 6433920 blocks 64k chunks md0 : active raid0 sdb1[1] sda2[0] 1026944 blocks 32k chunks unused devices: <none> I upgraded to 2.2.11, and also upgraded to raidtools-19990724-0.90. Now, nothing works. I get : /dev/md0: invalid argument. /dev/md1: invalid argument. /dev/md2: invalid argument. /dev/md3: invalid argument. I thought I might need to do mkraid --upgrade, but the program reported that my arrays were OK (under 2.2.11). Also, does 2.2.11 not do the AUTORUN? In 2.2.5, a kernel build asks you something about the kerenl auto-detecting raid arrays, but this is not true in 2.2.11. Could this be the problem? Here is dmesg for 2.2.11 (much shorter): md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 linear personality registered raid0 personality registered raid1 personality registered How can I mount my raid arrays under 2.2.11? Thanks John -- John Taylor Large Scale Distributed Information Systems System Administrator Computer Science Dept, University of Georgia [EMAIL PROTECTED] http://lsdis.cs.uga.edu/
