Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'fsck(8)'

This is an experimental report containing PRs for manpage 'fsck(8)' as of Wed Apr 16 07:37:01 2014 UTC. See notes.


PRs for manpage 'fsck(8)':
SSubmittedTrackerResp.Description
o2014/04/03docs/188214docManpage for fsck(8) doesn't say what happens when no -t or -T
o2012/03/29bin/166499fsck(8) behaviour does not match doc (PARTIALLY TRUNCATED INODE)
o2008/06/09bin/124409fsck(8) requires exact entry for mountpoints when executing / bug by design in getfsfile(3) in .../lib/libc/gen/fstab.c
s2007/04/02bin/111146fs[2tb] fsck(8) fails on 6T filesystem
o2006/03/21bin/94810fsfsck(8) incorrectly reports 'file system marked clean' when lost+found fills up
o2005/10/19bin/87651[patch] fsck(8) (on superblock error) tells wrong man page reference
o2005/06/08bin/82037mount(8)/unmount(8)/fsck(8) mount point specification inconsistency.
o2004/08/18bin/70600fsfsck(8) throws files away when it can't grow lost+found
o2001/05/27bin/27687fsfsck(8) wrapper is not properly passing options to fsck_<fstype>
9 problems total.


Notes

GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.