SEO

#1 (**permalink**) 01-04-2008, 09:23 PM

Fellow AIX'ers;

We've been using Samba for about 10 years now and it has been a
mainstay at our stie.

Our current version was taken from the bull.freeware site and
installed with smit. That version is 2.2.1

For editing purposes we have a share mapped to the aix disk and we use
a windows based editor to maintain certain source files on the logical
drive. Works great.

However, here's something that we've seen recently that we have not
noticed before. But that doesn't mean it wasn't there.

BTW - our editor is EditPlus version 2.11

If we access a file on the logical drive with the editor then exit it
and subsequently that file on the logical drive is altered by an aix
process. If we re-access that same file again with the editor we
still see the OLD VERSION.

The only way we can get around it is to disconnect the share then
reconnect it. Then when we access that file with the editor we see
the correct content.

This appears to be a caching issue. Has anyone experienced this
symptom before? And if so, what might you have done to rectify it?

Thanks in advance.

B

#2 (**permalink**) 01-04-2008, 09:23 PM

Bob Mariotti wrote:
> Fellow AIX'ers;
>
> We've been using Samba for about 10 years now and it has been a
> mainstay at our stie.
>
> Our current version was taken from the bull.freeware site and
> installed with smit. That version is 2.2.1
>
> For editing purposes we have a share mapped to the aix disk and we use
> a windows based editor to maintain certain source files on the logical
> drive. Works great.
>
> However, here's something that we've seen recently that we have not
> noticed before. But that doesn't mean it wasn't there.
>
> BTW - our editor is EditPlus version 2.11
>
> If we access a file on the logical drive with the editor then exit it
> and subsequently that file on the logical drive is altered by an aix
> process. If we re-access that same file again with the editor we
> still see the OLD VERSION.
>
> The only way we can get around it is to disconnect the share then
> reconnect it. Then when we access that file with the editor we see
> the correct content.
>
> This appears to be a caching issue. Has anyone experienced this
> symptom before? And if so, what might you have done to rectify it?
>
> Thanks in advance.
>
> B

You need to disable Opportunistic Locking (lazy writes in MS-speak).
Look for "Unix and Oplocks" in the Samba documentation.

-- Jason

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Samba 2.2x cache on aix 5.1 question?