linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@humilis.net>
To: Daniel Flinkmann <DFlinkmann@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0test11 overwriting file on mounted smb volume causes corrupted files!
Date: Mon, 1 Dec 2003 12:21:12 +0100	[thread overview]
Message-ID: <20031201112112.GA22180@favonius> (raw)
In-Reply-To: <200311290156.02239.DFlinkmann@gmx.de>

Hi Daniel,

Daniel Flinkmann wrote (ao):
> [Please CC to me directly, I'm not on the linix kernel mailing list]
> 
> [1.] One line summary of the problem:
> 
> 2.6.0test11 overwriting file on mounted smb volume causes corrupted files! 

I saw te same with -test9 with cifs.
For some reason the November archive of
http://lists.samba.org/archive/samba-technical/ is gone, but google has
my report cached. Search for:

"problem with updating files on cifs mount"

I'm still stuck btw.

  reply	other threads:[~2003-12-01 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29  0:56 2.6.0test11 overwriting file on mounted smb volume causes corrupted files! Daniel Flinkmann
2003-12-01 11:21 ` Ookhoi [this message]
2003-12-01 11:42   ` Daniel Flinkmann

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=20031201112112.GA22180@favonius \
    --to=ookhoi@humilis.net \
    --cc=DFlinkmann@gmx.de \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).