On Tue, Apr 03, 2012 at 04:35:28PM +0800, Liu Bo wrote: > > That's strange. Does it mean that if I create the filesystem and then > > reboot to another kernel with different PAGE_SIZE then the filesystem > > is unaccessible for me? > > I'm afraid yes until we can deal with sectorsize and PAGE_SIZE > gracefully. > > For now, I didn't test if a read will cause oops or not, but if it's > ok, an alternative way is to make FS readonly.
Writes will cause hang. I have tested that read-only mount of a 64k sectorsize is ok, file reads do not hang, but any file larger than the inline limit is empty due to failed csums. Example read of 65483 ./drivers/scsi/qla2xxx/qla_isr.c leads to [ 9249.370133] btrfs csum failed ino 13837 off 0 csum 4169121208 private 3722900035 while reading 65471 ./arch/powerpc/platforms/cell/spufs/file.c is just fine. So for now even forcing a read-only mount is not good option, though we may try to enhance the csum verification. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
