On Thu, Mar 28, 2002 at 04:12:37PM -0800, brian@worldcontrol.com wrote: > You can read all the gory details of my RAID1 setup at > http://www.litzinger.com/raid.html > ... > I created a bootable RAID 1 setup and everything works fine. > > Except, every time I power down the system and bring it back > up the system reports that the RAID array is unclean and > spends and hour doing a reconstruct. Responding to my own email, the message that flies by is 'invalidate: busy buffer'. There are generally what looks to be between 3 and 30 of them. There are some other messages, but no amount of futzing with /etc/rc.d/init.d/halt seems to be able to influence the computer to leave them on the screen long enough to be of any value. Here is what comes up on every boot, no matter how cleanly shutdown: md: Autodetecting RAID arrays. [events: 00000028] [events: 0000001e] [events: 00000028] [events: 0000001e] md: autorun ... md: considering hdd5 ... md: adding hdd5 ... md: adding hdc5 ... md: created md1 md: bind<hdc5,1> md: bind<hdd5,2> md: running: <hdd5><hdc5> md: hdd5's event counter: 0000001e md: hdc5's event counter: 0000001e md: md1: raid array is not clean -- starting background reconstruction md: RAID level 1 does not need chunksize! Continuing anyway. md1: max total readahead window set to 124k md1: 1 data-disks, max readahead per data-disk: 124k md1: 1 data-disks, max readahead per data-disk: 124k raid1: device hdd5 operational as mirror 0 raid1: device hdc5 operational as mirror 1 raid1: raid set md1 not clean; reconstructing mirrors raid1: raid set md1 active with 2 out of 2 mirrors md: updating md1 RAID superblock on device md: hdd5 [events: 0000001f]<6>(write) hdd5's sb offset: 69697856 md: syncing RAID array md1 md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc. md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction. md: using 124k window, over a total of 69697856 blocks. md: hdc5 [events: 0000001f]<6>(write) hdc5's sb offset: 69697856 md: considering hdd1 ... md: adding hdd1 ... md: adding hdc1 ... md: created md0 md: bind<hdc1,1> md: bind<hdd1,2> md: running: <hdd1><hdc1> md: hdd1's event counter: 00000028 md: hdc1's event counter: 00000028 md: md0: raid array is not clean -- starting background reconstruction md: RAID level 1 does not need chunksize! Continuing anyway. md0: max total readahead window set to 124k md0: 1 data-disks, max readahead per data-disk: 124k raid1: device hdd1 operational as mirror 0 raid1: device hdc1 operational as mirror 1 raid1: raid set md0 not clean; reconstructing mirrors raid1: raid set md0 active with 2 out of 2 mirrors md: updating md0 RAID superblock on device md: hdd1 [events: 00000029]<6>(write) hdd1's sb offset: 56128 Mar 28 23:14:31 lab kernel: md: delaying resync of md0 until md1 has finished resync (they share one or more physical units) Mar 28 23:14:31 lab kernel: md: hdc1 [events: 00000029]<6>(write) hdc1's sb offset: 56128 md: ... autorun DONE. -- Brian Litzinger <brian@worldcontrol.com> - 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
