Re: [dm-devel] [PATCH v3 1/2] dm-unstripe: unstripe RAID 0/dm-striped device

2017-12-23 Thread Scott Bauer
[snip] On Wed, Dec 13, 2017 at 04:11:44PM -0800, Randy Dunlap wrote: > > >= > Thanks, good catch. > > + tot_sec = i_size_read(bbdev->bd_inode) >> SECTOR_SHIFT; > > + mod = tot_sec % target->chunk_sectors; > > Did you build this on 32-bit also? Is th

Re: [dm-devel] [PATCH v3 1/2] dm-unstripe: unstripe RAID 0/dm-striped device

2017-12-15 Thread Randy Dunlap
On 12/15/2017 07:27 AM, Scott Bauer wrote: > [snip] > On Wed, Dec 13, 2017 at 04:11:44PM -0800, Randy Dunlap wrote: >> >>>= >> > > Thanks, good catch. > > >>> + tot_sec = i_size_read(bbdev->bd_inode) >> SECTOR_SHIFT; >>> + mod = tot_sec % target->chunk

[dm-devel] [PATCH v3 1/2] dm-unstripe: unstripe RAID 0/dm-striped device

2017-12-14 Thread Scott Bauer
This device mapper module remaps and unstripes IO so it lands solely on a single drive in a RAID 0/dm-stripe target. In a 4 drive RAID 0 the mapper exposes 1/4th of the LBA range as a virtual drive. Each IO to that virtual drive will land on only one of the 4 drives, selected by the user. Signed-o

Re: [dm-devel] [PATCH v3 1/2] dm-unstripe: unstripe RAID 0/dm-striped device

2017-12-13 Thread Randy Dunlap
On 12/13/2017 01:33 PM, Scott Bauer wrote: > This device mapper module remaps and unstripes IO so it lands > solely on a single drive in a RAID 0/dm-stripe target. > In a 4 drive RAID 0 the mapper exposes 1/4th of the LBA range > as a virtual drive. Each IO to that virtual drive will land on > only