Brian Behlendorf 7d2868d5fc Skip bad DVAs during free by setting zfs_recover=1 ... When a bad DVA is encountered in metaslab_free_dva() the system should treat it as fatal. This indicates that somehow a damaged DVA was written to disk and that should be impossible. However, we have seen a handful of reports over the years of pools somehow being damaged in this way. Since this damage can render otherwise intact pools unimportable, and the consequence of skipping the bad DVA is only leaked free space, it makes sense to provide a mechanism to ignore the bad DVA. Setting the zfs_recover=1 module option will cause the DVA to be ignored which may allow the pool to be imported. Since zfs_recover=0 by default any pool attempting to free a bad DVA will treat it as a fatal error preserving the current behavior. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #3099 Issue #3090 Issue #2720		2015-02-13 16:02:04 -08:00
..
avl	Explicitly include SPL compat headers	2014-11-19 12:30:39 -05:00
nvpair	Use vmem_alloc() for nvlists	2015-02-10 11:00:08 -08:00
unicode	Explicitly include SPL compat headers	2014-11-19 12:30:39 -05:00
zcommon	Change KM_PUSHPAGE -> KM_SLEEP	2015-01-16 14:41:26 -08:00
zfs	Skip bad DVAs during free by setting zfs_recover=1	2015-02-13 16:02:04 -08:00
zpios	Explicitly include SPL compat headers	2014-11-19 12:30:39 -05:00
.gitignore	gitignore: anchor entries at their respective directory	2013-04-02 10:50:17 -07:00
Makefile.in	Fix modules installation directory	2014-10-28 09:46:14 -07:00