From: Jens Axboe <axboe@kernel.dk>
To: "Jeffrey E. Hundstad" <jeffrey.hundstad@mnsu.edu>
Cc: xfs@oss.sgi.com, nathans@sgi.com
Subject: Re: vmsplice can't work well
Date: Thu, 31 Aug 2006 11:24:41 +0200 [thread overview]
Message-ID: <20060831092440.GC5528@kernel.dk> (raw)
In-Reply-To: <44F5D3C6.1010108@mnsu.edu>
XFS list,
On Wed, Aug 30 2006, Jeffrey E. Hundstad wrote:
> Jens Axboe wrote:
> >On Wed, Aug 30 2006, Jeffrey E. Hundstad wrote:
> >
> >>I tried your splie-git...tar.gz file and tried the splice-cp. It
> >>produced files that are the right length... but the files only contain
> >>nulls. Here's the straces:
> >>
> >
> >Works for me as well. Could be an fs issue, how large was the README and
> >what filesystem did you use?
> >
> >
> The file was 1130 bytes (it was the README in that directory.) The
> filesystem is XFS.
>
I can reproduce this quite easily, doing:
nelson:~ # splice-cp sda.blktrace.0 foo
nelson:~ # md5sum sda.blktrace.0 foo
4754070ae77091468c830ea23b125d68 sda.blktrace.0
efdc7b9d00692fdfe91a691277209267 foo
'foo' contains only zeroes. Doing the same on ext3 yields the correct
results, foo contains the right data. I'm testing on
2.16.18-rc5-current, Jeffrey used 2.6.17.x latest.
--
Jens Axboe
next parent reply other threads:[~2006-08-31 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44F4440F.1090300@gmail.com>
[not found] ` <20060829140542.GN12257@kernel.dk>
[not found] ` <44F5CC08.8010205@mnsu.edu>
[not found] ` <20060830174815.GF7331@kernel.dk>
[not found] ` <44F5D3C6.1010108@mnsu.edu>
2006-08-31 9:24 ` Jens Axboe [this message]
2006-08-31 23:17 ` vmsplice can't work well David Chinner
2006-08-31 23:18 ` Nathan Scott
2006-09-01 13:19 ` David Chinner
2006-09-01 13:45 ` Jens Axboe
2006-09-02 2:31 ` Jeffrey E. Hundstad
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=20060831092440.GC5528@kernel.dk \
--to=axboe@kernel.dk \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=nathans@sgi.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox