similar to: Samba 2.0.5a & Solaris 2.6 Assistance

agibson@nova.org wrote: > > I just brought up samba 2.0.5a in a Solaris 2.6 environment. Smooth > effort with no visible problems in CVS download, configuration, and > make but attempts to reference data after connection yield this > error. Has anyone seen this before and can point me in the right > direction to to address? Thanks Andy > > [1999/07/31 15:14:30, 1]

SAMBA 2.2.8A I am automounting a 6-in-1 smartmedia reader such as: /etc/auto..master /mnt/auto /etc/auto.misc --timeout=1 /etc/auto.misc carda -fstype=msdos,rw,nosuid,nodev,umask=000 :/dev/sda1 I am also making that a samba share: [card_a] comment = Removable Card Media path = /mnt/auto/carda browseable = yes public = no read only = no

Hello, i have the problem that samba writes in the wrong files This is the original log.smbd and there you can find something from Mozilla 1.4 inside: 2003/09/01 14:42:39, 1] smbd/service.c:close_cnum(677) wadjet (192.168.17.50) closed connection to service WLW // <!-- <mdb:mork:z v="1.4"/> --> < <(a=c)> // (f=iso-8859-1)

Hi, i have a problem with access xp (2002) database files after moving the files to the linux files server. really often (6 times today) the database file is corrupt. i am running samba 2.2.5 on linux mandrake 8.2 with kernel 2.4.18. i have read that this has something to do with the file locking, but don't know what to do right now. i've set the parameter "veto oplock files =

Hello, i have this problem again. I have samba logs, from log.smbd, inside my Wordperfect-Document: [2003/09/09 16:42:33, 2] smbd/close.c:close_normal_file(229) markus closed file SftemBASIC/Testprogramme/2.9_Structure.b~RFf12cf7.TMP (numopen=4) [2003/09/09 16:42:33, 2] smbd/open.c:open_file(246) markus opened file SftemBASIC/test/m3/M3/workbench/EMBWorkBench.exe read=Yes write=No

I can?t copy some files from server to directory /adawork/softtek om AIX box I?m using AIX 5.3 with samba 2.2.7-4 Here?s mys logs from samba server _________________________________________ file log.windows-server seek_file: (FAT_ATRASO_TRANS_5_3_1_in.txt) sys_lseek failed. Error was Invalid argument [2009/08/27 13:30:59, 3] smbd/error.c:error_packet(94) error string = Invalid argument

System specs: Fedora Core 4 2.6.13-1.1532_FC4smp ATI Radeon 9200 SE P4 2.4Ghz (hyperthreading) xorg 6.8.2 Aureal Semiconductor Vortex 2 sound card Intel 82801EB chipset wine-20050524 FC3 rpm works just fine on my FC4 system. But any versions after that lockup my system when running wine. For the 200506 - 200510 versions of wine I have compiled them from scratch so I assumed it was something

I have a level 10 debug of the smbd/oplock process_local_message problem but can still not figure out what causes the unknown UDP message command code. I checked the source but could only see that this is an invalid opcode command. Anyone a clue what is happening here ? Might wrong opcode commands crash samba ? Peter [2003/09/04 11:50:12, 3] smbd/process.c:switch_message(685) switch

----- Forwarded message from Brooklyn Linux Solutions CEO ----- >From ruben@www2.mrbrklyn.com Thu Mar 15 23:17:00 2001 From: Brooklyn Linux Solutions CEO <ruben@www2.mrbrklyn.com> Message-Id: <200103160417.f2G4H0O09806@www2.mrbrklyn.com> Subject: Some Users Work - Some don't In-Reply-To: <200103160226.f2G2Q1i09494@www2.mrbrklyn.com> from Brooklyn Linux Solutions CEO at

Hi, We have a simple "Remote Procedure Call" mechanism that we are using to communicate between Windows computers and our Unix Samba server. The Windows application is proprietary software (Progress - not ours) and we have to work within the constraints of it. We have a Unix named pipe sitting in a Samba shared directory. We have a small C program that runs as a Unix daemon,

Hi, we have a strange samba locking problem with version 3.0. Sometimes user only get a read only access to files. This happens with different users on different clients. Unix permissions are OK. I have realy no idea. Can you help ? Thanx Peter Huber -------------- next part -------------- [2004/03/02 15:03:56, 5] smbd/uid.c:change_to_root_user(217) change_to_root_user: now uid=(0,0)

From: Sergey Senozhatsky <sergey.senozhatsky at gmail.com> The patch partially reverts some of the UAPI bits of the buffer cache management hints. Namely, the queue consistency (memory coherency) user-space hint because, as it turned out, the kernel implementation of this feature was misusing DMA_ATTR_NON_CONSISTENT. The patch revers both kernel and user space parts: removes the DMA

We've just been hit rather badly by a very nasty bug that can cause rsync to silently discard files or fill them with zeroes. It happens when e.g. opendir() succeeds but readdir() returns an error; rsync does not check for an error from readdir() and so simply ignores the error (along with any remaining files in the directory). No error is reported to the user, who will then happily

Dear all, First of all, Merry Christmas! :) While testing a File I/O sample program, I've encountered a link failure due to missing implementation of "\01__isoc99_fscanf" function. I think this function should be named "__isoc99_fscanf" instead. Please see the program code and LLVM IR generated by DragonEgg and clang below. It shows that clang generates

----- Forwarded message from Jeremy Allison <jra@samba.org> ----- From: Jeremy Allison <jra@samba.org> To: samba-technical@samba.org Cc: jra@samba.org Subject: Patch to improve Samba write speeds on Linux ext3 with 3.2.x Reply-To: Jeremy Allison <jra@samba.org> Hi all, Intel recently did some research on Samba write speeds, tested in Linux using ext3 resulting in the following

Hi Kalever! First of all, I really appreciate your test results for block-store(https://github.com/pkalever/iozone_results_gluster/tree/master/block-store) :-) My teammate and I tested block-store(glfs backstore with tcmu-runner) but we have met a problem of performance. We tested some cases with one server that has RDMA volume and one client that is connected to same RDMA network. two

In some filesystems, typically optimized for large I/O throughputs (like IBM GPFS, IBM SAN FS, or distributed filesystems in general) a lot of lseek() operations can strongly impact on performances. In this cases it can be helpful to enlarge the block size used to handle sparse files directly from a command line parameter. For example, using a sparse write size of 32KB, I've been able to

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large

Hi, Michael I have met ext4 error when using vhost_scsi on arm64 platform, and suspect it is vhost_scsi issue. Ext4 error when testing virtio_scsi & vhost_scsi No issue: 1. virtio_scsi, ext4 2. vhost_scsi & virtio_scsi, ext2 3. Instead of vhost, also tried loopback and no problem. Using loopback, host can use the new block device, while vhost is used by guest (qemu).

Hi, Michael I have met ext4 error when using vhost_scsi on arm64 platform, and suspect it is vhost_scsi issue. Ext4 error when testing virtio_scsi & vhost_scsi No issue: 1. virtio_scsi, ext4 2. vhost_scsi & virtio_scsi, ext2 3. Instead of vhost, also tried loopback and no problem. Using loopback, host can use the new block device, while vhost is used by guest (qemu).