Re: Re: General question
Stephan von Krawczynski <[email protected]>
| Newsgroups | gmane.linux.enbd.general |
|---|---|
| Organization | ith Kommunikationstechnik GmbH |
| Message-ID | <[email protected]> |
Playing around with the version from 6th June I had to find out that the resync does not seem to work after _second_ network breakdown. It says: Jun 7 18:08:39 mail-a01 kernel: md: syncing RAID array md0 Jun 7 18:08:39 mail-a01 kernel: md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc. Jun 7 18:08:39 mail-a01 kernel: md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction. Jun 7 18:08:39 mail-a01 kernel: md: using 124k window, over a total of 987996 blocks. Jun 7 18:08:39 mail-a01 kernel: md0: retained bitmap f6908700 Jun 7 18:08:39 mail-a01 kernel: raid1: skipped clean sectors 0-127 Jun 7 18:08:39 mail-a01 kernel: raid1: synced dirty sectors 128-135 Jun 7 18:08:39 mail-a01 kernel: device not enabled. Jun 7 18:08:39 mail-a01 kernel: ENBD enbd.c #3467[33]: do_nbd_request ending req f7e02500 with prejudice Jun 7 18:08:39 mail-a01 kernel: end_request: I/O error, dev 2b:10 (nbd), sector 128 Jun 7 18:08:39 mail-a01 kernel: raid1: bitmap f6908700 already active! Jun 7 18:08:39 mail-a01 kernel: raid1: Disk failure on ndb, disabling device. Jun 7 18:08:39 mail-a01 kernel: Operation continuing on 1 devices Jun 7 18:08:39 mail-a01 kernel: raid1: skipped clean sectors 136-383 Jun 7 18:08:39 mail-a01 kernel: md: md_do_sync() got signal ... exiting This loops every few seconds... -- Regards, Stephan