Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASSERTION(atomic_read(&cvp->cv_waiters) == 0) failed #47

Closed
behlendorf opened this issue Aug 11, 2010 · 3 comments
Closed

ASSERTION(atomic_read(&cvp->cv_waiters) == 0) failed #47

behlendorf opened this issue Aug 11, 2010 · 3 comments

Comments

@behlendorf
Copy link
Contributor

spl-0.4.9-52-g46aa7b3
zfs-0.4.9-2817-g67425a0

$ lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid

$ uname -r
2.6.32-24-generic (x86)

$ sudo ./scripts/zconfig.sh 
test 1 - persistent zpool.cache: PASS
test 2 - scan disks for pools to import: PASS
test 3 - zpool import/export device: PASS
test 4 - zpool insmod/rmmod device: PASS
test 5 - zvol+ext3 volume: 
SPL: Loaded Solaris Porting Layer v0.5.0 (DEBUG mode)
SPLAT: Loaded Solaris Porting LAyer Tests v0.5.0
ZFS: Loaded ZFS Filesystem v0.5.0 (DEBUG mode)
 tank/fish: unknown partition table
 tank/fish: unknown partition table
 tank/fish: tank/fish1
kjournald starting.  Commit interval 5 seconds
SPLError: 7488:0:(spl-condvar.c:76:__cv_destroy()) ASSERTION(atomic_read(&cvp->cv_waiters) == 0) failed
SPLError: 7488:0:(spl-condvar.c:76:__cv_destroy()) SPL PANIC
SPL: Showing stack for process 7488
Pid: 7488, comm: zvol/0 Tainted: P           2.6.32-24-generic #39-Ubuntu
Call Trace:
 [] ? printk+0x1d/0x1f
 [] spl_debug_dumpstack+0x2a/0x40 [spl]
 [] spl_debug_bug+0x89/0xd0 [spl]
 [] __cv_destroy+0x28c/0x2a0 [spl]
 [] zfs_range_unlock+0x443/0x800 [zfs] 
 [] ? dmu_read+0x1b4/0x290 [zfs]
 [] ? mutex_lock+0x19/0x40
 [] ? zil_itx_assign+0xa1/0x180 [zfs]
 [] zvol_write+0xe1/0x510 [zfs]
 [] taskq_thread+0x205/0x7b0 [spl]
 [] ? schedule+0x44c/0x840
 [] ? default_wake_function+0x0/0x20
 [] ? taskq_thread+0x0/0x7b0 [spl]
 [] kthread+0x74/0x80
 [] ? kthread+0x0/0x80
 [] kernel_thread_helper+0x7/0x10

It doesn't appear to hit every run, perhaps 1 in 5.

@behlendorf
Copy link
Contributor Author

Observed in what will be zfs-0.5.1 when it's tagged.

@behlendorf
Copy link
Contributor Author

Observed again in the zfs-0.5.1 tag while running the zfault tests under FC13, 2.6.34.6-47.fc13.x86_64. It's still rare.

@behlendorf
Copy link
Contributor Author

This is believed to be fixed by the cv changes in the zfs range locking code.

akatrevorjay added a commit to akatrevorjay/zfs that referenced this issue Dec 16, 2017
# This is the 1st commit message:
Merge branch 'master' of https://github.com/zfsonlinux/zfs

* 'master' of https://github.com/zfsonlinux/zfs:
  Enable QAT support in zfs-dkms RPM

# This is the commit message openzfs#2:

Import 0.6.5.7-0ubuntu3

# This is the commit message openzfs#3:

gbp changes

# This is the commit message openzfs#4:

Bump ver

# This is the commit message openzfs#5:

-j9 baby

# This is the commit message openzfs#6:

Up

# This is the commit message openzfs#7:

Yup

# This is the commit message openzfs#8:

Add new module

# This is the commit message openzfs#9:

Up

# This is the commit message openzfs#10:

Up

# This is the commit message openzfs#11:

Bump

# This is the commit message openzfs#12:

Grr

# This is the commit message openzfs#13:

Yay

# This is the commit message openzfs#14:

Yay

# This is the commit message openzfs#15:

Yay

# This is the commit message openzfs#16:

Yay

# This is the commit message openzfs#17:

Yay

# This is the commit message openzfs#18:

Yay

# This is the commit message openzfs#19:

yay

# This is the commit message openzfs#20:

yay

# This is the commit message openzfs#21:

yay

# This is the commit message openzfs#22:

Update ppa script

# This is the commit message openzfs#23:

Update gbp conf with br changes

# This is the commit message openzfs#24:

Update gbp conf with br changes

# This is the commit message openzfs#25:

Bump

# This is the commit message openzfs#26:

No pristine

# This is the commit message openzfs#27:

Bump

# This is the commit message openzfs#28:

Lol whoops

# This is the commit message openzfs#29:

Fix name

# This is the commit message openzfs#30:

Fix name

# This is the commit message openzfs#31:

rebase

# This is the commit message openzfs#32:

Bump

# This is the commit message openzfs#33:

Bump

# This is the commit message openzfs#34:

Bump

# This is the commit message openzfs#35:

Bump

# This is the commit message openzfs#36:

ntrim

# This is the commit message openzfs#37:

Bump

# This is the commit message openzfs#38:

9

# This is the commit message openzfs#39:

Bump

# This is the commit message openzfs#40:

Bump

# This is the commit message openzfs#41:

Bump

# This is the commit message openzfs#42:

Revert "9"

This reverts commit de488f1.

# This is the commit message openzfs#43:

Bump

# This is the commit message openzfs#44:

Account for zconfig.sh being removed

# This is the commit message openzfs#45:

Bump

# This is the commit message openzfs#46:

Add artful

# This is the commit message openzfs#47:

Add in zed.d and zpool.d scripts

# This is the commit message openzfs#48:

Bump

# This is the commit message openzfs#49:

Bump

# This is the commit message openzfs#50:

Bump

# This is the commit message openzfs#51:

Bump

# This is the commit message openzfs#52:

ugh

# This is the commit message openzfs#53:

fix zed upgrade

# This is the commit message openzfs#54:

Bump

# This is the commit message openzfs#55:

conf file zed.d

# This is the commit message #56:

Bump
jkryl referenced this issue in mayadata-io/cstor Mar 7, 2018
jkryl referenced this issue in mayadata-io/cstor Mar 7, 2018
jkryl referenced this issue in mayadata-io/cstor Mar 8, 2018
richardelling pushed a commit to richardelling/zfs that referenced this issue Oct 15, 2018
pcd1193182 pushed a commit to pcd1193182/zfs that referenced this issue Apr 17, 2019
sdimitro pushed a commit to sdimitro/zfs that referenced this issue Dec 7, 2021
On 5.11 kernels, the `--call-graph dwarf,8192` option to perf causes
it to crash. This change allows callers to specify a different perf
invocation via the PERF_RECORD_CMD environment variable.
anodos325 pushed a commit to anodos325/zfs that referenced this issue Mar 18, 2022
FreeBSD: Fix zfsd auto online
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant