Public issue detail

Stuck D-state investigation for perl at folio_wait_bit

perl shows a repeated `D`-state wait, likely blocked in overlayfs wait via folio_wait_bit.

highpackage: perl-basesource: perlscore: 110reports: 1

Last seen: 2026-07-30 05:33 UTC. Public JSON: /v1/issues/019fa2e2-2716-7f23-a43f-6e55d56b931a

Technical snapshot

This is where Fixer saw the sampled task blocked in the kernel.

Kernel wait stack

  • State: D (disk sleep)
  • Wait site: folio_wait_bit
  • Package: perl-base 5.42.2-3
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
folio_wait_bit
folio_wait_writeback
truncate_inode_partial_folio
truncate_inode_pages_range
ext4_evict_inode
evict
__dentry_kill
dput
ovl_destroy_inode
destroy_inode
do_unlinkat
__x64_sys_unlink

Possible duplicates

These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.

postgres shows a repeated `D`-state wait, likely blocked in overlayfs wait via folio_wait_bit.

highpackage: postgresql-18source: postgresql-18score: 110reports: 2similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, same wait site, very similar public summary

Last seen: 2026-07-27 17:32 UTC. Public page: /issues/019f7e5e-e73c-7041-9856-3d12c7c861f2. Public JSON: /v1/issues/019f7e5e-e73c-7041-9856-3d12c7c861f2

qemu-arm shows a repeated `D`-state wait, likely blocked in overlayfs wait via folio_wait_bit.

highpackage: qemu-usersource: qemuscore: 110reports: 1similarity: 99%

Why this looks related: same classification, same stack or hot path signature, same subsystem, same wait site, very similar public summary

Last seen: 2026-08-01 15:09 UTC. Public page: /issues/019fbcfd-3ef3-7d83-b8b3-3b5a7492f5a5. Public JSON: /v1/issues/019fbcfd-3ef3-7d83-b8b3-3b5a7492f5a5

postgres shows a repeated `D`-state wait, likely blocked in filesystem io wait via folio_wait_bit.

highpackage: postgresql-18source: postgresql-18score: 110reports: 1similarity: 93%

Why this looks related: same stack or hot path signature, same subsystem, same wait site

Last seen: 2026-08-02 10:34 UTC. Public page: /issues/019f5585-a5a6-7803-a19e-61c2b6b11921. Public JSON: /v1/issues/019f5585-a5a6-7803-a19e-61c2b6b11921

Published attempts

No public attempts have been published for this issue yet.