On Thu, Aug 3, 2017 at 11:51 PM, Shyam Prasad N <nspmangal...@gmail.com> wrote: > Hi all, > > We're running a couple of experiments on our servers with btrfs > (kernel version 4.4). > And we're running some abrupt power-off tests for a couple of scenarios: > > 1. We have a filesystem on top of two different btrfs filesystems > (distributed across N disks).
What's the layout from physical devices all the way to your 16M file? This is hardware raid, lvm linear, Btrfs raid? All of that matters. Do the drives have write caching disabled? You might be better off with the drive write cache disabled, and then add bcache or dm-cache and an SSD to compensate. But that's just speculation on my part. The write cache in the drives is definitely volatile. And disabling them will definitely make writes slower. So, you might have slightly better luck with another layout. But the bottom line is, you need to figure out a way to avoid *any* data loss in your files because otherwise that means the 2nd file system has data loss and even corruption. This is not something a file system choice can solve. You need reliable power and reliable shutdown. And you may also need a cluster file system like ceph or glusterfs instead of depending on a single box to stay upright. -- Chris Murphy -- 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
