Re: Block device integrity support

2017-06-03 Thread Jens Axboe
On 06/03/2017 12:32 AM, Christoph Hellwig wrote: > On Fri, Jun 02, 2017 at 03:52:57PM -0700, Jens Axboe wrote: >> On 06/02/2017 03:38 PM, Bart Van Assche wrote: >>> On Fri, 2017-06-02 at 18:24 -0400, Martin K. Petersen wrote: > then the output shown below appears in the kernel log. Does anyone

Re: Block device integrity support

2017-06-03 Thread Christoph Hellwig
On Fri, Jun 02, 2017 at 03:52:57PM -0700, Jens Axboe wrote: > On 06/02/2017 03:38 PM, Bart Van Assche wrote: > > On Fri, 2017-06-02 at 18:24 -0400, Martin K. Petersen wrote: > >>> then the output shown below appears in the kernel log. Does anyone know > >>> how > >>> to fix this? Sorry but I'm not

Re: Block device integrity support

2017-06-02 Thread Jens Axboe
On 06/02/2017 03:38 PM, Bart Van Assche wrote: > On Fri, 2017-06-02 at 18:24 -0400, Martin K. Petersen wrote: >>> then the output shown below appears in the kernel log. Does anyone know how >>> to fix this? Sorry but I'm not really familiar with the integrity >>> code. >> >> Dmitry posted a fix for

Re: Block device integrity support

2017-06-02 Thread Bart Van Assche
On Fri, 2017-06-02 at 18:24 -0400, Martin K. Petersen wrote: > > then the output shown below appears in the kernel log. Does anyone know how > > to fix this? Sorry but I'm not really familiar with the integrity > > code. > > Dmitry posted a fix for this a few weeks ago. Ah, that's right. Jens, ha

Re: Block device integrity support

2017-06-02 Thread Martin K. Petersen
Jens, > There's not much in my for-next/4.13 branches yet, so I'm assuming this also > triggers with current mainline? Yep. -- Martin K. Petersen Oracle Linux Engineering

Re: Block device integrity support

2017-06-02 Thread Martin K. Petersen
Bart, > modprobe scsi_debug delay=0 dif=3 dix=-1 dev_size_mb=16 Those options don't make much sense. > then the output shown below appears in the kernel log. Does anyone know how > to fix this? Sorry but I'm not really familiar with the integ

Re: Block device integrity support

2017-06-02 Thread Jens Axboe
On 06/02/2017 02:53 PM, Bart Van Assche wrote: > Hello Jens and Christoph, > > With Jens' for-next branch (commit fe02d46ab775), if I run the following > commands: > > modprobe scsi_debug delay=0 dif=3 dix=-1 dev_size_mb=16 > mkfs.xfs /dev/disk/by-id/scsi-1Linux_scsi_debug_22000 > > then

Block device integrity support

2017-06-02 Thread Bart Van Assche
Hello Jens and Christoph, With Jens' for-next branch (commit fe02d46ab775), if I run the following commands: modprobe scsi_debug delay=0 dif=3 dix=-1 dev_size_mb=16 mkfs.xfs /dev/disk/by-id/scsi-1Linux_scsi_debug_22000 then the output shown below appears in the kernel log. Does anyone kn