Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Aug 2018 14:30:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 230732] Panic when using soft updates on a GELI volume in 11.2
Message-ID:  <bug-230732-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230732

            Bug ID: 230732
           Summary: Panic when using soft updates on a GELI volume in 11.2
           Product: Base System
           Version: 11.2-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: 2t8mr7kx9f@protonmail.com

Created attachment 196318
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D196318&action=
=3Dedit
Screenshot of the panic message

After updating to 11.2-RELEASE, FreeBSD panics when there is heavy disk
activity on a GELI volume with soft updates enabled.

I can reproduce this by duplicating a 8TB volume via rsync to the target di=
sk,
it panics every time with the same message:
"panic: softdep_deallocate_dependencies: dangling deps"

Disabling soft updates (tunefs -n disable) will allow the operation to fini=
sh.

The system is stable otherwise (memtest86 returns ok after a night of testi=
ng),
and the backup worked flawlessly on 11.1 and a volume without GELI on 11.2.

Attached you will find a screenshot of the panic, unfortunately I was not a=
ble
to get this in text form.

There has also been a second report with the same issue on reddit:
https://www.reddit.com/r/freebsd/comments/8uylxc/softdep_panics_on_112relea=
se/

Please let me know if I can provide any further information, I am happy to =
help
to get this cleared up.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230732-227>