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

Site Navigation

PRs for tag 'ntfs'

This is an experimental report containing PRs for tag 'ntfs' 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 'ntfs':
SSubmittedTrackerResp.Description
o2013/08/06kern/181082fs[fuse] [ntfs] Write to mounted NTFS filesystem using FUSE causes instant freeze/crash
o2009/07/17kern/136873fs[ntfs] Missing directories/files on NTFS volume
o2008/02/09kern/120483fs[ntfs] [patch] NTFS filesystem locking changes
o2008/02/09kern/120482fs[ntfs] [patch] Sync style changes between NetBSD and FreeBSD ntfs filesystem
o2007/11/18kern/118107fs[ntfs] [panic] Kernel panic when accessing a file at NTFS file system [regression]
o2007/07/24kern/114847fs[ntfs] [patch] [request] dirmask support for NTFS ala MSDOSFS
o2006/09/08kern/103035fs[ntfs] Directories in NTFS mounted disc images appear as empty files in Samba export
o2006/06/22kern/99290fs[ntfs] mount_ntfs ignorant of cluster sizes
o2006/05/17kern/97377fs[ntfs] [patch] syntax cleanup for ntfs_ihash.c
o2004/11/03kern/73484fs[ntfs] Kernel panic when doing `ls` from the client side (running Solaris 8) on an NFS exported ntfs file system in 4.10
o2004/09/15kern/71774fs[ntfs] NTFS cannot "see" files on a WinXP filesystem
11 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.