Problems with CVS on CIFS since kernel 2.6.30

Problems with CVS on CIFS since kernel 2.6.30

[Jon Bramley]

Hi all,
I'm experiencing a problem with the linux CIFS client which is
preventing me from using any kernel past 2.6.29, I've been banging my
head against this one for some months now, so thought it about time to
ask some experts. I'm running Gentoo linux on a 32 bit machine.

When connecting to our cifs share on any kernel I've tried since
2.6.29 (30, 31, 32, 33 and 34) I cannot use CVS on the share, as I get
the following error:

515 14:41 $ cvs update
cvs [update aborted]: cannot get working directory: No such file or directory

Here is the bottom part of an strace of the above command:
http://paste.org/pastebin/view/21095

dmesg always seems to report the following, upon mount, on all kernels
past 2.6.29, which I'm guessing is related:

 CIFS VFS: server 10.194.0.106 of type Samba 3.0.28a returned
unexpected error on SMB posix open, disabling posix open support.
Check if server update available.
 CIFS VFS: Autodisabling the use of server inode numbers on
\\shared.orbis\shared. This server doesn't seem to support them
properly. Hardlinks will not be recognized on this mount. Consider
mounting with the "noserverino" option to silence this message.

I've tried mounting the share using the noserverino option, which
indeed does get rid of the second of those lines in dmesg, but doesn't
fix the problem. Updating the server is not really an option (unless I
can prove very good reason) since this is my work server. One slightly
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.

I thought my problem could be related to the one described here:
https://bugzilla.kernel.org/show_bug.cgi?id=15088 but I think this was
fixed in 2.6.34, and that kernel is still not working for me (nor does
it with noserverino).

Are there any steps I could take to debug this issue further, or does
anyone know what the problem might be?

Thanks in advance,

Jon

Re: Problems with CVS on CIFS since kernel 2.6.30

[Suresh Jayaraman]

On 08/02/2010 07:28 PM, Jon Bramley wrote:
> Hi all,
> I'm experiencing a problem with the linux CIFS client which is
> preventing me from using any kernel past 2.6.29, I've been�banging�my
> head against this one for some months now, so thought it about time to
> ask some experts. I'm running Gentoo linux on a 32 bit machine.
> 
> When connecting to our cifs share on any kernel I've tried since
> 2.6.29 (30, 31, 32, 33 and 34) I cannot use CVS on the share, as I get
> the following error:
> 
> 515 14:41 $ cvs update
> cvs [update aborted]: cannot get working directory: No such file or directory
> 
> Here is the bottom part of�an strace of the above command:
> http://paste.org/pastebin/view/21095
> 
> dmesg always seems to report the following, upon mount, on all kernels
> past 2.6.29, which I'm guessing is related:
> 
> �CIFS VFS: server 10.194.0.106 of type Samba 3.0.28a returned
> unexpected error on SMB posix open, disabling posix open support.
> Check if server update available.
> �CIFS VFS: Autodisabling the use of server inode numbers on
> \\shared.orbis\shared. This server doesn't seem to support them
> properly. Hardlinks will not be recognized on this mount. Consider
> mounting with the "noserverino" option to silence this message.
> 
> I've tried mounting the share using the noserverino option, which

See options serverino, noserverino and section inode numbers in 'man
mount.cifs' for additional information regarding this error.

Is there a hardlink involved?

> indeed does get rid of the second of those lines in dmesg, but doesn't
> fix the problem. Updating the server is not really an option (unless I
> can prove very good reason) since this is my work server. One slightly

The samba version you are using seem to be quite old.. Does better POSIX
support/conformance sound like a good enough reason..?

> 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?


Thanks,

-- 
Suresh Jayaraman

Re: Problems with CVS on CIFS since kernel 2.6.30

[Jon Bramley]

Hi Suresh,

Firstly, thanks for responding.

> See options serverino, noserverino and section inode numbers in 'man
> mount.cifs' for additional information regarding this error.

I've read the man pages and understand that noserverino will break
hardlinks, but it doesn't work with or without this option.

> Is there a hardlink involved?

No.

> The samba version you are using seem to be quite old.. Does better POSIX
> support/conformance sound like a good enough reason..?

I doubt it. The problem I have is that it is working fine for Ubuntu
users (which is the vast majority) so they will not want to risk
breaking things. Of course that means I cannot currently update my
kernel (which they are less concerned about).

>> 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).

Thanks,

Jon

Re: Problems with CVS on CIFS since kernel 2.6.30

[Suresh Jayaraman]

On 08/02/2010 08:38 PM, Jon Bramley wrote:
> 
>> The samba version you are using seem to be quite old.. Does better POSIX
>> support/conformance sound like a good enough reason..?
> 
> I doubt it. The problem I have is that it is working fine for Ubuntu
> users (which is the vast majority) so they will not want to risk
> breaking things. Of course that means I cannot currently update my
> kernel (which they are less concerned about).

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/Ol4Ecudpl8XjKLYN78aQ@public.gmane.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?


Thanks,


-- 
Suresh Jayaraman

Re: Problems with CVS on CIFS since kernel 2.6.30

[Jon Bramley]

