similar to: locks directory over nfs

I cannot mount my Samba shares. I could, then I rebooted my device, and now I no longer can. The .conf file has not been changed in over a year. Here is the output of the log file: -bash-2.05b$ cat log.192.168.1.147 [2011/08/23 00:41:10, 0] lib/util_tdb.c:tdb_log(662) tdb(/opt/local/var/locks/sessionid.tdb): expand_file to 20480 failed (No space left on device) [2011/08/23 00:41:10, 1]

Hi, I'm hunting a bug in 3.0.x (tested on 3.0.10 and 3.0.20). Users can create and modfy files, but cannot delete them. The logs show [2005/09/21 20:48:14, 0, pid=18388, effective(4019, 412), real(4019, 0)] tdb/tdbutil.c:tdb_log(767) tdb(/srv/physik.fu-berlin.de/data/.samba/cluster1-test/cache/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) [2005/09/21 20:48:15, 0,

I'm running 2.11, and I've noticed a number of log entries that look like so: angie.log: tdb(/usr/local/samba/var/locks/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) [2004/10/03 15:14:36, 0] tdb/tdbutil.c:tdb_log(531) tdb(/usr/local/samba/var/locks/brlock.tdb): expand_file ftruncate to 8192 failed (Permission denied) The files in question look like this:

I'm running 2.11, and I've noticed a number of log entries that look like so: angie.log: tdb(/usr/local/samba/var/locks/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) [2004/10/03 15:14:36, 0] tdb/tdbutil.c:tdb_log(531) tdb(/usr/local/samba/var/locks/brlock.tdb): expand_file ftruncate to 8192 failed (Permission denied) The files in question look like this:

Hello, In regards to this thread: http://lists.samba.org/archive/samba/2005-September/111158.html I might be seeing a similar compatibility with this call is on Virtuozzo based system. > cat /etc/redhat-release Red Hat Linux release 9 (Shrike) > uname -a Linux hostname 2.6.8-022stab078.9-enterprise #1 SMP Thu Jun 8 12:38:51 MSD 2006 i686 athlon i386 GNU/Linux > mount /dev/vzfs on /

A couple of days ago, we noticed the following message appearing in syslog: Aug 14 15:09:35 zadok smbd[16067]: tdb(/var/lock/samba/locking.tdb): expand_file write of 8192 bytes failed (No space left on device) Similar messages would show up for several of the files under /var/lock/samba. Running df showed that /run/lock was full. Not having ever paid any attention to /run/lock before, I

Hi all,. I'm getting this:- [2002/03/08 10:26:28, 8] lib/util.c:(1274) fcntl_lock 6 34 0 1 2 [2002/03/08 10:26:28, 8] lib/util.c:(1314) fcntl_lock: Lock call successful [2002/03/08 10:26:28, 5] tdb/tdbutil.c:(475) tdb((NULL)): tdb_brlock failed (fd=7) at offset 4 rw_type=2 lck_type=6 [2002/03/08 10:26:28, 5] smbd/connection.c:(156) claiming 0 [2002/03/08 10:26:28, 0]

Hi, When I try to execute the following: smbclient -U% -L localhost I receive the following error: tdb(/usr/local/samba/var/locks/gencache.tdb): expand_file write of 1024 failed (Invalid argument) [2003/10/26 19:45:58, 0] lib/util_sock.c:read_socket_with_timeout(279) read_socket_with_timeout: timeout read. read error = Broken pipe. protocol negotiation failed Any ideas anyone? I have

Hello, I am using Red-hat Linux Application Server 3.0. I have installed and successfully configured samba server & thus able to connect from windows m/c....It works perfectly fine. But when I install our product( Its a java application and one kernel loadable module) on the same machine The samba server does not restart. Following are the messages in /var/log/samba/smbd.log. after

I've run into a problem with samba and tdb reporting "too many connections" If I do a typical configure: ./configure --prefix=/usr/local/samba \ --localstatedir=/var/samba \ --with-lockdir=/var/samba/locks \ --with-configdir=/usr/local/samba/etc I see errors like the following in /var/samba/log.smbd: [2001/11/10 22:58:53, 0] tdb/tdbutil.c:tdb_log(342)

Hi, I have compiled then installed Samba 3.6.22 on my AIX 5.2. When I start SMBD it systematicaly corrupts the filesystem on which it is installed and fails to start I start SMBD on an other port because an old samba (2.2.8) is already running and I have to validate 3.6.22 before shuting down the old one. You'll see more informations bellow : - smbd output - IBM errpt corruption report

Hi, I'm experiencing a serious problem when trying to replace libvorbis with tremor (from svn): premitting that I don't want to use the ov_* functions, calling vorbis_synthesis_headerin() on the 3 initial packets works with libvorbis but immediately fails with tremor. At first sight it seems that the function in tremor either receives a leading \n before every header (that

Howdy, Are access control lists (ACL, i.e. setfacl / getfacl) supported in GlusterFS 3.1? If yes, beyond mounting the bricks with "defaults,acl" what do I need to do to enable ACL for both NFS and native Gluster clients? Google isn't returning anything useful on this topic. Thanks, Mike ================================= Mike Hanby mhanby at uab.edu UAB School of Engineering

Hi all. I''m now try to read and write puseud physical memory of domU from Dom0 with xenaccess(this is using libxc). #http://xenaccess.sourceforge.net/ With xenaccess, I''m succeeded read and writing almost of the memory. But It fail when I try to access head 1M region and some bit regions. To be precise, xc_map_foreign_range() of libxc returns error code. **

Since commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered connectors harder") We've been failing atomic checks if they try to enable new displays on unregistered connectors. This is fine except for the one situation that breaks atomic assumptions: suspend/resume. If a connector is unregistered before we attempt to restore the atomic state, something we end up

Since commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered connectors harder") We've been failing atomic checks if they try to enable new displays on unregistered connectors. This is fine except for the one situation that breaks atomic assumptions: suspend/resume. If a connector is unregistered before we attempt to restore the atomic state, something we end up

Important! below On Fri, 2019-02-01 at 18:57 +0100, Daniel Vetter wrote: > On Thu, Jan 31, 2019 at 08:14:50PM -0500, Lyude Paul wrote: > > Since > > > > commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered > > connectors harder") > > > > We've been failing atomic checks if they try to enable new displays on > >

Howdy, With 3.1.3 the option was added to disable the builtin Gluster NFS. Does that mean that the following scenario should work: 1. Disable Gluster NFS "gluster volume set <VOLUME> nfs.disable on" 2. Restart the gluster servers for good measure 3. On one of the gluster servers, mount the volume using the gluster fuse client: mkdir /export/users # In /etc/fstab add

On Thu, Jan 31, 2019 at 08:14:50PM -0500, Lyude Paul wrote: > Since > > commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered > connectors harder") > > We've been failing atomic checks if they try to enable new displays on > unregistered connectors. This is fine except for the one situation that > breaks atomic assumptions: suspend/resume.

Howdy, I have a GlusterFS 3.1 volume being mounted on a client using NFS. From the client I created a directory under the mount point and set the permissions to root:groupa 750 My user account is a member of groupa on the client, yet I am unable to list the contents of the directory: $ ls -l /gfs/dir1 ls: /gfs/dir1/: Permission denied $ ls -ld /gfs/dir1 rwxr-x--- 9 root groupa 73728 Nov 9