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

Site Navigation

PRs for tag '2tb'

This is an experimental report containing PRs for tag '2tb' as of 4-24-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

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


PRs for tag '2tb':
SSubmittedTrackerResp.Description
o2013/01/24usb/175551usb[2tb] Seagate 2TB USB extern hard disk have errors with FreeBSD
o2010/01/31bin/143389[2tb] [patch] fdisk(8) cannot handle above 1TB under i386 system.
f2009/10/11kern/139510pjd[geom] [2tb] gmirror disappears after boot on 2T disks
o2007/12/20kern/118912fs[2tb] disk sizing/geometry problem with large array
s2007/04/02bin/111146fs[2tb] fsck(8) fails on 6T filesystem
o2007/01/11bin/107829fs[2TB] fdisk(8): invalid boundary checking in fdisk / wraps value of > 2TB filesystem.
o2005/03/26kern/79251geom[2TB] newfs fails on 2.6TB gbde device
o2000/05/29kern/18874fs[2TB] 32bit NFS servers export wrong negative values to 64bit clients
8 problems total.

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.