> what I'm waiting for now, it's laying down the image (rsync and I get > these messages every X (once a md device finishes sync'n I guess) > (note i have tried 1000/1000 on speed and it took the same amount of > time as this appears to be taking). > > md: minimum _guaranteed_ reconstruction speed: 5000 KB/sec/disc. > md: using maximum available idle IO bandwidth (but not more than 100000 > KB/sec) > for reconstruction. > md: using 128k window, over a total of 2007744 blocks. > md: md2: sync done. > RAID1 conf printout: > --- wd:2 rd:2 > disk 0, wo:0, o:1, dev:sda3 > disk 1, wo:0, o:1, dev:sdb3
Okay same issue this time, system finished after 4-5 hours and on boot it comes up with this Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda7 fsck.ext3: Device or resource busy while trying to open /dev/sda7 Filesystem mounted or opened exclusively by another program? [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. This is the second time, the volume is not dirty and if I stop the raid group and run fsck on /dev/sda7 it comes back clean. If I remove the .autofsck<blah> file the system will come up correctly.. I may need to move some of these issues elsewhere as I may be getting into something with software raid more so than SI setting it up (or?) Tory ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
