https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-4208 Lustre <p>The DSL Pool Configuration lock should be held when calling dsl_prop_register(). </p> <p>See comments here:</p> <p><a href="https://github.com/zfsonlinux/zfs/blob/master/module/zfs/dsl_pool.c#L947" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/zfsonlinux/zfs/blob/master/module/zfs/dsl_pool.c#L947</a></p> <p>and assertion here:</p> <p><a href="https://github.com/zfsonlinux/zfs/blob/master/module/zfs/dsl_prop.c#L238" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/zfsonlinux/zfs/blob/master/module/zfs/dsl_prop.c#L238</a></p> <p>Therefore osd_zfs will panic on mount if using a debug build of ZFS.</p> LU-4208

dsl_prop_register()) ASSERTION(dsl_pool_config_held(dp)) failed

Bug Major Resolved Fixed Nathaniel Clark Ned Bass patch zfs Mon, 4 Nov 2013 22:53:20 +0000 Fri, 21 Feb 2014 14:18:09 +0000 Fri, 21 Feb 2014 14:18:09 +0000 Lustre 2.4.1 Lustre 2.5.0 Lustre 2.6.0 Lustre 2.6.0 Lustre 2.5.1 0 3 <p><a href="http://review.whamcloud.com/#/c/8172/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/8172/</a></p> <p>Landing this change will take a bit of coordination, since it has a dependency on a ZFS build that exports the needed symbols. I don't really want to add an autoconf check, because the compatibility code would be messy. The DSL pool config lock is an <tt>rrwlock_t</tt> lock, which is a component of ZFS, but the API isn't exported. So without dsl_pool_config_{enter,exit} exported, there's really no clean way to take the lock without duplicating the rrwlock implementation in Lustre.</p> <p>Nathaniel</p> <p>could you please take care of this one?</p> <p>Thanks</p> <p>Peter</p> <p>I think we should add an autoconf check, I don't think it would be that much of an issue. After landing an updated 8172 then we just wait for ZFS 0.6.3 to come out to close the bug.</p> <p>Lustre patches are landed.</p> <p>This can be closed when builds start using zfs 0.6.3</p> <p>This landed for 2.6. Is it needed for b2_4 and b2_5 also?</p> <p>I would say yes.</p> <p>b2_5 and master are both at zfs 0.6.2, b2_4 is using 0.6.1. The current tip of zfs master (as of 2 weeks ago) wasn't stable enough to move to (see <a href="https://github.com/zfsonlinux/zfs/issues/2088" class="external-link" target="_blank" rel="nofollow noopener">ZFS Issue 2088</a>). I will backport the lustre change to both b2_4 and b2_5</p> <p>b2_5 <a href="http://review.whamcloud.com/9256" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9256</a><br/> b2_4 <a href="http://review.whamcloud.com/9255" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9255</a></p> <p>Landed for 2.5.1 and 2.6 but will only take effect once we move to zfs 0.6.3</p> Development Rank 1|hzw7yf: Rank (Obsolete) 11437 Severity