> On 11 Feb 2017, at 12:43, Wouter Verhelst wrote:
>
>>> Interesting. Some input into the info extension (re blocksizes) would
>>> definitely be appreciated.
>>>
>>
>> What do you mean? Right now the client is just calling NBD_SET_BLKSIZE
>> with 4k blocksize since all of our devices are 4k d
On Fri, Feb 10, 2017 at 04:47:42PM -0500, Josef Bacik wrote:
> On Fri, 2017-02-10 at 21:07 +0100, Alex Bligh wrote:
> > >
> > > On 10 Feb 2017, at 19:06, Josef Bacik wrote:
> > >
> > > We noticed when trying to do O_DIRECT to an export on the server
> > > side
> > > that we were getting requests
On Fri, 2017-02-10 at 21:07 +0100, Alex Bligh wrote:
> >
> > On 10 Feb 2017, at 19:06, Josef Bacik wrote:
> >
> > We noticed when trying to do O_DIRECT to an export on the server
> > side
> > that we were getting requests smaller than the 4k sectorsize of the
> > device. This is because the cli
> On 10 Feb 2017, at 19:06, Josef Bacik wrote:
>
> We noticed when trying to do O_DIRECT to an export on the server side
> that we were getting requests smaller than the 4k sectorsize of the
> device. This is because the client isn't setting the logical and
> physical blocksizes properly for th
