Re: old raid tools dangerous with 2.6.18?
On Sunday October 1, [EMAIL PROTECTED] wrote: Richard Bollinger [EMAIL PROTECTED] writes: It appears that raidhotadd doesn't always trigger a resync under 2.6.18. Starting with a broken raid1 mirror: Same with evms and 2.6.18. it does not trigger the raid1 resync in any case. (while it does with 2.6.17) Have these tools to be updated ? Well, mdadm-2.x should work, but this is a serious bug in md. The following patch fixes it and should go in 2.6.18.1. Thanks and apologies. NeilBrown Fix problem where hot-added drives are not resynced. If a drive is added with HOT_ADD_DISK rather than ADD_NEW_DISK, saved_raid_disk isn't initialised properly, and the drive can be included in the array without a resync. ### Diffstat output ./drivers/md/md.c |1 + 1 file changed, 1 insertion(+) diff .prev/drivers/md/md.c ./drivers/md/md.c --- .prev/drivers/md/md.c 2006-10-03 17:10:54.0 +1000 +++ ./drivers/md/md.c 2006-10-03 17:11:19.0 +1000 @@ -3867,6 +3867,7 @@ static int hot_add_disk(mddev_t * mddev, } clear_bit(In_sync, rdev-flags); rdev-desc_nr = -1; + rdev-saved_raid_disk = -1; err = bind_rdev_to_array(rdev, mddev); if (err) goto abort_export; - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Recipe for Mirrored OS Drives
On Sun, Oct 01, 2006 at 07:45:46PM -0400, andy liebman wrote: -- Run rsync to copy contents from your existing OS drive rsync -av /mnt/oldroot /mnt/newroot rsync -av /mnt/oldhome /mnt/newhome At least add the -H flag to copy hardlinks. -S for sparse files might also be useful. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[no subject]
Hello Neil, Ingo and [insert your name here], I try to understand the raid5 and md code and I have a question concerning the cache. There are two ways of calculating the parity: read-modify-write and reconstruct-write. In my understanding, the code only checks how many buffers it has to read for each method (rmw or rcw) without considering the cache. But what if there was relevant data in the cache? How would the raid code know it so it can build a decision on top of this knowledge? I hope You can help me, since I could not find any information on this in the mailing list archive. Thanks in advance, Jochen - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Recipe for Mirrored OS Drives
Nix wrote: On 2 Oct 2006, David Greaves spake: I suggest you link from http://linux-raid.osdl.org/index.php/RAID_Boot The pages don't really have the same purpose. RAID_Boot is `how to boot your RAID system using initramfs'; this is `how to set up a RAID system in the first place', i.e., setup. I'll give it a bit of a tweak-and-rename in a bit. Fair :) FYI I've done quite a bit on the Howto section: http://linux-raid.osdl.org/index.php/Overview It still needs a lot of work I think but it's getting there... David -- - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: old raid tools dangerous with 2.6.18?
Neil Brown [EMAIL PROTECTED] writes: It appears that raidhotadd doesn't always trigger a resync under 2.6.18. Starting with a broken raid1 mirror: Same with evms and 2.6.18. it does not trigger the raid1 resync in any case. (while it does with 2.6.17) Have these tools to be updated ? Well, mdadm-2.x should work, but this is a serious bug in md. The following patch fixes it and should go in 2.6.18.1. yeah, perfect, Thanks a lot ! -- - To unsubscribe from this list: send the line unsubscribe linux-raid in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
