From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Jon Bramley <brammers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Problems with CVS on CIFS since kernel 2.6.30
Date: Mon, 02 Aug 2010 22:10:20 +0530 [thread overview]
Message-ID: <4C56F4F4.5010903@suse.de> (raw)
In-Reply-To: <AANLkTikqgFHX=9quJmJyQvkX-3ZreLGoF0k5YKCFq+WW-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 08/02/2010 09:26 PM, Jon Bramley wrote:
> On 2 August 2010 16:33, Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
>> If upgrading is not feasible, could you try patching Samba server with
>> this patch (relatively very less risk):
>> � �http://www.mail-archive.com/samba-cvs-w/Ol4EcudpnDHl7Qnj/AWg@public.gmane.org.org/msg55843.html
>>
>> I think that should help resolving the bug with posix opens against
>> older server.
>>
>>>>> strange thing, is that some of my colleagues run Ubuntu 10.04, which
>>>>> uses the 2.6.32 kernel, and they can use the share without problem.
>>>
>>>> What is the server version in this case?
>>>
>>> Exactly the same server that I'm connecting to (3.0.28a).
>>
>> Strange.. Any idea whether the Ubuntu kernel is the released 2.6.32
>> kernel or any -rc version of 2.6.32?
>
> Just checked on a colleagues machine, and uname -r reports 2.6.32-24-generic
>
> Also checked the dmesg on the Ubuntu 10.04 box:
>
> The exact same errors that I get appear, which leads me to believe
> that this in itself is not the cause of my issue.
>
> Any other ideas to debug further?
>
Perhaps, try enabling debugging as mentioned in the url below before you
do the operation (for both the clients) and post
http://wiki.samba.org/index.php/LinuxCIFS_troubleshooting
But, I still think the real problem is the server-side one and perhaps
the Ubuntu client has just got lucky in this case..
Thanks,
--
Suresh Jayaraman
next prev parent reply other threads:[~2010-08-02 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 13:58 Problems with CVS on CIFS since kernel 2.6.30 Jon Bramley
[not found] ` <AANLkTingdjU-KKW3=KboAnR0pNeiE7aEje0nXhM6bYbe-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-02 14:53 ` Suresh Jayaraman
[not found] ` <4C56DBDD.4070501-l3A5Bk7waGM@public.gmane.org>
2010-08-02 15:08 ` Jon Bramley
[not found] ` <AANLkTin9uwwDaw+nvAiDKnPxPbbBXycVS3rLvhCaoJxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-02 15:33 ` Suresh Jayaraman
[not found] ` <4C56E564.3020508-l3A5Bk7waGM@public.gmane.org>
2010-08-02 15:56 ` Jon Bramley
[not found] ` <AANLkTikqgFHX=9quJmJyQvkX-3ZreLGoF0k5YKCFq+WW-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-02 16:40 ` Suresh Jayaraman [this message]
2010-08-02 17:14 ` Jeff Layton
[not found] ` <20100802131440.5b16a86b-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-08-03 12:24 ` Jon Bramley
[not found] ` <AANLkTim=gnAh4G_JeRCEcCkfXb5pQwTTKh6+-7yAyyHu@mail.gmail.com>
[not found] ` <AANLkTim=gnAh4G_JeRCEcCkfXb5pQwTTKh6+-7yAyyHu-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-03 12:35 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C56F4F4.5010903@suse.de \
--to=sjayaraman-l3a5bk7wagm@public.gmane.org \
--cc=brammers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox