/freebsd/sys/geom/raid3/ |
H A D | g_raid3.c | 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd
|
/freebsd/sys/geom/mirror/ |
H A D | g_mirror.c | 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd 4a7f7b10 Tue Sep 11 20:20:13 GMT 2012 Gleb Smirnoff <glebius@FreeBSD.org> When synchronizing, include in the config dump amount of bytes syncronized. The rationale behind this is the following: for large disks the percent synchronisation counter ticks too seldom, and monitoring software (as well as human operator) can't tell whether synchronisation goes on or one of disks got stuck. On an idle server one can look into gstat and see whether synchronisation goes on or not, but on a busy server that won't work. Also, new value monitored can be differentiated obtaining the synchronisation speed quite precisely.
Submitted by: Konstantin Kukushkin <dark ramtel.ru> Reviewed by: pjd
|