public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: "idra@samba.org" <idra@samba.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-cifs-client <linux-cifs-client@lists.samba.org>,
	Steve French <sfrench@samba.org>, Avi Kivity <avi@argo.co.il>
Subject: Re: [linux-cifs-client] Re: 2.6.19.1 bug? tar: file changed as we read it
Date: Tue, 19 Dec 2006 02:02:16 -0500	[thread overview]
Message-ID: <200612190205_MC3-1-D591-6D92@compuserve.com> (raw)

In-Reply-To: <1166458956.30152.18.camel@localhost.localdomain>

On Mon, 18 Dec 2006 11:22:36 -0500, simo wrote:

> > With cifs, a directory search shows different sizes but opening
> > them by name gives identical contents:
> > 
> > $ ll ipt_dscp* ipt_DSCP*
> > -r-------- 1 me me 1581 Jan 28  2004 ipt_dscp.c
> > -r-------- 1 me me 2753 Jan 29  2004 ipt_DSCP.c
> > $ ll ipt_dscp.c ipt_DSCP.c
> > -r-------- 1 me me 1581 Jan 28  2004 ipt_dscp.c
> > -r-------- 1 me me 1581 Jan 28  2004 ipt_DSCP.c
> > $ diff ipt_dscp.c ipt_DSCP.c
> > $
> > 
> > So where is the bug? On the server?
> 
> What is the server?
> Samba? Which vertsion?

Samba 2.2.3.

> Do you use unix extensions? Or "case sensitive = yes" ?

No UNIX extensions.  Not case sensitive.

SO this is kind of expected, but smbfs and cifs client for Linux have
subtly different behavior.

-- 
MBTI: IXTP

             reply	other threads:[~2006-12-19  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19  7:02 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-18 16:13 2.6.19.1 bug? tar: file changed as we read it Chuck Ebbert
2006-12-18 16:22 ` [linux-cifs-client] " simo

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=200612190205_MC3-1-D591-6D92@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=avi@argo.co.il \
    --cc=idra@samba.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.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