similar to: 6346204 NFSv4 client suffers undetected write errors to full file system

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 81369c96cb78f5d0d43b3f267deb0c8477aeca83 Log message: 6300246 nfs4_delegation_accept(): Deadlock: cycle in blocking chain 6321564 r_statev4_lock shouldn''t be held over dnlc_update() Files: update: usr/src/uts/common/fs/nfs/nfs4_callback.c update: usr/src/uts/common/fs/nfs/nfs4_vnops.c

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 76b3a89dc4ebc9f389aa37dd4f7e76275266630c Log message: PSARC 2005/487 sysidtool(1m) Integrated NFSv4 Prompts 6231897 ON changes in support of 5110062: nuke sysidnfs4(1m) Files: create: deleted_files/usr/src/cmd/fs.d/nfs/sysidnfs4/Makefile create: deleted_files/usr/src/cmd/fs.d/nfs/sysidnfs4/config_nfs4.c create:

Since upgrading S4 DCs I am see the following message in log.samba - DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested: FFFFFFF8Unable to fetch value for secret BCKUPKEY_13bb48fc-0844-4736-9972-e26453333856, are we an undetected RODC? DsCrackNames: Unsupported operation requested: FFFFFFF8DsCrackNames: Unsupported operation requested:

Garming - thanks for your quick response. That link you gave me has Samba 3.x patches. I didn't notice any links to 4.x patches. Official Distro Releases are often behind the current stable release, generally. In fact, when I first installed Samba4 the Linux version was more recent than the Ubuntu version. This lag is probably due to abundance of caution and/or lack of manpower. I

On Mon, 19 Sep 2016 10:50:25 -0400 Adam Tauno Williams via samba <samba at lists.samba.org> wrote: > On Mon, 2016-09-19 at 10:45 -0400, Adam Tauno Williams via samba > wrote: > > Since upgrading S4 DCs I am see the following message in log.samba - > > The message "Unable to fetch value for secret BCKUPKEY_13bb48fc-0844 > > -4736-9972-e26453333856, are we an

If it is that bug that you're referencing, besides obviously upgrading, you could try to patch it yourself. Whether or not you need to patch this, probably depends on whether or not your users are actually seeing issues. All that seems to happen is that it's entering a failure case when it hasn't actually failed. https://www.samba.org/samba/patches/ Cheers, Garming On 04/07/16

I upgraded from 4.1.23 to 4.2.12 and am now getting (lots of) messages: Unable to fetch value for secret BCKUPKEY_, are we an undetected RODC? I found an almost identical message (titled: "Update samba4 from 4.1.17 to 4.2.1 failed") on the web from May 22, 2015 at: http://samba.2283325.n4.nabble.com/Update-samba4-from-4-1-17-to-4-2-1-failed-td4686215.html but saw no resolution other

Author: praks Repository: /hg/zfs-crypto/gate Revision: 4c3b7ab574cc73502effa96c11c293e04fd54309 Log message: 6256083 Need a lightweight file page mapping mechanism to substitute segmap 6387639 segkpm segment set to incorrect size for amd64 Files: create: usr/src/uts/common/vm/vpm.c create: usr/src/uts/common/vm/vpm.h update: usr/src/pkgdefs/SUNWhea/prototype_com update:

Author: marks Repository: /hg/zfs-crypto/gate Revision: d3160869d28dca623e514dc1f38e84d9335c2a55 Log message: 6362908 nfsv4-test: RENAME does not check PERM with NFSv4/ZFS 6372549 nfsv4 server returns OK for SETATTR of size on a symlink over ZFS, INVAL is expected Files: update: usr/src/uts/common/fs/zfs/zfs_acl.c update: usr/src/uts/common/fs/zfs/zfs_vnops.c

Author: thurlow Repository: /hg/zfs-crypto/gate Revision: 1713bd2d1b7b2466298721235c1f98e4e01b0be8 Log message: 6344186 NFSv3 needs to support .zfs (like NFSv4 already does) Files: update: usr/src/cmd/fs.d/nfs/mountd/mountd.c update: usr/src/cmd/fs.d/nfs/mountd/mountd.h update: usr/src/cmd/fs.d/nfs/nfslog/fhtab.h update: usr/src/cmd/fs.d/nfs/nfslog/nfslog_elf.c update:

