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

Site Navigation

PRs for tag 'ufs'

This is an experimental report containing PRs for tag 'ufs' as of 4-19-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 'ufs':
SSubmittedTrackerResp.Description
o2013/05/23kern/178854fs[ufs] FreeBSD kernel crash in UFS
o2013/04/05kern/177658fs[ufs] FreeBSD panics after get full filesystem with ufs snapshot
o2013/01/06kern/175071fs[ufs] [panic] softdep_deallocate_dependencies: unrecovered I/O error
o2012/12/08kern/174279fs[ufs] UFS2-SU+J journal and filesystem corruption
o2012/05/16kern/167979fs[ufs] DIOCGDINFO ioctl does not work on 8.2 file systems
o2012/04/13kern/166912fs[ufs] [panic] Panic after converting Softupdates to journaled softupdates
o2012/02/29kern/165559[ufs] [patch] ufsmount.h uses the 'export' keyword as a structure member name
o2012/01/25kern/164472fs[ufs] fsck -B panics on particular data inconsistency
o2012/01/15kern/164184fs[ufs] [panic] Kernel panic with ufs_makeinode
o2011/10/21kern/161864fs[ufs] removing journaling from UFS partition fails on gpt-labelled disk
o2011/09/28kern/161112fs[ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3
f2011/09/20kern/160860fs[ufs] Random UFS root filesystem corruption with SU+J [regression]
o2011/08/19kern/159930fs[ufs] [panic] kernel core
p2011/04/21kern/156545fs[ufs] mv could break UFS on SMP systems
o2011/04/05kern/156193fs[ufs] [hang] UFS snapshot hangs && deadlocks processes
o2010/12/10kern/152991[ufs] false disk full with a too slow flash module
o2010/10/06kern/151251fs[ufs] Can not create files on filesystem with heavy usage
o2010/06/03kern/147420fs[ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt inode)
o2010/05/18kern/146708fs[ufs] [panic] Kernel panic in softdep_disk_write_complete
o2010/03/31kern/145246fs[ufs] dirhash in 7.3 gratuitously frees hashes when it shouldn't [regression]
o2010/03/21kern/144929fs[ufs] [lor] vfs_bio.c + ufs_dirhash.c
o2009/12/27kern/142068fs[ufs] BSD labels are got deleted spontaneously
o2009/08/31kern/138421fs[ufs] [patch] remove UFS label limitations
o2009/07/21kern/136968fs[ufs] [lor] ufs/bufwait/ufs (open)
o2009/07/20kern/136945fs[ufs] [lor] filedesc structure/ufs (poll)
o2009/06/11kern/135469fs[ufs] [panic] kernel crash on md operation in ufs_dirbad
o2009/03/23kern/132960fs[ufs] [panic] panic:ffs_blkfree: freeing free frag
o2009/03/05kern/132331fs[ufs] [lor] LOR ufs and syncer
o2008/11/27kern/129231fs[ufs] [patch] New UFS mount (norandom) option - mostly useful for building redundant NFS servers
o2008/10/01kern/127787fs[lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfslock, user map/vfs
o2008/08/05kern/126287fs[ufs] [panic] Kernel panics while mounting an UFS filesystem with snapshot enabled
a2008/07/14kern/125613trasz[ufs] [patch] ACL problems with special files
o2007/11/25bin/118249fs[ufs] mv(1): moving a directory changes its mtime
o2007/11/10kern/117954fs[ufs] dirhash on very large directories blocks the machine for tens of seconds
o2007/07/17kern/114676fs[ufs] snapshot creation panics: snapacct_ufs2: bad block
o2007/04/17kern/111782fs[ufs] dump(8) fails horribly for large filesystems
o2006/12/01kern/106107fs[ufs] left-over fsck_snapshot after unfinished background fsck if filesystem clean
o2006/10/14kern/104406fs[ufs] Processes get stuck in "ufs" state under persistent CPU load
o2006/03/23kern/94849fs[ufs] rename on UFS filesystem is not atomic
o2006/03/21kern/94769fs[ufs] Multiple file deletions on multi-snapshotted filesystems causes hang
o2004/10/22bin/73019fs[ufs] fsck_ufs(8) cannot alloc 607016868 bytes for inoinfo
o2004/07/13kern/68978fs[panic] [ufs] crashes with failing hard disk, loose pointers in kernel?
42 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.