7103ac8ad6
In theory, all data access errors mean that a member is out of sync at most. But they were treated as more serious errors to avoid the situation where a flaky disk gets repeatedly disconnected, re-synchronized, reconnected and then disconnected again. ENXIO is a special error that means that the member disk disappeared, so it should get the same handling as the GEOM orphaning event. There is a better chance that when the disk is reconnected, it will be a good member again. When ENXIO happens on a read we use the exisiting G_MIRROR_BUMP_SYNCID mechanism which means that the mirror's syncid is increased as soon as there is a write to the mirror. That's because no data has got out of sync yet, but the problematic memeber is disconnected, so the future write will make it stale. When ENXIO happens on a write we use a new G_MIRROR_BUMP_SYNCID_NOW mechanism which means that we update the mirror metadata as soon as possible because the problematic memeber is already behind. Reviewed by: markj, imp MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D9463 |
||
|---|---|---|
| .. | ||
| bde | ||
| cache | ||
| concat | ||
| eli | ||
| gate | ||
| journal | ||
| label | ||
| linux_lvm | ||
| mirror | ||
| mountver | ||
| multipath | ||
| nop | ||
| part | ||
| raid | ||
| raid3 | ||
| sched | ||
| shsec | ||
| stripe | ||
| uzip | ||
| vinum | ||
| virstor | ||
| zero | ||
| geom_aes.c | ||
| geom_bsd_enc.c | ||
| geom_bsd.c | ||
| geom_ccd.c | ||
| geom_ctl.c | ||
| geom_ctl.h | ||
| geom_dev.c | ||
| geom_disk.c | ||
| geom_disk.h | ||
| geom_dump.c | ||
| geom_event.c | ||
| geom_flashmap.c | ||
| geom_fox.c | ||
| geom_int.h | ||
| geom_io.c | ||
| geom_kern.c | ||
| geom_map.c | ||
| geom_mbr_enc.c | ||
| geom_mbr.c | ||
| geom_redboot.c | ||
| geom_slice.c | ||
| geom_slice.h | ||
| geom_subr.c | ||
| geom_sunlabel_enc.c | ||
| geom_sunlabel.c | ||
| geom_vfs.c | ||
| geom_vfs.h | ||
| geom_vol_ffs.c | ||
| geom.h | ||
| notes | ||