Chris Mason wrote: > On Mon, Oct 25, 2010 at 03:11:22PM +0800, Li Zefan wrote: >> Lzo is a much faster compression algorithm than gzib, so would allow >> more users to enable transparent compression, and some users can >> choose from compression ratio and compression speed. > > This is also much smaller than I expected, really nice. It looks like > older kernels won't properly deal (nicely give EIO) with lzo compressed > files? > > We can add compatbits to deal with that if it is the case. > I forgot compatibility issue with older kernels.. Though I didn't test older kernels, I don't think they can deal with lzo compressed files properly, at least not for inlined extents, in which case I think btrfs will just show compressed data to the users. So yes, an incompat flag is needed. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
