Bug#851533: NBD: exported files over something around 1 TiB get an insane device size on the client side and are actually empty

On Mon, Jan 16, 2017 at 11:37 AM, Ben Hutchings wrote: > > This should possibly go to 4.9-stable, but in any case I've queued it > up for our next upload. After applying this patch, it fails to build on armel [0] And I find it need another patch [1] [0]

Bug#851533: NBD: exported files over something around 1 TiB get an insane device size on the client side and are actually empty

On Mon, 2017-01-16 at 02:37 +, Ben Hutchings wrote: > This should possibly go to 4.9-stable, but in any case I've queued it > up for our next upload. Could you ping the responsible people? Guess you have far better contacts there than me ;-) Cheers, Chris. smime.p7s Description: S/MIME

Bug#851533: NBD: exported files over something around 1 TiB get an insane device size on the client side and are actually empty

Control: tag -1 pending On Mon, 2017-01-16 at 00:35 +0100, Christoph Anton Mitterer wrote: > Source: linux > Version: 4.9.2-2 > Severity: normal > Tags: patch upstream > > > Hey. > > There's an issue in NBD which prevents some larger images to be > correctly "connected" on the client side (if

Bug#851533: NBD: exported files over something around 1 TiB get an insane device size on the client side and are actually empty

Source: linux Version: 4.9.2-2 Severity: normal Tags: patch upstream Hey. There's an issue in NBD which prevents some larger images to be correctly "connected" on the client side (if done by the kernel), largely described here: https://github.com/NetworkBlockDevice/nbd/issues/44 Thers's a