May 7, 201016 yr Uah, I just replaced a data disk with a new one. Hit Start and now I'm stuck as you can see in the scrrenshot. There's no way to sto/reboot/change that situation. What should I do? Thanks Harald bla.txt
May 7, 201016 yr Uah, I just replaced a data disk with a new one. Hit Start and now I'm stuck as you can see in the scrrenshot. There's no way to sto/reboot/change that situation. What should I do? Thanks Harald It can take as long as 5 or 6 minutes for the translation journals to be re-played. (assuming that is what is happening) Wait a bit longer and press refresh again. See if you can grab a copy of the syslog. Instructions in the wiki under troubleshooting. Joe L.
May 7, 201016 yr Author Yes, several minutes later it looked promising. I hit Stop and Start (just to be sure) and now Data Rebuild is working. BUT 5.000 Writes to the parity disk after 3% do make me nerveous. Why does data rebuild write to parity??? Thanks Harald
May 7, 201016 yr Yes, several minutes later it looked promising. I hit Stop and Start (just to be sure) and now Data Rebuild is working. BUT 5.000 Writes to the parity disk after 3% do make me nerveous. Why does data rebuild write to parity??? Thanks Harald They were not written to the parity disk during the rebuild. They were written to the parity disk when the disk having its journal replayed was written to. When it is replayed, the parity disk is kept in sync with the writes. Same thing happened when I just re-started my server after I ran out of RAM using ffmpeg and handbreak. I've not written anything new to the server but I show 5104 writes to the parity disk and 5037 writes to the data disk. (the extra "writes" to the parity disk were the other disks in the array mounting themselves) My display showed "mounting" for over 2 minutes. Look at the line below where I highlighted the time it took in RED I've seen syslogs posted where it took over 5 or 6 minutes. In my syslog it showed: May 6 23:42:52 Tower kernel: REISERFS (device hdj1): journal params: device hdj1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 May 6 23:42:52 Tower kernel: REISERFS (device hdj1): checking transaction log (hdj1) May 6 23:42:52 Tower kernel: REISERFS (device hdj1): replayed 2 transactions in 0 seconds May 6 23:42:52 Tower kernel: REISERFS (device hdj1): Using r5 hash to sort names May 6 23:42:52 Tower kernel: REISERFS (device md11): checking transaction log (md11) May 6 23:42:52 Tower kernel: REISERFS (device md10): checking transaction log (md10) May 6 23:42:52 Tower kernel: REISERFS (device md8): checking transaction log (md8) May 6 23:42:52 Tower kernel: REISERFS (device md7): checking transaction log (md7) May 6 23:42:52 Tower kernel: REISERFS (device md6): checking transaction log (md6) May 6 23:42:52 Tower kernel: REISERFS (device md5): checking transaction log (md5) May 6 23:42:52 Tower kernel: REISERFS (device md4): checking transaction log (md4) May 6 23:42:52 Tower kernel: REISERFS (device md3): checking transaction log (md3) May 6 23:42:52 Tower kernel: REISERFS (device md2): checking transaction log (md2) May 6 23:42:52 Tower kernel: REISERFS (device md1): checking transaction log (md1) May 6 23:42:53 Tower kernel: REISERFS (device md10): replayed 2 transactions in 1 seconds May 6 23:42:53 Tower kernel: REISERFS (device md6): replayed 2 transactions in 1 seconds May 6 23:42:53 Tower kernel: REISERFS (device md5): replayed 2 transactions in 1 seconds May 6 23:42:53 Tower kernel: REISERFS (device md3): replayed 2 transactions in 1 seconds May 6 23:42:53 Tower kernel: REISERFS (device md8): replayed 2 transactions in 1 seconds May 6 23:42:53 Tower kernel: REISERFS (device md6): Using r5 hash to sort names May 6 23:42:53 Tower kernel: REISERFS (device md10): Using r5 hash to sort names May 6 23:42:53 Tower kernel: REISERFS (device md2): replayed 2 transactions in 1 seconds May 6 23:42:54 Tower kernel: REISERFS (device md1): replayed 2 transactions in 2 seconds May 6 23:42:54 Tower kernel: REISERFS (device md8): Using r5 hash to sort names May 6 23:42:54 Tower kernel: REISERFS (device md3): Using r5 hash to sort names May 6 23:42:54 Tower kernel: REISERFS (device md5): Using r5 hash to sort names May 6 23:42:54 Tower kernel: REISERFS (device md4): replayed 2 transactions in 2 seconds May 6 23:42:54 Tower kernel: REISERFS (device md7): replayed 2 transactions in 2 seconds May 6 23:42:54 Tower kernel: REISERFS (device md2): Using r5 hash to sort names May 6 23:42:54 Tower kernel: REISERFS (device md1): Using r5 hash to sort names May 6 23:42:55 Tower kernel: REISERFS (device md7): Using r5 hash to sort names May 6 23:42:55 Tower kernel: REISERFS (device md4): Using r5 hash to sort names May 6 23:45:07 Tower kernel: REISERFS (device md11): replayed 980 transactions in 135 seconds May 6 23:45:07 Tower kernel: REISERFS (device md11): Using r5 hash to sort names (More RAM should be arriving by fed-ex today) Joe L.
Archived
This topic is now archived and is closed to further replies.