similar to: DFree and sub-Share "disk" (volume?)

Displaying 20 results from an estimated 2000 matches similar to: "DFree and sub-Share "disk" (volume?)"

2019 Feb 25
0
DFree and sub-Share "disk" (volume?)
On 2019-02-20 at 22:11 -0800 James Wright via samba sent off: > I read over the documentation for both the 'dfree' and 'get quota command' > options, but it seems that the paths those pass as their first parameter > are useless to me, as they mostly seem to be the share's root (represented > as '.'), not the actual path being queried. you might have a look
2019 Feb 14
2
Automaticaly unlock files
Hi all, I've been looking for an answer for this issue but Google didn't help. So I resource to the next best thing: the Samba mailing list. Question: Is there a way to automaticaly, after a certain amount of time, unlock a file after, for example, a client crash or network problem? I know how to do it manually of course, but that is, well, cumbersome. I've looked at
2019 Feb 14
1
Automaticaly unlock files
Ah, a workaround! I'd seen something like this on an old thread but I've always tried to stay away from socket options. I'll give these a try. Thanks for your help P.S.: strange that I don't see more people "complaining" about this.... Best regards, Carlos Volker Lendecke <Volker.Lendecke at sernet.de> escreveu no dia quinta, 14/02/2019 à(s) 05:38: > On Thu,
2019 Mar 02
1
Samba 4 File Locking
I have an old application that would kick up a warning "File is open - do you want to open in read only mode" on my previous Samba3 NT style domain set up. It's also accessing the file share thru a connection coming thru an VM setup. On my Samba 4 AD setup, I'm not getting the initial read only message. file locking seems to be different. It seems like two concurrent users can
2019 Feb 23
2
winbind causing huge timeouts/delays since 4.8
> Am 23.02.2019 um 22:23 schrieb Rowland Penny via samba <samba at lists.samba.org>: >>>>> He also has these: >>>>> >>>>> idmap config * : rangesize = 1000000 >>>>> idmap config * : range = 1000000-19999999 >>>>> idmap config * : backend = autorid >>>>> >>>>> The '*' domain
2002 Jun 14
2
Help: dfree command
Hi folks, I'm trying to use a custom dfree command to have my Samba share reports accurate disk usage, here my dfree script (I pretty much copied it right off the smb.conf man page) #!/bin/sh /bin/df -k $1 | tail -1 | awk '{print $2" "$4}' In smb.conf, I included this line: dfree command = /usr/local/admin/samba-2.2.4/bin/dfree This dfree command is root owned,
2018 May 02
2
dfree command...
On Wed, May 02, 2018 at 10:00:02PM +0200, Robert S. Irrgang via samba wrote: > Nobody any idea? Use debug level 10 and log statements in your script to ensure it's being invoked and returning values. Without knowing details this is impossible to debug. > Am 30.04.2018 um 19:40 schrieb Robert S. Irrgang via samba: > > Hello, > > > > I've a little problem with
2002 Apr 17
1
dfree command
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}'`
2016 Jun 07
1
dfree is broken on this system
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] ../source3/smbd/dfree.c:139(sys_disk_free) WARNING: dfree is broken on this system What could be the cause of this? Tom Schulz Applied Dynamics Intl. schulz at
2019 Apr 29
2
dfree command in homes section
Hi everyone, we are using custom dfree commands to implement quotas. While these work fine on normal shares, the "dfree command" parameter seems to be ignored in the homes section. Is this correct (and intended)? Best regards Felix IT-Services Telefon 02461 61-9243 E-Mail: f.stolte at fz-juelich.de -------------------------------------------------------------------------------------
2018 May 04
1
dfree command...
On Fri, May 04, 2018 at 05:10:47AM +0200, Robert S. Irrgang via samba wrote: > I've put it in debug mode level 10. > The only place where dfree was displayed in the log is this. > > [2018/05/04 04:53:53.397520, 3, pid=13784, effective(0, 0), real(0, 0)] > ../source3/param/loadparm.c:2668(lp_do_section) > Processing section "[global]" > ... > doing
2019 May 06
1
dfree command cannot report correct disk space
Hi, my  filesystems is mounted like the below df output, /share is exported in samba. Filesystem                     Size  Used Avail Use% Mounted on /dev/sda1                       50G  9.1G   41G  19% /share nfs1:/                          492T  433T   59T  89% /share/group1 If a 100G file is copied to /share/group1, samba will report the storage doesn't have enough space. I tried to
2008 Oct 09
1
dfree causing write access problems
Hi I'm having problems with the dfree option on a Solaris 10 fileserver. Specifically: I had 3.0.X on the fileserver and the dfree option worked fine. I upgraded to 3.2.2 and now if dfree is enabled the clients get 1MB reported as the size of the share and when a client tries to right to the system they get told that the filesystem is full. The script output has been tested throughly
2017 Jan 26
1
About dfree command directive
Hello everyone, i need known if samba (4.5.2-Debian) disable the "dfree command" directive, because i create a script that simple write "hello" to a file and when i connect to my share, tell the free space, but the script never execute. The main need is that i used btrfs subvolumes with quotas for some shares and in batch i wrote a script that "echoes" the free
2018 Apr 30
2
dfree command...
Hello, I've a little problem with samba 4.5.x on debian stretch. I've shared a folder with a mounted partition and a sub-mounted partition. mount /dev/sdb1 /opt/smb mount /dev/sdc1 /opt/smb/subfolder But on windows only the free size of /dev/sdb1 is reported. So I try to use the "dfree command" directive to give back the full free size of all sub-mounted devices. But it seems
2012 Nov 28
1
Custom, per share (or user) dfree command?
Hi list, I am Mikael and I am new to this list. In our data center I need to give some users low end "backup storage" to Windows servers. For this I thought Samba shares could be a very easy and nice solution. I am able to limit the user's disk usage with file system quota, but unfortunately the disk space and usage reported to the Windows machines are the total amount of storage
2019 Feb 25
2
winbind causing huge timeouts/delays since 4.8
On 25.02.2019 10:20, Rowland Penny via samba wrote: > On Mon, 25 Feb 2019 09:24:24 +0100 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > >>>> I'm confused.. how is the choice of the idmap backend related to an >>>> AD DC use case? >>> Only in the case of wanting the same ID everywhere. >> In my understanding, the
2008 Oct 15
2
XFS tree quota and samba free space report
greetings, does anyone know, if it is possible to propagate somehow the XFS "directory tree quota" status to SMB workstation client free space report? currently the client sees total free space of share's partition (instead of tree quota free space). when the tree quota limit is reached, the write attempts fail, but free space report shows enough space, so this is confusing. I
2019 Jul 09
1
CTDB Samba 4.10 example?
Hi there, I use Samba 4.9 since its releaseday and also had some troubles first due to the lack of informations in the wiki. Anyways... after some try & error i got it working and since i run the Cluster (non-production environment) had no errors except CTDBs monitoring of the Samba process did'nt work as i would expect it (RPC-Server was dead but CTDB did'nt complain and "ctdb
2016 Jun 08
0
dfree is broken on this system
> 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]