PRs for manpage 'fsck(8)'
This is an experimental report containing PRs for manpage 'fsck(8)' as of Fri May 30 07:37:06 2014 UTC. See notes.
PRs for manpage 'fsck(8)':
|o||2014/04/03||docs/188214||doc||Manpage for fsck(8) doesn't say what happens when no -t or -T|
|o||2012/03/29||bin/166499||fsck(8) behaviour does not match doc (PARTIALLY TRUNCATED INODE)|
|o||2008/06/09||bin/124409||fsck(8) requires exact entry for mountpoints when executing / bug by design in getfsfile(3) in .../lib/libc/gen/fstab.c|
|s||2007/04/02||bin/111146||fs||[2tb] fsck(8) fails on 6T filesystem|
|o||2006/03/21||bin/94810||fs||fsck(8) incorrectly reports 'file system marked clean' when lost+found fills up|
|o||2005/10/19||bin/87651||[patch] fsck(8) (on superblock error) tells wrong man page reference|
|o||2005/06/08||bin/82037||mount(8)/unmount(8)/fsck(8) mount point specification inconsistency.|
|o||2004/08/18||bin/70600||fs||fsck(8) throws files away when it can't grow lost+found|
|o||2001/05/27||bin/27687||fs||fsck(8) wrapper is not properly passing options to fsck_<fstype>|
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.