[zfs-code] Re: ASSERT failed dn->dn_nlevels > level (0x0 > 0x0) dbuf.c, line: 1523

2006-09-29 Thread Mark Maybee
Darren, I looked a bit at your dumps... in both cases, the problem is that the os_phys block that we read from the disk is garbage: > 0x9377b000::print objset_phys_t { os_meta_dnode = { dn_type = 0 dn_indblkshift = 0 dn_nlevels = 0 dn_nblkptr = 0

[zfs-code] Re: ASSERT failed dn->dn_nlevels > level (0x0 > 0x0) dbuf.c, line: 1523

2006-09-29 Thread Darren J Moffat
Matthew Ahrens wrote: > Darren J Moffat wrote: >> Thanks again for trying. Now what do I do ;-( > > The bug doesn't exist in nevada, right? So try removing your code until > you find what's broken. Yep, Whats more if I use my code to operate on a version 3 pool (crypto bumps the version to 4

[zfs-code] Re: ASSERT failed dn->dn_nlevels > level (0x0 > 0x0) dbuf.c, line: 1523

2006-09-29 Thread Darren J Moffat
Matthew Ahrens wrote: > I just looked at your code and didn't see anything that would be causing > your bugs. I can't speak for the SPA stuff, but the rest looks good. > Here are some general comments: Thanks for looking. > in dmu_object_info_t, you need to decrease the size of doi_pad by 1 >

[zfs-code] Re: ASSERT failed dn->dn_nlevels > level (0x0 > 0x0) dbuf.c, line: 1523

2006-09-29 Thread Matthew Ahrens
Darren J Moffat wrote: > Thanks again for trying. Now what do I do ;-( The bug doesn't exist in nevada, right? So try removing your code until you find what's broken. --matt