From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-block@vger.kernel.org, nbd-general@lists.sourceforge.net
Subject: Re: NBD: exported files over something around 1 TiB get an insane device size on the client side and are actually empty
Date: Sun, 15 Jan 2017 02:27:25 +0100 [thread overview]
Message-ID: <1484443645.7110.33.camel@scientia.net> (raw)
In-Reply-To: <1484442228.7132.0@smtp.office365.com>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
On Sat, 2017-01-14 at 20:03 -0500, Josef Bacik wrote:
> nbd: use loff_t for blocksize and nbd_set_size args
I'm just trying your patch, which does however not apply to 4.9.2 (but
I've adapted it)... will tell later if it worked for me.
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2017-01-15 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 23:31 NBD: exported files over something around 1 TiB get an insane device size on the client side and are actually empty Christoph Anton Mitterer
2017-01-15 1:03 ` Josef Bacik
2017-01-15 1:27 ` Christoph Anton Mitterer [this message]
2017-01-15 4:27 ` Christoph Anton Mitterer
2017-01-15 7:13 ` [Nbd] " Alex Bligh
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=1484443645.7110.33.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=jbacik@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
/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