Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Jon Bramley <brammers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Problems with CVS on CIFS since kernel 2.6.30
Date: Tue, 3 Aug 2010 08:35:14 -0400	[thread overview]
Message-ID: <20100803083514.1179c92c@corrin.poochiereds.net> (raw)
In-Reply-To: <AANLkTim=gnAh4G_JeRCEcCkfXb5pQwTTKh6+-7yAyyHu-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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>

      parent reply	other threads:[~2010-08-03 12:35 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
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 [this message]

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=20100803083514.1179c92c@corrin.poochiereds.net \
    --to=jlayton-eunubhrolfbytjvyw6ydsg@public.gmane.org \
    --cc=brammers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sjayaraman-l3A5Bk7waGM@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