Re: Data and metadata extent allocators [1/2]: Recap: The data story

2017-10-31 Thread Hans van Kranenburg
On 10/28/2017 02:12 AM, Qu Wenruo wrote: > > On 2017年10月28日 02:17, Hans van Kranenburg wrote: >> Hi, >> >> This is a followup to my previous threads named "About free space >> fragmentation, metadata write amplification and (no)ssd" [0] and >> "Experiences with metadata balance/convert" [1], explo

Re: Data and metadata extent allocators [1/2]: Recap: The data story

2017-10-27 Thread Qu Wenruo
On 2017年10月28日 02:17, Hans van Kranenburg wrote: > Hi, > > This is a followup to my previous threads named "About free space > fragmentation, metadata write amplification and (no)ssd" [0] and > "Experiences with metadata balance/convert" [1], exploring how good or > bad btrfs can handle filesyst

Re: Data and metadata extent allocators [1/2]: Recap: The data story

2017-10-27 Thread Hans van Kranenburg
Hi Martin, On 10/27/2017 10:10 PM, Martin Steigerwald wrote: >> Q: How do I fight this and prevent getting into a situation where all >> raw space is allocated, risking a filesystem crash? >> A: Use btrfs balance to fight the symptoms. It reads data and writes it >> out again without the free spac

Re: Data and metadata extent allocators [1/2]: Recap: The data story

2017-10-27 Thread Martin Steigerwald
Hello Hans, Hans van Kranenburg - 27.10.17, 20:17: > This is a followup to my previous threads named "About free space > fragmentation, metadata write amplification and (no)ssd" [0] and > "Experiences with metadata balance/convert" [1], exploring how good or > bad btrfs can handle filesystems that

Data and metadata extent allocators [1/2]: Recap: The data story

2017-10-27 Thread Hans van Kranenburg
Hi, This is a followup to my previous threads named "About free space fragmentation, metadata write amplification and (no)ssd" [0] and "Experiences with metadata balance/convert" [1], exploring how good or bad btrfs can handle filesystems that are larger than your average desktop computer and/or w