Date: Tue, 30 Sep 2014 01:06:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193875] [zfs] [panic] [reproducable] zfs/space_map.c: solaris assert: sm->sm_space + size <= sm->sm_size Message-ID: <bug-193875-8-CRWZQnjRRr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193875-8@https.bugs.freebsd.org/bugzilla/> References: <bug-193875-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193875 --- Comment #5 from Xin LI <delphij@FreeBSD.org> --- (In reply to Palle Girgensohn from comment #4) > I did not try a newly created pool, it is a large pool with data, one of = two > redundant systems where we use zfs send | ssh | zfs recv to keep them in > sync. The other machine is still on 9.3, and we got this problem after > updating one system to 10.0. So, we cannot really upgrade just yet. Also,= it > shouln't present such a big problem just running an old version...? Since you haven't upgraded the pool, will it be possible for you to downgra= de your kernel/world and see if you can reproduce the problem? > But as you say, there seems to something fishy with the pool, and maybe > there is nothing wrong with the kernel itself.=20 >=20 > Are you sure there are no other ways to fix this but to recreate the pool? > Thera are just Terabytes of data, it will take a week... :-/ Yeah I know =EF=BC=9A=EF=BC=88 > is there no zdb magic or zpool export + scrub + zpool import ditto with > vfs.zfs.recover =3D1 that could help? Unfortunately, space map corruptions are fatal currently. In the future ma= ybe we can implement a tool that traverses all data and rebuild the space map f= rom that, but it's not trivial... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193875-8-CRWZQnjRRr>