Bug 211037

Summary: [panic] softdep_deallocate_dependencies: got error 6 while accessing filesystem
Product: Base System Reporter: David Gordon <david.gordon>
Component: kernAssignee: freebsd-fs (Nobody) <fs>
Status: Closed Not Enough Information    
Severity: Affects Some People CC: fbsdbugs4, kib, mckusick, pi
Priority: --- Keywords: crash
Version: 10.3-STABLE   
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
Crash stack trace none

Description David Gordon 2016-07-12 16:09:53 UTC
Created attachment 172415 [details]
Crash stack trace

Consistently crash FreeBSD anytime transfer rates raise above 2Gbps (every few days). See attached file for kernel stack trace.

FreeBSD is running nas4free and is installed as a virtual machine over ESX 6.0u1 and mounts files to be shared over iscsi from an EqualLogic SAN. Once disks are mounted, NFS is used to share the files to the network. ESXi, N4032 switch, and nas4free use MTU of 9000+ and are configured to use a lossless priority VLAN for SAN traffic.

I would be happy to answer any questions about our setup to help resolve this bug.
Comment 1 Konstantin Belousov freebsd_committer freebsd_triage 2016-07-18 12:18:36 UTC
(In reply to David Gordon from comment #0)
Can you show _exact_ kernel messages before and during the panic, say, 10 lines before the panic message itself and then everything that follows it ?

We do not have 'secondary' panics, so the three lines you demonstrated are puzzling, at least.  It could be that you get two panics, each on the its own CPU, but again, I need to see precise messages first.
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2022-10-17 12:18:02 UTC
Keyword: 

    crash

– in lieu of summary line prefix: 

    [panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>
Comment 3 Kirk McKusick freebsd_committer freebsd_triage 2022-10-17 13:45:58 UTC
Never able to reproduce and did not get any followup information.