Le 15/08/16 à 08:32, "Austin S. Hemmelgarn" <[email protected]> a écrit :
ASH> On 2016-08-15 06:39, Daniel Caillibaud wrote: ASH> > I'm newbie with btrfs, and I have pb with high load after each btrfs subvolume delete […] ASH> Before I start explaining possible solutions, it helps to explain what's ASH> actually happening here. […] Thanks a lot for these clear and detailed explanations. ASH> > Is there a better way to do so ? ASH> While there isn't any way I know of to do so, there are ways you can ASH> reduce the impact by reducing how much your backing up: Thanks for these clues too ! I'll use --commit-after, in order to wait for complete deletion before starting rsync the next snapshot, and I keep in mind the benefit of putting /var/log outside the main subvolume of the vm (but I guess my main pb is about databases, because their datadir are the ones with most writes). -- Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
