Bug 255739 - ffs crash in UFS
Summary: ffs crash in UFS
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 13.0-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-10 02:42 UTC by doctor
Modified: 2021-05-11 23:08 UTC (History)
2 users (show)

See Also:

Attachments
core file (289.04 KB, text/plain)
2021-05-11 18:24 UTC, doctor 		no flags Details
info file (520 bytes, text/plain)
2021-05-11 18:25 UTC, doctor 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description doctor 2021-05-10 02:42:37 UTC 
on 3 occasion I have seen 3 crashes in FFS on a UFS system on 3 separate occasions.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2021-05-10 10:33:37 UTC 
^Triage: assign to fs@, but I will note that without further information there's little we can do to try to diagnose this.
Comment 2 doctor 2021-05-11 18:24:59 UTC 
Created attachment 224854 [details]
core file
Comment 3 doctor 2021-05-11 18:25:39 UTC 
Created attachment 224855 [details]
info file
Comment 4 doctor 2021-05-11 18:26:17 UTC 
adding more information.  The vmcore.1 file is 1.1GB
Comment 5 Kirk McKusick freebsd_committer freebsd_triage 2021-05-11 23:08:39 UTC 
What were the details on the filesystem in question (df information, and ideally the first 100 lines of dumpfs of the filesystem). Were you running it using soft updates or journalled soft updates?

Were there any I/O errors reported for the drive in the system logs.

Did you run fsck on it after the crash, and if so what if any errors did it report/fix?