similar to: samba quotas

Hi I'm using SuSE-Linux 7.3, Kernel 2.4.18 with samba 2.2.3a and XFS with quotas The problem is the quotas won't be displayed in Samba. So I've tried to write my own dfree command and add it in smb.conf. dfree.sh: #!/bin/sh used_space=`/usr/bin/quota -u $1 | tail -1 | awk '{print $2}'` quota_space=`/usr/bin/quota -u $1 | tail -1 | awk '{print $4}'`

Hello there, I am working with dovecot v2.2.12, and have setup a user and domain quota by using a quota/quota_rule for user and quota2/quota2_rule for the domain. This works fine when the limit configuration for both is stored inside dovecot configuration files. However, I would like to have the limits configurable on a user and domain base, and that data is stored inside my SQL database.

v2 -> v3: - Drop gnulib fallback.

It started out as "this'll be just a simple fix ..." and turned into something a bit over-engineered in the end. Here it is anyway. Rich.

v1 -> v2: - Removed the f_type field from StatVFS.statvfs structure. - New function StatVFS.filesystem_is_remote, written in C. [Thinking about it, this should probably be called ?is_network_filesystem?, but I can change that before pushing]. - Use statvfs instead of fstatvfs, and statfs instead of fstatfs. - Rejigged the comments in builder/builder.ml to make them simpler

In order to reduce the number of credit update messages, we send them only when the space available seen by the transmitter is less than VIRTIO_VSOCK_MAX_PKT_BUF_SIZE. Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- include/linux/virtio_vsock.h | 1 + net/vmw_vsock/virtio_transport_common.c | 14 +++++++++++--- 2 files changed, 12 insertions(+), 3 deletions(-)

Since this new temporary directory will contain UNIX sockets for communicating with nbdkit, then its path must not be too long. Use the existing directory that libguestfs exposes for this, i.e. sockdir. --- v2v/nbdkit.ml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/v2v/nbdkit.ml b/v2v/nbdkit.ml index 65317f9b..46b20c9d 100644 --- a/v2v/nbdkit.ml +++ b/v2v/nbdkit.ml

v1 was here: https://www.redhat.com/archives/libguestfs/2020-April/msg00007.html There's a BZ for this now which I forgot to add to the commit message: https://bugzilla.redhat.com/show_bug.cgi?id=1814611 For v2: - Fix incorrect reference to $TMPDIR in existing manual. - Separate handling for small temporary files and large temporary files. Small temporary files go into $TMPDIR

The whole loop=0,1,2 thing was kind of odd and not very self explanatory. I''ve replaced it with a list_for_each_entry on space_info->block_groups. If we have a hint we just jump into the loop with the block group and start looking for space. If we don''t find anything we start at the beginning and start looking. We never come out of the loop with a ref on the block_group

On Wed, Jul 17, 2019 at 01:30:27PM +0200, Stefano Garzarella wrote: > In order to reduce the number of credit update messages, > we send them only when the space available seen by the > transmitter is less than VIRTIO_VSOCK_MAX_PKT_BUF_SIZE. > > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- > include/linux/virtio_vsock.h | 1 + >

On Wed, Jul 17, 2019 at 01:30:27PM +0200, Stefano Garzarella wrote: > In order to reduce the number of credit update messages, > we send them only when the space available seen by the > transmitter is less than VIRTIO_VSOCK_MAX_PKT_BUF_SIZE. > > Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> > --- > include/linux/virtio_vsock.h | 1 + >

I am migrating the main file servers at work onto a new storage platform based on GPFS. I am using RHEL 5.6 with the samba3x packages (aka 3.5.4) recompiled to get the vfs_gpfs and tsmsm modules, with a couple of extra patches to vfs_gpfs module to bring it 3.5.8 level. It is running with ctdb against Windows AD 2008 R2 domain controllers with all the idmapping been held in the AD. In order to

I was planning to use this function to harden the code in v2v/input_ova.ml against malicious OVA files. However I didn't complete that work. Hate to see a good commit go to waste ... Rich.

The first patch is just some simple refactoring. See the second patch for a description of the new virt-sparsify --tmp option. I tested this using a loopback device as my temporary block device, and it seems to work fine for me. Federico .. this needs a BZ :-) Rich.

Hi All, This is my first post to centos-docs. I've read several months of archives, but, this may be too trivial. Re: http://wiki.centos.org/TipsAndTricks/EncryptedFilesystem/Scripts This line: FREE_SPACE=$(df -m $SECRET_PATH |grep / | awk '{ print $4 }') gave me a problem due to line wrapping in df. For example: $ df -m /home/ja/verify/ Filesystem 1M-blocks Used

On 18/05/2019 14:19, Hendrik Friedel wrote: > Hello > >> No, probably a lack of users using your combination of Samba, btrfs >> and quotas. > I would have thought that btrfs is becoming more mainstream now. And > then, Samba and Quotas should be rather common... >> Is btrfs becoming more common ? > >> Of course, more info may help, what is in your smb.conf

I noticed a huge problem with the free space cache that was presenting as an early ENOSPC. Turns out when writing the free space cache out I forgot to take into account pinned extents and more importantly clusters. This would result in us leaking free space everytime we unmounted the filesystem and remounted it. I fix this by making sure to check and see if the current block group has a cluster

Fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1354507 Main explanation is in patch #3. Rich.

HFvs> Hello, >>> In my impression: Yes. Also, this problem seems to affect also zfs HFvs> and >> I'm mostly interested in the claim that ZFS is affected. >> I haven't followed this thread carefully, but what exactly is the problem we're >> talking about, and how do we know it impacts ZFS? >> [Something more than a single one-liner in that

Dear all, I've successfully setup a Samba 2.2.3a file server with quota support on a RedHat Linux 7.1 with Kernel 2.4.18-ac2. Win NT clients (NT, 2K, XP) works fine, and samba report the quota per user as disk capacity. But Win98/ME clients don't. Samba report the filesystem capacity, and even worse, users can bypass their quotas ! I solved the problem using a dfree script written in