On Mon, Jul 27, 2015 at 06:40:57AM -0400, Ming Lei wrote: > On Fri, Jul 17, 2015 at 3:27 AM, Hannes Reinecke <[email protected]> wrote: > > Currently the loop driver just simulates 512-byte blocks. When > > creating images for virtual machines it might be required to use > > a different physical blocksize (eg 4k for S/390 DASD). > > Looks 'qemu-img create' doesn't have parameter of block size, > so could you share your use case? And I am just curious why > 512-byte can't work for this case.
The use case is to suppot 4k sectors sizes such as DASDs usually provide, or just to create a 4k block device to check your filesystem of choice handles 4k sectors just fine. Replace 4k with other sector sizes of your choice for added benefit. In addition to the DASD use case it's really a very useful debugging tool. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
