PRs for tag '2tb'
This is an experimental report containing PRs for tag '2tb' as of 4-18-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':
|o||2013/01/24||usb/175551||usb||[2tb] Seagate 2TB USB extern hard disk have errors with FreeBSD|
|o||2010/01/31||bin/143389||[2tb] [patch] fdisk(8) cannot handle above 1TB under i386 system.|
|f||2009/10/11||kern/139510||pjd||[geom] [2tb] gmirror disappears after boot on 2T disks|
|o||2007/12/20||kern/118912||fs||[2tb] disk sizing/geometry problem with large array|
|s||2007/04/02||bin/111146||fs||[2tb] fsck(8) fails on 6T filesystem|
|o||2007/01/11||bin/107829||fs||[2TB] fdisk(8): invalid boundary checking in fdisk / wraps value of > 2TB filesystem.|
|o||2005/03/26||kern/79251||geom||[2TB] newfs fails on 2.6TB gbde device|
|o||2000/05/29||kern/18874||fs||[2TB] 32bit NFS servers export wrong negative values to 64bit clients|
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.