On 2 August 2010 16:33, Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
> On 08/02/2010 08:38 PM, Jon Bramley wrote:
>>
>>> The samba version you are using seem to be quite old.. Does better POSIX
>>> support/conformance sound like a good enough reason..?
>>
>> I doubt it. The problem I have is that it is working fine for Ubuntu
>> users (which is the vast majority) so they will not want to risk
>> breaking things. Of course that means I cannot currently update my
>> kernel (which they are less concerned about).
>
> 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/Ol4Ecudpl8XjKLYN78aQ@public.gmane.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:

[  964.362027]  CIFS VFS: Autodisabling the use of server inode
numbers on \\shared.openbet\shared. This server doesn't seem to
support them properly. Hardlinks will not be recognized on this mount.
Consider mounting with the "noserverino" option to silence this
message.
[  964.368470]  CIFS VFS: server 10.194.0.105 of type Samba 3.0.28a
returned unexpected error on SMB posix open, disabling posix open
support. Check if server update available.

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?

Thanks,

Re: Problems with CVS on CIFS since kernel 2.6.30

[Suresh Jayaraman]

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

Re: Problems with CVS on CIFS since kernel 2.6.30

[Jeff Layton]

On Mon, 2 Aug 2010 16:56:10 +0100
Jon Bramley <brammers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> 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:
> 
> [  964.362027]  CIFS VFS: Autodisabling the use of server inode
> numbers on \\shared.openbet\shared. This server doesn't seem to
> support them properly. Hardlinks will not be recognized on this mount.
> Consider mounting with the "noserverino" option to silence this
> message.
> [  964.368470]  CIFS VFS: server 10.194.0.105 of type Samba 3.0.28a
> returned unexpected error on SMB posix open, disabling posix open
> support. Check if server update available.
> 
> 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?
> 

Yes, I agree that the above warnings may have nothing to do with the
problem. We need to understand what the problem is. The strace shows
this:

write(2, "cvs [update aborted]: cannot get"..., 78cvs [update aborted]: cannot get working directory: No such file or directory) = 78

...but I don't see any system calls that returned -ENOENT. Maybe it
occurred in another thread or something?

So I'm a little unclear as to what cvs is complaining about. It's quite
possible that it's ultimately a bug in cifs, but without more info I
really can't guess as to what the problem is. What we really need is a
description of the problem couched in terms of the system call
interface.

-- 
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>

Re: Problems with CVS on CIFS since kernel 2.6.30

[Jon Bramley]

On 2 August 2010 18:14, Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org> wrote:
>
> On Mon, 2 Aug 2010 16:56:10 +0100
> Jon Bramley <brammers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > 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:
> >
> > [  964.362027]  CIFS VFS: Autodisabling the use of server inode
> > numbers on \\shared.openbet\shared. This server doesn't seem to
> > support them properly. Hardlinks will not be recognized on this mount.
> > Consider mounting with the "noserverino" option to silence this
> > message.
> > [  964.368470]  CIFS VFS: server 10.194.0.105 of type Samba 3.0.28a
> > returned unexpected error on SMB posix open, disabling posix open
> > support. Check if server update available.
> >
> > 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?
> >
>
> Yes, I agree that the above warnings may have nothing to do with the
> problem. We need to understand what the problem is. The strace shows
> this:
>
> write(2, "cvs [update aborted]: cannot get"..., 78cvs [update aborted]: cannot get working directory: No such file or directory) = 78
>
> ...but I don't see any system calls that returned -ENOENT. Maybe it
> occurred in another thread or something?
>
> So I'm a little unclear as to what cvs is complaining about. It's quite
> possible that it's ultimately a bug in cifs, but without more info I
> really can't guess as to what the problem is. What we really need is a
> description of the problem couched in terms of the system call
> interface.
>
> --
> Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>

I've posted the dmesg output with cifsFYI set to 7, for the failed cvs
update command here:

http://paste.org/pastebin/view/21123

One strange thing I noticed, is that at one point it seems to be doing
something with /home/jbramley/cvs_src/appserv/lib/ix86, but that
folder is not in any of my env vars (PATH, LD_LIBRARY_PATH etc.) so I
can see no reason for it to be looking there. Could this be some kind
of inode confusion on the cifs share?

Thanks,

Jon

Re: Problems with CVS on CIFS since kernel 2.6.30

[Jeff Layton]

On Tue, 3 Aug 2010 13:23:30 +0100
Jon Bramley <brammers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> I've posted the dmesg output with cifsFYI set to 7, for the failed cvs
> update command here:
> 
> http://paste.org/pastebin/view/21123
> 
> One strange thing I notice, is that at one point it seems to be doing
> something with /home/jbramley/cvs_src/appserv/lib/ix86, but that folder is
> not in any of my env vars (PATH, LD_LIBRARY_PATH etc.) so I can see no
> reason for it to be looking there. Could this be some kind of inode
> confusion on the cifs share?
> 


*shrug* -- maybe...

Without a clear description of what the actual problem is it's
anybody's guess. All you've really told us so far is that cvs doesn't
work right. We need to understand what's wrong at the system call level
before we can really do much to help you.

I'd not bother with debugging output and such at this point. You need
to focus on the application. What's going wrong with it? Once you
understand that, then we can look at what's happening in the kernel.

-- 
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>