similar to: Quotas not working over NFS?

Samba 2.2.0 on SPARC Solaris 8 Configured with: ./configure --with-pam --with-syslog --with-quotas --with-msdfs --with-acl-support I am accessing the share \\server\mgerdts, which is itself an automounted (NFS) directory. That is, /home/mgerdts on server really exists on nfsserver. On nfsserver, rquotad is commented out of inetd.conf. Using smbclient (2.0.7, yeah I know) I do: smbclient

I've been trying to implement the quota system for a Linux cluster. I'm trying it out on a mini-cluster of 4 CentOS 6.3 VMs. I've named them: lion-login lion-sn1 lion-cn01 lion-cn02 All nodes are on the virtual subnet 192.168.56.0/24. lion-sn1 (storage node 1) is the NFS server and the other three nodes are the NFS clients. /etc/exports on lion-sn1: /home 192.168.56.0/24(rw)

Hello everyone! I am currently running Samba 2.0.7 on a RedHat Linux 6.1 box. My user home directories on this box are NFS mounted from another server. Quotas have been enabled on this server and rpc.rquotad is running. On Linux, I can see the user's quotas via a quota -v <username> :- testing:~# quota -v try Disk quotas for user try (uid 1006): Filesystem blocks quota

Hello, I am having some trouble getting quota's to work. When I try to set the quota for a user, it does not show up when I run repquota. I am doing this on a Redhat (RHEL5) machine (I assume it is the same on Centos). I think I am missing a step, but this is what I am doing: (1) I add usrquota to the /etc/fstab file, then reboot LABEL=/home /home ext3 defaults,usrquota 1 2 (2) Verify

hi all, I hope you can help me with a strange quota/nfs/XFS behavior... I'm using Centos 5.6 on both a nfs server and client. Both are 64-bit, and using a recent kernel: NFS server: Linux fs2.priv 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:22:04 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux NFS client: Linux nx8.priv 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:22:04 EDT 2011 x86_64 x86_64 x86_64

-----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:

Should I report this as a bug somewhere? Or is it just a problem with the old fedora box, probably fixed long ago and not relevant to the centos list? On the server side, theme4, a very old fedora box, exports t4d5 via NFS. t4d5 is big, has lots of space, and the user tobiasf has plenty of quota: [root at theme4 ~]# quota -vls tobiasf|grep sdf /dev/sdf1 1312G 4578G 4769G

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, I've to create a dir (/usr/local/samba/server) for win users (group @test), and I've to simulate a dir quota (50-55Gb) on my freebsd system. These are my steps: 1. kernel with 'options QUOTA' 2. rc.conf with enable_quotas="YES" and check_quotas="YES" 3. fstab: /dev/da0s1f /usr

Hi All, We have a mixed environment running with Windows and Linux with samba as the domain controller.  Smart card login is configured and working properly with pkinit and certs, etc (https://wiki.samba.org/index.php/Samba_AD_Smart_Card_Login) though I don't think this is related. A handful of Windows clients are regularly getting their accounts locked during what seems to be a

Hey, I've been strugling to get quota working on my enviroment. I have one storage server that exports the 'home' dir. My mail server mounts the exported 'home' server at '/home' # dovecot --version > 1.1.14 I'm also running Postfix and using Dovecot/LDA as MDA so that we can use the Dovecot's Quota plugin. The thing is that if the user has exceeded

Hey all, I've got quotas enabled and turned on, it works fine for my first test user: $ quota -u user1 Disk quotas for user user1 (uid 2001): Filesystem usage quota limit grace files quota limit grace /var/mailboxes 2772 450000 500000 30 0 0 Then, I used the edquota to generate quotas for the next 1000 users: $ edquota -p user1 2002-3000

I'm not able to get the FS quota module to behave as I expect. Depsite having function fs quotas and dovecot apparently configured to use then, the quotas appear to be empty and/or not configured. Any clues? # quota kgc Disk quotas for user kgc (uid 500): Filesystem blocks quota limit grace files quota limit grace /dev/sda3 1229460 7000000 8000000

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

Hi All, I have a very strange problem that I'm unable to pinpoint at the moment. For some reason I am simply unable to get xfs_quotas to report correctly on a freshly installed, fully patched CentOS 6 box. I have specified all the same options as on another machine which *is* reporting quota LABEL=TEST /exports/TEST xfs inode64,nobarrier,delaylog,usrquota,grpquota 0 0 xfs_quota -xc

Hello, I set up NFSv4 server. To make sure I set vfs.nfsd.server_min_nfsvers=4. I can check its version, for example, by tcpduming and then I can see in wireshark lines like: Network File System Program Version: 4 V4 Procedure: COMPOUND.... .... is there any easier way to check its version? I see there is nfsstat -e option which shows delegs and locks. But all other ones are combined with nfsv3

Hey there, I'm pretty sure I've found a bug with doveadm when concatenating with another search key. While doveadm HEADER <field pattern> works fine when not using additional search keys, it doesn't work properly when concatenating with other serarch keys - it then simply seems to ignore the additional HEADER <field pattern> search key. It's reproduceable, also

Hello, I am mounting via NFS a number of volumes and re-sharing these as CIFS. We have been using this arrangement successfully for a number of years. We are replacing the "CIFS>NFS" proxy servers (which are also PDC/BDCs to OpenLDAP) and a weird problem seems to occur. The problem is the quota/disk size appears to be wrong. For example, if I use the unix quota command on the SMB