thr3ads.net - search: "nfssvc"

2009 Nov 23

1

NFS4 issue

...t4 directories. For a couple of weeks we had a small number of users using the system with no issues, today we added 7 users and the system crashed and did not perform correctly since. Nov 23 10:20:03 sulphur rpc.idmapd[5199]: nfsdcb: id '-2' too big! Nov 23 10:42:25 sulphur nfsd[27306]: nfssvc: Setting version failed: errno 16 (Device or resource busy) Nov 23 10:42:25 sulphur nfsd[27306]: nfssvc: unable to bind UPD socket: errno 98 (Address already in use) Nov 23 10:42:26 sulphur kernel: slab error in kmem_cache_destroy(): cache `nfsd4_files': Can't free all objects Nov 23 10:...

"nfsd: non-standard errno: -512"

2009 Oct 12

0

"nfsd: non-standard errno: -512"

CentoOS 5.3, 2.6.18-164.el5. ocfs2-tools-1.4.3-1.el5 ocfs2-2.6.18-164.el5-1.4.4-1.el5 I have NFS Sharing ocfs2 volume over NFS3, and sometimes NFS server stop with error: "nfsd: non-standard errno: -512" Oct 12 17:01:22 piano nfsd[9885]: nfssvc: Setting version failed: errno 16 (Device or resource busy) Oct 12 17:01:22 piano nfsd[9885]: nfssvc: unable to bind UPD socket: errno 98 (Address already in use) Oct 12 17:01:24 piano nfsd[9961]: nfssvc: Setting version failed: errno 16 (Device or resource busy) Oct 12 17:01:24 piano nfsd[9961]: n...

Panic in nfs/ffs after upgrade from 6.2 to 6.3-RELEASE

2008 Aug 16

0

Panic in nfs/ffs after upgrade from 6.2 to 6.3-RELEASE

...000,4000) at getnewbuf+0x1bb getblk(c5964cc0,0,0,4000,0,...) at getblk+0x360 cluster_read(c5964cc0,46e5,0,0,0,...) at cluster_read+0xde ffs_read(e78e7b08) at ffs_read+0x25f VOP_READ_APV(c0a65560,e78e7b08) at VOP_READ_APV+0x38 nfsrv_read(c69b3800,c520d900,c532f900,e78e7c98,0,...) at nfsrv_read+0xb16 nfssvc_nfsd(c532f900) at nfssvc_nfsd+0x435 nfssvc(c532f900,e78e7d04) at nfssvc+0x1c0 syscall(3b,3b,3b,1,0,...) at syscall+0x2bf Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280bdf17, esp = 0xbfbfeb0c, ebp = 0xbfbfeb28 --- Uptime: 12h24m16s Dumping 1023 MB (...

panic: ffs_valloc: dup alloc

2006 Mar 13

2

panic: ffs_valloc: dup alloc

I get the above panic after nfs clients attach to this nfs server and being read/write ops on it after an unclean shutdown. I've fsck'ed the fs, and it marks it as clean, but I get this every time. It's an NFS share of a GEOM stripe (about 2TB). mode = 0100600, inum = 58456203, fs = /mnt panic: ffs_valloc: dup alloc I do have dumps from two crashes so far. This is

[PATCH -next 000/491] treewide: use fallthrough;

2020 Mar 11

0

[PATCH -next 000/491] treewide: use fallthrough;

[PATCH -next 000/491] treewide: use fallthrough;

2020 Mar 11

0

[PATCH -next 000/491] treewide: use fallthrough;

[PATCH -next 000/491] treewide: use fallthrough;

2020 Mar 11

0

[PATCH -next 000/491] treewide: use fallthrough;