-
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
Memory reclaim deadlock #232
Milestone
Comments
FransUrbo
referenced
this issue
in FransUrbo/zfs
Apr 24, 2013
+ Use --with-linux{-obj} values from previous ./configure run. + Use --with-spl{-obj} values from previous ./configure run. + _configure was specified earlier, but never used. Use it!
fuhrmannb
pushed a commit
to fuhrmannb/cstor
that referenced
this issue
Nov 3, 2020
…enzfs#232) (openzfs#239) Signed-off-by: Vitta <[email protected]>
sdimitro
pushed a commit
to sdimitro/zfs
that referenced
this issue
Dec 11, 2020
Since we have embedded slog metaslabs, the calculation in metaslab_group_get_space() is no longer accurate, because it includes all metaslabs (including the ZIL metaslab), not just the ones in the requested group (which is of a particular class, e.g. normal, non-log class). Since the returned space is larger than expected, when metaslab_class_fragmentation() divides by the class's space, we may get a result >100.
mmaybee
pushed a commit
to mmaybee/openzfs
that referenced
this issue
Apr 6, 2022
old: checkpoint: Extent { location: DiskLocation( 72057594041394288, ), size: 576000, }, new: checkpoint: Extent { location: DiskLocation { disk: DiskId( 1, ), offset: 1775348224, }, size: 576000, },
EchterAgo
pushed a commit
to EchterAgo/zfs
that referenced
this issue
Aug 4, 2023
Signed-off-by: Andrew Innes <[email protected]>
ixhamza
pushed a commit
to ixhamza/zfs
that referenced
this issue
May 23, 2024
[stable/dragonfish] Merge zfs-2.2.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following deadlock was observed when zio->create()->cv_init()->kmem_alloc(..., KM_SLEEP) entered direct memory reclaim. It unfortunately ended waiting for the cv->tx_quiesce_done_cv but this could never occur because this thread was responsible for finishing syncing the current txg. Deadlock.
The text was updated successfully, but these errors were encountered: