similar to: samba 3.3 - poor performance (compared to NFS)

I see via yum that there is "samba" and there is "samba3x" available for CentOS (my boxes are hooked to the main CentOS repo, Fedora EPEL, and RPMFORGE). 'samba' is 3.0.33 'samba3x' is 3.3.8 Is there any down-side to upgrading to 'samba3x' and running 3.3.8 instead of 3.0.33? I'm assuming that, in general, I should be running the latest

From the smb.conf manpage, it says that an 'include <file>' will include that file into smb.conf as if it were typed in place. Yet, I have a setup where: /etc/samba/smb.conf contains: [global] <various global parameters> include /etc/samba/smb.conf.local and then /etc/samba/smb.conf.local contains my share definitions. I'm doing it

I ran the same dd tests from KnowYourNFSAlpha-1.pdf and performance is inconsistent and causes the server to become unresponsive. My server freezes every time when I run the following command: dd if=/dev/zero of=garb bs=256k count=64000 I would also like to mount a path like: /volume/some/random/dir # mount host:/gluster/tmp /mnt/test mount: host:/gluster/tmp failed, reason given by server: No

Newbie question! We currently are running a product call TAS from Syntax Corporation and would like to move to Samba. I have review the documentation and cannot find how to set up muliple services on one server. I tried using the Netbios name = and the include statement to bring in another smb.conf file but I don't think I'm on the right track.

Hi all, 1) My NFS3 clients don't display or obey existing non-POSIX ACLs on files of NFS3-mounted exports. 2) setfacl on the client throws error and fails : # setfacl -m u:stowler:rw testfile.text setfacl: testfile.text: Operation not supported 3) at time of client mount the server's /var/log/messages shows "kernel: svc: unknown version (3)". Any thoughts greatly

Hello, Actually I have some troubels concerning samba (3.0.24) on debian (4.0): I would like to have some samba-shares on a nfs-filesystem. NFS works fine for the Linux clients and the Linux server. The nfs filesystem is mounted from an other server on /home. The next step is to set up samba to have some shares on the nfs Filesystem (/home/$LOGIN, anonymized configuration attached).

Hi, After running rm -rf on a directory, the files under it got deleted, but the directory was not deleted and was showing stale file handle error. After 18 minutes, I'm able to delete the directory. So could anyone help me in knowing what could have happened or when in general I get such errors. The following is NFS log: [2017-12-21 13:56:01.592256] I [MSGID: 108019]

Hi all, I haven't found any root cause or workaround for this yet. Can any one help me in underatanding the issue? Regards, Jeevan. On Dec 21, 2017 8:20 PM, "Jeevan Patnaik" <g1patnaik at gmail.com> wrote: > Hi, > > > After running rm -rf on a directory, the files under it got deleted, but > the directory was not deleted and was showing stale file handle

Hi All, I know this isn't the ganesha mailing list but wondered if anyone can help. I'm having issue with file creation over NFS, I have a gluster volume "vol1" presented via Ganesha with the following config:EXPORT{? ? ? ? Export_Id = 20;? ? ? ? Path = "/vol1";? ? ? ? FSAL {? ? ? ? ? ? ? ? name = GLUSTER;? ? ? ? ? ? ? ? hostname = "gnfs01";? ? ? ? ? ? ? ?

An ESTALE error usually means the gfid could not be found. Does repeating the "rm -rf" delete the directory? Regards, Nithya On 3 January 2018 at 12:16, Jeevan Patnaik <g1patnaik at gmail.com> wrote: > Hi all, > > I haven't found any root cause or workaround for this yet. Can any one > help me in underatanding the issue? > > Regards, > Jeevan. > >

Hi Rowland, >> Hi, >> >> I've a strange problem. I migrated my NT4 PDC to a ad on my debian >> stretch (samba version is 4.5.12). >> >> The Domain Controller has some shares for my users. >> >> One user just told me he can't access the share...before the >> migration he was able to access the share btw! So I checked the ACL's

Hi All, Well, it <http://goo.gl/hzxyw> was too good to be true. Under extreme, extended IO on a 48core node, some part of the the NFS stack collapses and leads to an IO lockup thru NFS. We've replicated it on 48core and 64 core nodes, but don't know yet whether it acts similarly on lower-core-count nodes. Tho I haven't had time to figure out exactly /how/ it collapses, I

I have an issue that is not all that unique, so I'm hoping someone has done it before. On the client end I have some very old RedHat based systems. On the server end is a Windows 2008 system running NFS server software. The clients mount the server resource as an NFS2 mount but some compliance issues were discovered with the setup. For various reasons, updating the client is not an option at

>>>>> "Mark" == Mark Moseley <moseleymark at gmail.com> writes: Mark> This is just me throwing things out to look at, but did the Mark> client mount on the old server use NFS3 and the new upgraded Mark> client uses NFS4? Sometimes that can cause weirdness with id Mark> mapping.? Another thing to check is selinux, is it enabled? It's one of those

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Those symbols only used within this file, and should be static. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/char/virtio_console.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c index 13ad9b1..f73ad64 100644 ---

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Those symbols only used within this file, and should be static. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/char/virtio_console.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c index 13ad9b1..f73ad64 100644 ---

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Fix to return -ENOENT in the pcistub_device_find() and pci_get_drvdata() error handling case instead of 0(overwrite to 0 by str_to_slot()), as done elsewhere in this function. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/xen/xen-pciback/pci_stub.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Fix to return -ENOENT in the pcistub_device_find() and pci_get_drvdata() error handling case instead of 0(overwrite to 0 by str_to_slot()), as done elsewhere in this function. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- drivers/xen/xen-pciback/pci_stub.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3

On 2023-04-01 15:13, Kees van Vloten via samba wrote: > > On 01-04-2023 20:38, Rowland Penny via samba wrote: >> >> >> On 01/04/2023 19:10, Gary Dale via samba wrote: >> >>> https://wiki.samba.org/index.php/Idmap_config_ad in the Configuring >>> the ad Back End section. >> >> Yes, but right at the top there is a warning box that says:

From: Wei Yongjun <yongjun_wei at trendmicro.com.cn> Using for_each_set_bit_from() to simplify the code. Signed-off-by: Wei Yongjun <yongjun_wei at trendmicro.com.cn> --- net/bridge/br_fdb.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/net/bridge/br_fdb.c b/net/bridge/br_fdb.c index b0812c9..48fe761 100644 --- a/net/bridge/br_fdb.c +++ b/net/bridge/br_fdb.c