From: David Disseldorp <ddiss@suse.de>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: FSCTL_QUERY_ALLOCATED_RANGES issue with Windows2016
Date: Tue, 20 Aug 2019 00:03:48 +0200 [thread overview]
Message-ID: <20190820000348.440ee8ce@suse.de> (raw)
In-Reply-To: <20190819183151.15642e8f@suse.de>
On Mon, 19 Aug 2019 18:31:51 +0200, David Disseldorp wrote:
> Nothing stands out in the captures to me, but I'd be curious whether you
> see any differences in behaviour if you set write-through on open or
> explicitly FLUSH after the SET-SPARSE call.
Hmm actually it looks like there's already a FLUSH shortly after the
mtime update following the SetInfo(EOF). One thing that does look a
little weird is the AllocationSize field before that FLUSH - in
seek_bad.cap.gz it's 2M, whereas it's ~6M in seek_good.cap.gz.
This'd be a good case to use Aurélien's smbcmp utility :)
Cheers, David
next prev parent reply other threads:[~2019-08-19 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 6:30 FSCTL_QUERY_ALLOCATED_RANGES issue with Windows2016 ronnie sahlberg
2019-08-15 15:15 ` Tom Talpey
2019-08-16 2:17 ` ronnie sahlberg
2019-08-15 15:48 ` David Disseldorp
2019-08-16 2:07 ` ronnie sahlberg
2019-08-16 4:36 ` ronnie sahlberg
2019-08-19 16:31 ` David Disseldorp
2019-08-19 22:03 ` David Disseldorp [this message]
2019-08-20 17:47 ` Tom Talpey
2019-08-22 22:46 ` ronnie sahlberg
2019-08-16 9:07 ` David Disseldorp
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=20190820000348.440ee8ce@suse.de \
--to=ddiss@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.