Date: Mon, 8 Sep 2008 02:22:19 GMT From: FreeBSD bugmaster <bugmaster@FreeBSD.org> To: freebsd-fs@FreeBSD.org Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org Message-ID: <200809080222.m882MJUL006662@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker Resp. Description
--------------------------------------------------------------------------------
o kern/127029 fs [panic] mount(8): trying to mount a write protected zi
o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file
o kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li
o kern/124621 fs [ext3] Cannot mount ext2fs partition
o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t
o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386,
o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha
o bin/118249 fs mv(1): moving a directory changes its mtime
o kern/116170 fs [panic] Kernel panic when mounting /tmp
o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui
o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala
o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo
o bin/114468 fs [patch] [request] add -d option to umount(8) to detach
o bin/113838 fs [patch] [request] mount(8): add support for relative p
o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show
o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b
o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D
17 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809080222.m882MJUL006662>