hummm, i think i forgot the resync on sync_action hehehe thanks a lot! :) 2012/5/17 Marcus Sorensen <shadowsor@xxxxxxxxx>: > Did you do that to all of the related arrays? what does > /sys/block/md1/md/sync_action show? Perhaps its just paused and you > can start it manually by echoing 'resync' into it. > > On Thu, May 17, 2012 at 9:57 AM, Roberto Spadim <roberto@xxxxxxxxxxxxx> wrote: >> i did this and don't worked >> echo 1 > /sys/block/md1/md/sync_force_parallel >> >> at /proc/mdstat >> /dev/md1 appears as sync >> but stay at 0% >> and after /dev/md0 resync /dev/md1 start >> >> there's another way to force sync? >> >> 2012/5/17 Marcus Sorensen <shadowsor@xxxxxxxxx> >>> >>> see /sys/block/md[0,1,2]/md/sync_force_parallel >>> >>> On Thu, May 17, 2012 at 9:50 AM, Roberto Spadim <roberto@xxxxxxxxxxxxx> wrote: >>> > hi guys, i was running a resync in a non-normal hardware instalation >>> > >>> > it's a server with 4 disks, they are in a raid hardware controller (perci >>> > from dell) >>> > disk 1-2 are raid1 and linux know it about /dev/sda >>> > disk 3-4 are raid1 and linux know it about /dev/sdb >>> > >>> > well i add more 4 disks >>> > disk 5-6 raid1 with /dev/sdc >>> > disk 7-8 raid1 with /dev/sdd >>> > >>> > nice... >>> > well /dev/sda and /dev/sdb have same partitions (/dev/sda1, 2 3 4) and have >>> > some md devices in this partitions.. >>> > /dev/md0 = /dev/sda1 /dev/sdb1 >>> > /dev/md1 = /dev/sda2 /dev/sdb2 >>> > /dev/md2 = /dev/sda3 /dev/sdb3 >>> > all raid 1 too >>> > >>> > i create same partitions on /dev/sdc, /dev/sdd >>> > and add they to md raid1 >>> > /dev/md0 = /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 >>> > /dev/md1 = /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 >>> > /dev/md2 = /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 >>> > >>> > >>> > nice.. >>> > mdadm start resync... >>> > the point is... >>> > /dev/sda1 start copies to /dev/sdc1 and /dev/sdd1, i checked this with >>> > iostat -d 1 -k, and server is idle, only mdadm and raid is running, >>> > /dev/sda1 have reads and /dev/sdc1 and /dev/sdd1 have writes >>> > nice.. >>> > >>> > the problem is... >>> > /dev/sdc2 and /dev/sdd2 didn't start sync while /dev/md0 is running, since >>> > they share the same devices (/dev/md0 => /dev/sda1, /dev/md1 => /dev/sda2) >>> > >>> > could i force a sync in /dev/md1?? >>> > since /dev/sda is a raid1 hardware, it can handle two disks without >>> > performace problems... >>> > it have 2 heads, in others words the mdadm disk balance isn't perfect here >>> > to this solution, but works... the problem is sync not running, if i could >>> > force it every things could be allright >>> > >>> > i must check kernel version, it's about 2.6.3x, 1 year old +- >>> > >>> > well that's it, any ideas? >>> > >>> > >>> > *** >>> > sorry if i send two emails, the email was configured to HTML/RICH TEXT text >>> > >>> > >>> > -- >>> > Roberto Spadim >>> > Spadim Technology / SPAEmpresarial >>> > -- >>> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in >>> > the body of a message to majordomo@xxxxxxxxxxxxxxx >>> > More majordomo info at http://vger.kernel.org/majordomo-info.html >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in >>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >> >> >> >> -- >> Roberto Spadim >> Spadim Technology / SPAEmpresarial > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Roberto Spadim Spadim Technology / SPAEmpresarial -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
