Linux CIFS filesystem development
 help / color / mirror / Atom feed
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 20:23:17 +0530	[thread overview]
Message-ID: <4C56DBDD.4070501@suse.de> (raw)
In-Reply-To: <AANLkTingdjU-KKW3=KboAnR0pNeiE7aEje0nXhM6bYbe-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

  parent reply	other threads:[~2010-08-02 14:53 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 [this message]
     [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
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=4C56DBDD.4070501@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