diff options
| author | pjd <pjd@FreeBSD.org> | 2011-12-18 12:27:45 +0000 |
|---|---|---|
| committer | pjd <pjd@FreeBSD.org> | 2011-12-18 12:27:45 +0000 |
| commit | 952e2f20b5b7f292d040b0456988f2748e4a554f (patch) | |
| tree | 112af611d7225166582bdded325e13ad89fb5819 /usr.sbin/service | |
| parent | 3c1d6d15932737a320fd0860781f16898f43ef5f (diff) | |
| download | FreeBSD-src-952e2f20b5b7f292d040b0456988f2748e4a554f.zip FreeBSD-src-952e2f20b5b7f292d040b0456988f2748e4a554f.tar.gz | |
From time to time people report space map corruption resulting in panic
(ss == NULL) on pool import. I had such a panic recently. With current version
of ZFS it is still possible to import the pool in readonly mode and backup
all the data, but in case it is impossible for some reason add tunable
vfs.zfs.space_map_last_hope, which when set to '1' will tell ZFS to remove
colliding range and retry. This seems to have worked for me, but I consider
it highly risky to use.
MFC after: 1 week
Diffstat (limited to 'usr.sbin/service')
0 files changed, 0 insertions, 0 deletions
