Summary: | makefs command creates UFS fs image with bad summary info when size option (-s) is specified | ||
---|---|---|---|
Product: | Base System | Reporter: | Jane <jane062019a> |
Component: | bin | Assignee: | Greg Lehey <grog> |
Status: | Open --- | ||
Severity: | Affects Some People | CC: | emmecerre, fs, grog, imp, jane062019a, jfc, lwhsu |
Priority: | --- | ||
Version: | 13.2-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Jane
2023-09-11 17:50:35 UTC
The image isn't corrupt. It's perfectly readable. Only the summary information is incorrect, which is just metadata that fsck reconstructs. It is a problem that needs to be fixed, but isn't an image with bad data user data. Also, you should be able to fsck the image directly w/o needing the md device. I'll take a look at this, as it potentially affects the boot loader automation we're doing. Thanks for the information. This makes sense: the systems used these fs (mounted in RO) without issues for a while.I noticed the issue only during a random check (the "preen" fsck at boot time is always clean). Now I found a temporary workaround creating the fs with some additional options ("-o bsize=4096 -o density=8192"), but I'll remove them when the fix will be available. Thanks again! Bug #277739 is similar except fsck wants to clear an inode while rebuilding a cylinder group. ^Triage: committer's bit was taken in for safekeeping. ^Triage: reassign by request. It turns out only the ports bit was taken into safekeeping, not the src bit. |