On Thu, Jul 02, 2009 at 05:22:24PM +0200, Tomasz Chmielewski wrote: > Chris Mason wrote: >> On Fri, 2009-04-24 at 01:34 +0200, Tomasz Chmielewski wrote: >>> Chris Mason schrieb: >>> >>>>> However, with btrfs, I'm not sure about: >>>>> >>>>> - what happens if SAN machine crashes while the iSCSI file images >>>>> were being written to; with LVM and its block devices, I'm >>>>> somehow more confident it wouldn't make more data loss than >>>>> necessary >>>> If iscsi is writing with O_DIRECT|O_SYNC it should work. >>> What if it doesn't? >>> >> >> Writes would go to the page cache only (not O_DIRECT) and the metadata >> wouldn't get flushed with each write (not O_SYNC). > > What about the "administrative" part of using btrfs as a volume manager? In this case it depends on exactly how you do it. If you're just using files and putting filesystems on those files (not partitioning inside the image), then you can use truncate to shrink the image and fallocate (or truncate if you want it sparse) to extend it. If you want to make partition tables inside the volumes, then you need to do the truncate/fallocate game and also change the partition table. -chris -- 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
