Hi, On 12/3/10 9:30 AM, Jiang Jinke wrote: > Hi, > > Thanks for your reply. > > I re-check the system and found there is a raid fail message pops up > in the dmesg. > [root ~]# cat /proc/mdstat > Personalities : [raid1] > md0 : active raid1 sdb1[1] sda1[0] > 104320 blocks [2/2] [UU] > > md3 : active raid1 sdb2[1] sda2[2](F) > 432983808 blocks [2/1] [_U] > > When I remove one of the raid disk, the mediaproxy goes wrong again. > > Remove by > [root ~]# mdadm /dev/md3 --remove /dev/sda2 > > Restarted again, and works fine now. > I'm wonder if there is anything affect the mediaproxy while doing > mdadm remove/add, set fail operation ? >
MediaProxy doesn't do anything with physical block devices, however, having an unstable or failing server may lead to unexpected behavior. > I did try mediaproxy 2.4.1 in my test server, will try to upgrade to > 2.4.2 if possible later. Thanks again. > Yes, the best would be to test version 2.4.2 on a 'clean' environment so that results are not altered by side factors. Regards, -- Saúl Ibarra Corretgé AG Projects _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
