similar to: Bug#447153: /usr/bin/scp: Fails to notice write errors

Last friday we upgraded from 1.9.17p4 to version 1.9.18p3 on a HP-UX 9.04 machine. Now we get lots of entries in the log.smb file like: ERROR: del_share_mode: failed to ftruncate share mode file /programs/samba/var/locks/share.1073807365.8199 to size 42 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file /programs/samba/var/locks/share.1073807365.8195 to size 42

Thank you for the information that you have passed on to me. My own research has found that ftruncate is quite happy to set a file to the same size that it is already, so something else must be causing the problem. The comment before the ftruncate in set_share_mode says the file is being truncated just for safety, so normally it is probably not necessary to truncate the file. Regards, Tim >

Hi, I'm running Samba 3.0.23a on Linux. One of my share is a USB disk with a FAT32 filesystem. When copying large files from my Windows XP machine to this share, smbd seem to "reserve" (by using ftruncate()) the space needed on the USB disk before actually doing any copying. This ftruncate() operation takes quite a while when the file is large. It may even cause the client to time

Samba 1.9.17p1. The log file contains Ks of messages like this: ERROR: set_share_mode: failed to ftruncate share mode file /usr/adm/locks/share.119542272.430101 to size 64 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file /usr/adm/locks/share.119542272.430101 to size 64 (Permission denied) ERROR: set_share_mode: failed to ftruncate share mode file

I added debuging as follows: /* no O_EXCL, existence check is via the fcntl lock */ lockfile_fd = open(lockfile_name.buf, O_NONBLOCK|O_CREAT|O_WRONLY, 0644); if (lockfile_fd == -1) { ret = errno; DEBUG(1, ("%s: open failed: %s\n", __func__, strerror(errno))); return ret; }

Any suggestion.... On Dec 6, 2017 11:51, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com> wrote: > Hi Team, > > We are getting the crash in glusterd after start of it. When I tried to > debug in brick logs we are getting below errors: > > [2017-12-01 14:10:14.684122] E [MSGID: 100018] > [glusterfsd.c:1960:glusterfs_pidfile_update] 0-glusterfsd: pidfile >

Hi, Two patches to add ftruncate and vsyslog syscalls. These were in the klibc that Greg K-H has in the udev tarball. I got his permission to contribute them to the main-line klibc. mh -- Martin Hicks Wild Open Source Inc. mort@wildopensource.com 613-266-2296 -------------- next part -------------- A non-text attachment was scrubbed... Name: klibc-ftruncate.diff Type:

https://bugzilla.mindrot.org/show_bug.cgi?id=2176 Bug ID: 2176 Summary: unchecked returned value from ftruncate Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: sftp Assignee: unassigned-bugs at mindrot.org

Hi List, I had a need recently to efficiently synchronise between some large LUNs (boot drive disks) at two different datacentres. Solutions like drbd and $proprietary_array_vendors_software were overkill - we only needed (wanted!) to periodically synchronise these LUNs whenever major changes were generated on the source. On the other hand however, re-sending the entire disk contents each time

http://bugzilla.mindrot.org/show_bug.cgi?id=403 Summary: scp generates sparse file when no space left Product: Portable OpenSSH Version: 3.1p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

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 am trying to see if Samba 4.2.0rc4 will run on a Solaris 10 i386 system. After getting it to build, startup fails. Starting it up as smbd -i -d 10 The output indicates that everything is starting normally until the following is output: messaging_dgm_lockfile_create: ftruncate failed: Invalid argument messaging_dgm_init: messaging_dgm_create_lockfile failed: Invalid argument messaging_dgm_init

Without the glusterd log file and the core file or the backtrace I can't comment anything. On Wed, Dec 6, 2017 at 3:09 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Any suggestion.... > > On Dec 6, 2017 11:51, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com> wrote: > >> Hi Team, >> >> We are getting the crash in glusterd after

--- pxzcat.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pxzcat.c b/pxzcat.c index 4ab8689..9bcdc36 100644 --- a/pxzcat.c +++ b/pxzcat.c @@ -29,10 +29,11 @@ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. */ +#define _GNU_SOURCE #include <config.h>

http://bugzilla.mindrot.org/show_bug.cgi?id=1236 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|bitbucket at mindrot.org |djm at mindrot.org Attachment #1189 is|0

On Mon, Oct 23, 2017 at 3:40 PM, Brian Cain <brian.cain at gmail.com> wrote: > > > On Mon, Oct 23, 2017 at 5:21 PM, Rui Ueyama via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> If your system does not support fallocate(2), we use ftruncate(2) to >> create an output file. fallocate(2) succeeds even if your disk have less >> space than the

--- examples/create-disk.c | 20 +++++--------------- examples/mount-local.c | 22 +++++----------------- golang/examples/create-disk.go | 12 ++---------- ocaml/examples/create_disk.ml | 4 +--- perl/examples/create_disk.pl | 4 +--- python/examples/create_disk.py | 5 +---- ruby/examples/create_disk.rb | 4 +--- 7 files changed, 16 insertions(+), 55 deletions(-) diff

Hi Atin, Please find the backtrace and logs files attached here. Also, below are the BT from core. (gdb) bt #0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00003fff88350fd0 in __GI_abort () at abort.c:89 [**ALERT: The abort() might not be exactly invoked from the following function line. If the trail function

I hope these logs were sufficient... please let me know if you require more logs. On Wed, Dec 6, 2017 at 3:26 PM, ABHISHEK PALIWAL <abhishpaliwal at gmail.com> wrote: > Hi Atin, > > Please find the backtrace and logs files attached here. > > Also, below are the BT from core. > > (gdb) bt > > #0 0x00003fff8834b898 in __GI_raise (sig=<optimized out>) at >

If your system does not support fallocate(2), we use ftruncate(2) to create an output file. fallocate(2) succeeds even if your disk have less space than the requested size, because it creates a sparse file. If you mmap such sparse file, you'll receive a SIGBUS when the disk actually becomes full. So, lld can die suddenly with SIGBUS when your disk becomes full, and currently we are not doing