Summary: | [panic] handle_written_inodeblock: Invalid link count -1 for inodedep | ||
---|---|---|---|
Product: | Base System | Reporter: | Christos Chatzaras <chris> |
Component: | kern | Assignee: | freebsd-fs (Nobody) <fs> |
Status: | Open --- | ||
Severity: | Affects Only Me | CC: | lwhsu, mckusick, rpilania |
Priority: | --- | Keywords: | crash |
Version: | 13.0-STABLE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
Christos Chatzaras
2021-04-18 21:54: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> Hi Team, we are also facing same issue. It is very difficult to reproduce it. It happens once out of 20-30 times on reboot. Version String: FreeBSD 13.0-RELEASE-p13 #0: Mon Apr 10 23:08:53 IST 2023 /usr/build/iproot/freebsd/mods/src/sys/amd64/compile/MESSAGING_GATEWAY.amd64 Panic String: handle_written_inodeblock: Invalid link count -1 for inodedep 0xfffff80117296000 Dump Parity: 3386838829 Bounds: 0 Dump Status: good Not able to do it repeatedly. One way i was able to reproduce it only one time. 1. Downloaded some files. 2. Enabled console logs in boot/loader.conf and enabled rc debugging in rc.conf 3. Reboot the system. It looks like due uncleaned shutdown it might be causing some file system corruprtion. Platform vmware (VMware Virtual Platform) Disk 0 200GB VMware Virtual disk 2.0 at mpt0 bus 0 scbus2 target 0 lun 0 RAM Total 8192M Swap 6 GB Any idea by when it can be fixed. I have not been able to reproduce this panic with our existing tests. If you can find a script that will produce this panic let me know and I will track it down. Note that there has been a fix for this panic message in 14.0, but it fixed a problem that was introduced during the 14.0 development so is not relevant to the 13 releases. |