Page MenuHomeFreeBSD

explain fsck -f more in detail
ClosedPublic

Authored by wosch on Mar 3 2019, 4:47 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Mar 22, 11:39 PM
Unknown Object (File)
Fri, Mar 22, 11:38 PM
Unknown Object (File)
Fri, Mar 22, 11:38 PM
Unknown Object (File)
Fri, Mar 22, 11:38 PM
Unknown Object (File)
Fri, Mar 8, 3:55 AM
Unknown Object (File)
Jan 7 2024, 12:22 AM
Unknown Object (File)
Jan 7 2024, 12:18 AM
Unknown Object (File)
Jan 7 2024, 12:17 AM
Subscribers

Details

Summary

As discussed in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223491 you may need to run fsck -f on a file system with a corrupt journal due a lying disk. The current man page is not clear about whats happens here. This patch adds a brief explanation.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

0mp requested changes to this revision.Mar 3 2019, 4:59 PM
0mp added a subscriber: 0mp.

Also, please remember to bump the date of the manual page.

sbin/fsck/fsck.8
147 ↗(On Diff #54642)

As per style.mdoc(5) it would be better to stylize it like this:

Running
.Dq Li fsck -f
ignores ...
This revision now requires changes to proceed.Mar 3 2019, 4:59 PM

Your change looks good. I'll approve once you update the suggested mandoc refinement.

Thanks, this seems reasonable to me too.

follow style.mdoc(5) rules

OK from manpages (keep in mind I am only a ports committer ;)

This revision is now accepted and ready to land.Mar 5 2019, 7:02 PM

Looks good, thanks for clarifying -f.

This revision was automatically updated to reflect the committed changes.