On Wed, Aug 15, 2012 at 10:40:08PM +1000, Joseph Glanville wrote: > Hi James, Kent. > > I can confirm this is the issue I was seeing, thanks for locating the > blkback issue! Cool! > Is there anything xen-devel should be doing about this? I wouldn't > expect blkback to care about block size... Well, I wouldn't be surprised if Windows doesn't work on a device with block size > 512 bytes. But Linux (ext4 at least) certaintly does work with 4k blocks - unless maybe it was breaking on something in the boot process? So it sounds like this might be indicative of a bug in blkback. > Joseph. > > On 14 August 2012 09:30, James Harper <james.harper@xxxxxxxxxxxxxxxx> wrote: > >> > >> Just mentioned this in the other thread, but if this is due to the 4k blocksize - > >> that's easy to fix: just format with 512 byte blocksize > >> > >> make-bcache --block 512 > >> > >> Maybe I should change the default. > > > > I suggest making the default 512, but also print a warning if the user didn't explicitly set it,eg "Block size not set - defaulting to 512 bytes" > > > > James > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > CTO | Orion Virtualisation Solutions | www.orionvm.com.au > Phone: 1300 56 99 52 | Mobile: 0428 754 846 -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