Author: calum Repository: /hg/zfs-crypto/gate Revision: fbc718ddef873be386b04b6eae2b298d174fce12 Log message: PSARC/2006/313 NFSv4: nfsd "-s" distributed stable storage 6244819 NFSv4 needs distributed stable storage to work on Cluster HA-NFS Files: update: usr/src/cmd/fs.d/nfs/nfsd/Makefile update: usr/src/cmd/fs.d/nfs/nfsd/nfsd.c update: usr/src/uts/common/fs/nfs/nfs4_srv.c update:

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 4af930f29a665f04c4cf91ef1fbc049fb427a304 Log message: 6417056 nfssrv should use doors/xdr as its IPC mech to mountd(1m) Files: create: deleted_files/usr/src/uts/common/rpcsvc/nfsauth_prot.x create: usr/src/cmd/fs.d/nfs/mountd/nfsauth_xdr.c create: usr/src/uts/common/fs/nfs/nfs_auth_xdr.c create: usr/src/uts/common/nfs/auth.h delete:

Author: sdussud Repository: /hg/zfs-crypto/gate Revision: 5c763b375c39e588ef67da67923415de517cd8ec Log message: 6322778 memleaks at crdup/crnetadjust Files: update: usr/src/uts/common/fs/nfs/nfs3_vnops.c update: usr/src/uts/common/fs/nfs/nfs4_vnops.c update: usr/src/uts/common/fs/nfs/nfs_acl_vnops.c

Author: marks Repository: /hg/zfs-crypto/gate Revision: 49eca6287e6a581e3e46ada9d34a54b7665027b1 Log message: 6434606 getfacl/setfacl of files/dirs over NFSv4 with ZFS underneath fail Files: update: usr/src/uts/common/fs/fs_subr.c

dear smbfs maintainers! i sent this mail to you, since i got no answer from sending it to the "M:" entry of SMBFS. _______________ i had problems with setting permissions on a mounted smb file system. therefore i took a look at the smbfs code and a suspicious code part caught my eye. IMHO the patched line can't be correct, because comparing uids to gids doesn't make any sense.

Hello, [ I've just reported this as https://bugzilla.samba.org/show_bug.cgi?id=2116 ] ------------------ rsync-2.6.3 can fail to report a write error. Here's a demonstration, writing to a full partition: You can reproduce it like this: $ echo foo > in $ strace -f -o log rsync in /full/tmp $ grep 'write.*ENOSP' log 4787 write(1, "foo\n", 4) =

Author: marks Repository: /hg/zfs-crypto/gate Revision: 30d7e3669aa20772767cb9726d60c32659192c23 Log message: 6395977 unpack dump core when run over NFSv4 over ZFS Files: update: usr/src/cmd/compress/compress.c update: usr/src/cmd/pack/pack.c update: usr/src/cmd/unpack/unpack.c

Author: rmesta Repository: /hg/zfs-crypto/gate Revision: 7413fc53072f4145c1b3ac0e2169234084b4c6ab Log message: 6417056 nfssrv should use doors/xdr as its IPC mech to mountd(1m) (fix unref) Files: create: deleted_files/usr/src/cmd/fs.d/nfs/mountd/svc_local.c delete: usr/src/cmd/fs.d/nfs/mountd/svc_local.c

hi there - is it possible to share a directory via samba and (kernel-)nfsv4 in parallel and make samba use (ie.: read, write and enforce) nfsv4 acls to implement winnt-acls? i know that using nfs3 and posix acls is working halfway okay, but couldn't find anything useful for nfsv4 and the associated acls - sorry if i missed something obvious. i played around with the nfs4acl_xattr and

hi all, i'm managing a large installation of a dovecot cluster in director + NFS backend architecture and we are moving from NFSv3 to NFSv4. Our NFS server is a Netapp in clustered mode and reading technical specs of NFSv4 delegation feature it seems that enabling delegation in this type of dovecot architecture should bring great benefits: only one backend server access a specific mailbox at a