The Samba copy file call flow
jinronggong at hotmail.com
Tue May 6 23:40:00 MDT 2014
Thanks Richard, I need tell other process that the file write operation is finished, if the close operation is delayed, the other process must hold the file context for the delayed time, but anyway, I found another solution to avoid this issue, thanks again for you nice help^^
From: samba-technical-bounces at lists.samba.org [mailto:samba-technical-bounces at lists.samba.org] On Behalf Of Richard Sharpe
Sent: Monday, May 05, 2014 9:55 PM
Subject: Re: The Samba copy file call flow
On Mon, May 5, 2014 at 4:02 AM, GongJinrong <jinronggong at hotmail.com> wrote:
> Hi, Richard
> Thanks for your advice, and I will update it to a new version, with
> your excellent paper "Writing a Samba VFS", I wrote a VFS module, but
> when I debug the samba code, I found a strange thing, the close
> operation always is delayed about 15 seconds when I do a file copy, can the close operation be called just after writing all data immediately?
This is most likely because the redirector on your client was given a batch oplock and hangs on to the open file handle for those 15 seconds.
If you do not want this happening you have to stop handing out oplocks. However, that will impact performance.
Is there any reason you need to see the close immediately after the last write?
> -----Original Message-----
> From: samba-technical-bounces at lists.samba.org
> [mailto:samba-technical-bounces at lists.samba.org] On Behalf Of Richard
> Sent: Monday, May 05, 2014 3:47 AM
> To: GongJinrong
> Cc: samba-technical
> Subject: Re: The Samba copy file call flow
> On Sun, May 4, 2014 at 1:50 AM, GongJinrong <jinronggong at hotmail.com> wrote:
>> Thanks Brad, my installed samba is really old, I installed it by yum
>> in CentOS 6.3, and now the yum version is updated to 3.6.9, I will
>> update it, thanks a lots for your advice^^.
> Even 3.6.9 is really old, and you should try to use something more recent. The SerNet folks were making source and binary RPMs available for more recent version of 3.6, so you should probably go with those if you want to stick with a 3.6.x version, and installing their RPMs is not so hard.
> I notice that the latest there is from March in 2014 which is quite recent:
> However, for Samba 4 you will need to register with them, as it says
> here: http://ftp.sernet.de/pub/samba/4.0/README.txt
> Building an RPM from their source RPM is also not that hard, especially as it seems you want to make some mods.
>> -----Original Message-----
>> From: samba-technical-bounces at lists.samba.org
>> [mailto:samba-technical-bounces at lists.samba.org] On Behalf Of Brad
>> Sent: Sunday, May 04, 2014 2:30 PM
>> To: samba-technical at lists.samba.org
>> Subject: Re: The Samba copy file call flow
>> On Sun, 4 May 2014 02:15:21 PM GongJinrong wrote:
>>> my samba version is 3.5.10,
>> This is almost three years old. Perhaps you could choose a newer
>> version - I'd recommend the latest 4.1 release, but even 3.6.23 (if
>> you really do not want to go to Samba 4) would be better - there are
>> quite a few security fixes since
>> 3.5.10 (see https://www.samba.org/samba/history/samba-3.6.23.html for
>> the release).
>> I don't know the details of the VFS question you are asking though.
> Richard Sharpe
More information about the samba-technical