similar to: 2.2.0 panics with quotas and no rpc.rquotad on NFS server

Hi Uli, [Sorry for slow response, life is busy...] On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > we are using ctdb 4.15.5 on RHEL8 (Kernel > 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 > clients. Whenever an ip takeover happens most clients report > something like this: > [Mon Feb 13 12:21:22

The disk free space is being incorrectly reported on our Sun boxes, running Solaris 2.6 and 2.5.1 and Samba 2.0.4b At debug level 5, log.smb reports: [1999/06/12 14:49:07, 5] smbd/quotas.c:disk_quotas(268) disk_quotas: looking for path "." devno=254000004 [1999/06/12 14:49:07, 5] smbd/quotas.c:disk_quotas(318) disk_quotas: looking for quotas file "/home/rand/quotas"

Hi all, I am trying to find out how to disable rquotad and pop (port 443) for rquotad /etc/sysconfig/nfs has it quoted out but yet it is running? How do I disable it? also what about pop? Jerry

Hello everyone, We have a CentOS 6.3 NFSv4 server and client, and we've run into a situation where the client is unable to list "private" (chmod 700-ed) directories, even if the current user owns the directory in question. A bit more background: we're also using Samba 3.5+Winbind to provide authentication and UID/GID mapping against a Windows 2008 R2 domain controller.

Hi, Can someone give me some pointer or links to understand how Filelocking and rquotad works on NFS ? I searched a lot on google , didn't get any good articles on that. -- Regards Basil

I am attempting to use the 'dfree command' option of smb.conf to handle a few special cases and the like for returning disk free information. The Samba server is acting in a PDC role, running Samba 2.2.3a on a SunBlade 100 running Solaris 8, patched with all Recommended patches. From a Windows 2000 box (the only thing I have handy to test with, and will be the bulk of our client

I think the problem is in these few lines: ---------------------------- dovecot: Jul 15 18:13:21 Info: IMAP(01234567g): fs quota add storage dir = /home/h1/sc/01234567g/mail dovecot: Jul 15 18:13:21 Info: IMAP(01234567g): fs quota block device = homesvr:/h1 dovecot: Jul 15 18:13:21 Info: IMAP(01234567g): fs quota mount point = /home/h1 ---------------------------------- Since my configuration

Hello, we are using ctdb 4.15.5 on RHEL8 (Kernel 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 clients. Whenever an ip takeover happens most clients report something like this: [Mon Feb 13 12:21:22 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb 13 12:21:28 2023] nfs: server x.x.253.252 not responding, still trying [Mon Feb 13 12:22:31 2023] nfs: server

> >> On Tue, Jun 07, 2016 at 01:36:52PM -0400, Thomas Schulz wrote: >>> Running Samba 4.3.4 on a Solaris 10 i386 box and Samba 4.4.3 on a >>> Solaris 10 sparc box. >>> I have not looked at the logs for awhile. Just checking now and I see >>> many of the following on both systems. >>> >>> [2016/06/01 11:22:04.402945, 0]

The attached patch is an updated version of my quota-rquotad patch for the quota plugin. Like quota-fs, it only does quota reporting, not enforcing or changing. It also only works on FreeBSD, and possibly other *BSD's. It lacks any and all configure-time tests to see if RPC is even supported, and hardcodes the (Free)BSD way of getting at the NFS server of an NFS mount. I'm mostly mailing

Hi, Last time, I have got no reply, hope this time is better. OS: Solaris 10 Dovecot version : 1.1.1 file system of /var/mail : NFS from Solaris file system of /home : other NFS server that not support rquotad. Here is my setting that works: ---------------------------- plugin { quota = fs:INBOX:mount=/var/mail quota2 = fs:home:noenforcing:mount=/home/h1 } The above settings works. Dovecot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:10.nfs Security Advisory The FreeBSD Project Topic: Remote denial of service in NFS server Category: core Module: sys_nfsserver Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:10.nfs Security Advisory The FreeBSD Project Topic: Remote denial of service in NFS server Category: core Module: sys_nfsserver Announced:

Hi Rolan, I should have corrected that, my bad! It is an NFS client mounting the NFS server, I.e. nfsClient:/some_dir_mounted_via_nfs Si On 21/07/2015 10:20, "devzero at web.de" <devzero at web.de> wrote: >>Over ssh/nfs >>rsync -nuvaz --delete /source/ root at nfsServer.domain.co.uk: > >i don`t see nfs here, i see rsync syncing a local dir via ssh to a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:10.nfs Security Advisory The FreeBSD Project Topic: Remote denial of service in NFS server Category: core Module: sys_nfsserver Announced:

> On Tue, Jun 07, 2016 at 01:36:52PM -0400, Thomas Schulz wrote: > > Running Samba 4.3.4 on a Solaris 10 i386 box and Samba 4.4.3 on a > > Solaris 10 sparc box. > > I have not looked at the logs for awhile. Just checking now and I see > > many of the following on both systems. > > > > [2016/06/01 11:22:04.402945, 0]

I just upgraded to 0.22.0 from 0.18.4 and I''m running into what I think are problems due to changes in scope rules. In my site.pp manifest, I have the following: import "classes/*" node nfsserver { include nfsserver } node webserver { include webserver } class cluster1_sites { website { "example.com": ...; "example2.com": ...; } } node

Hello, I've got a little problem with NFSv4 + Kerberos. I can do a mount with Kerberos with a valid ticket, but read-only. After the mount -vvv -t nfs -o nfsv4,sec=krb5 nfsserver:/ /mount_test/ I can see: #klist: Feb 6 07:22:47 Feb 6 17:22:43 nfs/nfsserver at my.domain #/var/heimdal/kdc.log: 2013-02-06T07:28:26 TGS-REQ clientnfs at my.domain from IPv4:192.168.0.23 for nfs/nfsserver at

Hi, I noticed that my 4.8R box seems to have a NFS problem. I use a FreeBSD/i386 4.8R box as a NFS server, and a FreeBSD/i386 5-CURRENT (as of today) as the NFS client. On the client, /a (on the server) can be mounted successfully with -o rw,bg,intr,mntudp options. However, when a large amount of write operations such as "cp -r /home/ncvs /a" are performed on the client, the

I have moved a Samba installation from an old samba 2.2.8a (on a 2.4.21 kernel) to a new server running Samba 3.0.10 on a SuSE 9.2 (kernel 2.6.8) and I now have a problem using the (same) shares from client W2K machines. When I open "My Computer" window on a client, the drives are marked by a red cross, as if they were disconnected, and the disksize is zero. I can decend into the