Am Mon, 27 Mar 2017 20:06:46 +0500 schrieb Roman Mamedov <r...@romanrm.net>:
> On Mon, 27 Mar 2017 16:49:47 +0200 > Christian Theune <c...@flyingcircus.io> wrote: > > > Also: the idea of migrating on btrfs also has its downside - the > > performance of “mkdir” and “fsync” is abysmal at the moment. I’m > > waiting for the current shrinking job to finish but this is likely > > limited to the “find free space” algorithm. We’re talking about a > > few megabytes converted per second. Sigh. > > Btw since this is all on LVM already, you could set up lvmcache with > a small SSD-based cache volume. Even some old 60GB SSD would work > wonders for performance, and with the cache policy of "writethrough" > you don't have to worry about its reliability (much). That's maybe the best recommendation to speed things up. I'm using bcache here for the same reasons (speeding up random workloads) and it works wonders. Tho, for such big storage I'd maybe recommend a bigger SSD and a new one. Bigger SSDs tend to last much longer. Just don't use the whole of it to allow for better wear leveling and you'll get a final setup that can serve the system much longer than for the period of migration. -- Regards, Kai Replies to list-only preferred. -- 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
