PRs for tag 'nfs'
This is an experimental report containing PRs for tag 'nfs' as of 5-30-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 'nfs':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2014/02/26 | kern/187094 | [nfs] [patch] FreeBSD DHCP ignores dhcp option interface-mtu | |
| o | 2013/09/05 | kern/181834 | fs | [nfs] amd mounting NFS directories can drive a dead-lock [regression] |
| o | 2013/07/20 | kern/180678 | fs | [NFS] succesfully exported filesystems being reported as failed |
| f | 2013/04/29 | kern/178231 | fs | [nfs] 8.3 nfsv4 client reports "nfsv4 client/server protocol prob err=10026" |
| o | 2013/04/19 | kern/177971 | fs | [nfs] FreeBSD 9.1 nfs client dirlist problem w/ nfsv3,rsize=4096,wsize=4096 |
| f | 2012/11/16 | kern/173657 | fs | [nfs] strange UID map with nfsuserd |
| o | 2012/08/16 | kern/170680 | fs | [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEASE |
| o | 2012/06/11 | kern/168947 | fs | [nfs] [zfs] .zfs/snapshot directory is messed up when viewed by a Linux client, and ls -l can hang it |
| o | 2012/06/11 | kern/168942 | fs | [nfs] [hang] nfsd hangs after being restarted (not -HUP) and then an export being mounted |
| o | 2012/04/19 | kern/167105 | fs | [nfs] mount_nfs can not handle source exports wiht more then 63 chars |
| o | 2012/03/28 | kern/166477 | fs | [nfs] NFS data corruption. |
| o | 2011/12/21 | kern/163501 | fs | [nfs] NFS exporting a dir and a subdir in that dir to the same host; mountd error message needs improvement |
| o | 2011/10/01 | kern/161205 | fs | [nfs] [pfsync] [regression] [build] Bug report freebsd 9.0 beta 3 |
| o | 2011/08/01 | kern/159351 | fs | [nfs] [patch] - divide by zero in mountnfs() |
| f | 2011/06/16 | kern/157929 | fs | [nfs] NFS slow read |
| o | 2011/01/24 | kern/154255 | net | [nfs] NFS not responding |
| o | 2010/11/07 | kern/152022 | fs | [nfs] nfs service hangs with linux client [regression] |
| o | 2010/10/24 | kern/151681 | net | [nfs] NFS mount via IPv6 leads to hang on client with "ipfw: pullup failed" |
| o | 2010/10/08 | kern/151326 | fs | [nfs] nfs exports fail if netgroups contain duplicate entries |
| o | 2010/09/06 | kern/150336 | fs | [nfs] mountd/nfsd became confused; refused to reload nfs maps |
| o | 2010/05/11 | kern/146502 | fs | [nfs] FreeBSD 8 NFS Client Connection to Server |
| o | 2010/03/30 | kern/145189 | fs | [nfs] nfsd performs abysmally under load |
| o | 2010/02/11 | kern/143825 | fs | [nfs] [panic] Kernel panic on NFS client |
| o | 2010/01/25 | kern/143212 | fs | [nfs] NFSv4 client strange work ... |
| o | 2009/12/14 | kern/141463 | fs | [nfs] [panic] Frequent kernel panics after upgrade from 7.2-STABLE to 8-STABLE [regression] |
| o | 2009/12/01 | kern/141086 | fs | [nfs] [panic] panic("nfs: bioread, not dir") on FreeBSD 7.2-STABLE |
| p | 2009/10/15 | bin/139651 | fs | [nfs] mount(8): read-only remount of NFS volume does not work |
| o | 2009/08/01 | kern/137327 | dfr | [nfs] nfs nlm memery leak |
| p | 2009/07/08 | kern/136470 | fs | [nfs] Cannot mount / in read-only, over NFS |
| o | 2009/06/04 | kern/135237 | [nfs] sendfile(2) and SF_NODISKIO blocks on NFS files | |
| o | 2009/02/04 | kern/131360 | fs | [nfs] poor scaling behavior of the NFS server under load |
| o | 2009/02/03 | kern/131342 | fs | [nfs] mounting/unmounting of disks causes NFS to fail |
| o | 2009/01/16 | kern/130628 | net | [nfs] NFS / rpc.lockd deadlock on 7.1-R |
| o | 2008/12/19 | kern/129760 | fs | [nfs] after 'umount -f' of a stale NFS share FreeBSD locks up |
| f | 2008/12/17 | kern/129719 | net | [nfs] [panic] Panic during shutdown, tcp_ctloutput: inp == NULL |
| o | 2008/11/24 | kern/129132 | [nfs] 7.1-Beta2 nfsd cannot lock | |
| o | 2008/10/28 | kern/128448 | net | [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be resolved (mount_nfs) |
| o | 2008/05/17 | kern/123755 | dfr | [nfs] fstat() fails to return ESTALE with rename()d files |
| o | 2008/03/10 | kern/121566 | rc | [nfs] [request] [patch] ethernet iface should be brought up when booting from a mfs_root over nfs |
| o | 2008/01/19 | kern/119791 | net | [nfs] UDP NFS mount of aliased IP addresses from a Solaris 10 NFS v4 server fail |
| o | 2008/01/13 | kern/119617 | net | [nfs] nfs error on wpa network when reseting/shutdown |
| o | 2007/11/28 | kern/118318 | fs | [nfs] NFS server hangs under special circumstances |
| o | 2007/11/19 | kern/118126 | fs | [nfs] [patch] Poor NFS server write performance |
| o | 2007/07/11 | kern/114506 | [nfs] nfs_readdirrpc doesn't use copyout to write out dirents | |
| o | 2007/07/09 | kern/114451 | [nfs] [patch] prevent NFS server possible crash | |
| o | 2007/05/08 | kern/112528 | net | [nfs] NFS over TCP under load hangs with "impossible packet length" |
| o | 2007/04/19 | kern/111848 | [nfs] removing a file from a diskless nfs mounted root fs hangs | |
| o | 2007/04/02 | kern/111162 | [nfs] nfs_getpages does not restart interrupted system call | |
| o | 2006/12/12 | kern/106646 | [nfs] [patch] Pointer incorrectly cast to ulong | |
| o | 2006/11/07 | kern/105241 | [nfs] problem with Linux NFS server up/down combined with zombied umount process and a manual mount request | |
| o | 2006/05/16 | kern/97329 | [nfs] [patch] code simplification | |
| o | 2006/03/22 | kern/94830 | [nfs] [patch] mount_nfs causes a fatal trap 18 if the value of desiredvnodes is below 1000 | |
| o | 2005/10/05 | kern/86944 | [nfs] [patch] When I use FreeBSD with NFS client, close(2) or a fsync(2) system call gives back ENOLCK. | |
| s | 2005/09/19 | kern/86319 | [nfs] [request] support a "noac" NFS mount flag to turn off the attribute cache | |
| o | 2005/03/29 | kern/79336 | [nfs] NFS client doesn't detect file updates on Novell NFS server | |
| s | 2005/03/15 | kern/78884 | [nfs] [patch] nfs client cache negative lookups | |
| o | 2005/03/10 | kern/78673 | [nfs] [patch] nfs client open resets attrstamp ever if fs is mounted readonly | |
| o | 2005/02/22 | kern/77902 | [nfs] NFS client should use VA_UTIMES_NULL to determine whether to use NFSV3SATTRTIME_TOSERVER | |
| o | 2005/01/12 | kern/76126 | [nfs] [patch] 4.11 client will send a NFS request to rename a file to itself to the NFS server, no error returned | |
| o | 2004/09/05 | kern/71391 | [nfs] [panic] md via NFS file + mount -t ntfs: panic: locking against myself | |
| o | 2004/08/20 | kern/70708 | [nfs] gcore/procfs not finding /proc/pid/file on repeated invocations when running from NFS | |
| s | 2004/06/03 | kern/67545 | [nfs] NFS Diskless Mount Option Suggestion | |
| o | 2004/03/27 | kern/64816 | [nfs] [patch] mmap and/or ftruncate does not work correctly on nfs mounted file systems | |
| a | 2004/02/02 | kern/62278 | [nfs] [patch] NFS server may not set eof flag when reading last chunk of file | |
| o | 2003/10/07 | kern/57696 | [nfs] NFS client readdir terminates prematurely if renaming files | |
| o | 2003/03/03 | kern/48894 | [nfs] Suggested improvements to the NFS read-ahead heuristic code | |
| o | 2002/10/29 | kern/44580 | [nfs] NFS updates file access time when file is modified. | |
| o | 2001/10/19 | kern/31380 | [nfs] NFS rootfs mount failure message too cryptic | |
| o | 2001/05/09 | kern/27232 | [nfs] On NFSv3 mounted filesystems, stat returns st_blksize=512 | |
| o | 2000/10/26 | conf/22308 | [nfs] mounting NFS during boot blocks if host map comes from NIS | |
| o | 2000/10/25 | kern/22291 | [nfs] getcwd(3) fails on recently-modified NFS-mounted dirs | |
| s | 2000/03/22 | conf/17540 | [nfs] NIS host lookups cause NFS mounts to wedge at boot | |
| s | 2000/03/01 | kern/17108 | [nfs] SecureRPC not supported in mount_nfs command | |
| o | 1999/01/22 | kern/9619 | fs | [nfs] Restarting mountd kills existing mounts |
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.