Bug 255739
| Summary: | ffs crash in UFS | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | doctor | ||||||
| Component: | misc | Assignee: | freebsd-fs (Nobody) <fs> | ||||||
| Status: | Closed Not Enough Information | ||||||||
| Severity: | Affects Some People | CC: | chris, mckusick | ||||||
| Priority: | --- | ||||||||
| Version: | 13.0-RELEASE | ||||||||
| Hardware: | amd64 | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
|
Description
doctor
2021-05-10 02:42: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. Created attachment 224854 [details]
core file
Created attachment 224855 [details]
info file
adding more information. The vmcore.1 file is 1.1GB 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? |
