-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
l2arc_mfuonly_pos: VERIFY3(tx->tx_txg <= spa_final_dirty_txg(os->os_spa)) failed (64 <= 63) #16714
Labels
Type: Defect
Incorrect behavior (e.g. crash, hang)
Comments
I think this problem goes from L2ARC rebuild not being stopped by |
I've intercepted the log message that causes it, confirming my guess:
|
amotin
added a commit
to amotin/zfs
that referenced
this issue
Nov 19, 2024
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714
13 tasks
gamanakis
pushed a commit
to gamanakis/zfs
that referenced
this issue
Nov 20, 2024
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714
gamanakis
pushed a commit
to gamanakis/zfs
that referenced
this issue
Nov 20, 2024
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714
gamanakis
pushed a commit
to gamanakis/zfs
that referenced
this issue
Nov 20, 2024
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: George Amanakis <gamanakis@gmail.com> Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714 Closes openzfs#16782
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Nov 21, 2024
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: George Amanakis <gamanakis@gmail.com> Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714 Closes openzfs#16782
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Nov 21, 2024
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: George Amanakis <gamanakis@gmail.com> Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714 Closes openzfs#16782
amotin
pushed a commit
that referenced
this issue
Nov 25, 2024
This allowed to debug #16714, fixed in #16782. Without assertions added here it is difficult to figure out what logs cause the problem, since the assertion happens in sync thread context. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Pavel Snajdr <snajpa@snajpa.net> Co-authored-by: Alexander Motin <mav@FreeBSD.org> Closes #16795
ixhamza
pushed a commit
to truenas/zfs
that referenced
this issue
Dec 2, 2024
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: George Amanakis <gamanakis@gmail.com> Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714 Closes openzfs#16782
behlendorf
pushed a commit
to behlendorf/zfs
that referenced
this issue
Dec 3, 2024
This allowed to debug openzfs#16714, fixed in openzfs#16782. Without assertions added here it is difficult to figure out what logs cause the problem, since the assertion happens in sync thread context. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Pavel Snajdr <snajpa@snajpa.net> Co-authored-by: Alexander Motin <mav@FreeBSD.org> Closes openzfs#16795
lundman
pushed a commit
to openzfsonwindows/openzfs
that referenced
this issue
Jan 26, 2025
Without doing that there is a race window on export when history log write by completed rebuild dirties transaction beyond final, triggering assertion. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: George Amanakis <gamanakis@gmail.com> Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc. Closes openzfs#16714 Closes openzfs#16782
lundman
pushed a commit
to openzfsonwindows/openzfs
that referenced
this issue
Jan 26, 2025
This allowed to debug openzfs#16714, fixed in openzfs#16782. Without assertions added here it is difficult to figure out what logs cause the problem, since the assertion happens in sync thread context. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Pavel Snajdr <snajpa@snajpa.net> Co-authored-by: Alexander Motin <mav@FreeBSD.org> Closes openzfs#16795
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Describe the problem you're observing
QEMU Almalinux 9 runner reported
l2arc_mfuonly_pos
as KILLED with this panic:Describe how to reproduce the problem
Saw this as a test result while testing an unrelated PR
https://github.com/tonyhutter/zfs/actions/runs/11598165017/job/32293419930?pr=3
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: