Gabriel de Perthuis posted on Sat, 20 Jul 2013 22:47:46 + as
excerpted:
> On Sat, 20 Jul 2013 17:15:50 +0200, Jason Russell wrote:
>> Ive also noted that this excessive hdd chatter does not occur
>> immediately after a fresh format with arch on btrfs root.
>>
>> Ive made some deductions/assum
On Jul 21, 2013, at 4:38 AM, Duncan <1i5t5.dun...@cox.net> wrote:
>
> What I'd suggest is to turn on the btrfs autodefrag mount option, and to
> do it *BEFORE* you start installing stuff on the filesystem.
Is there a good reason why autodefrag is not a default mount option?
> I believe
> it
Chris Murphy posted on Sun, 21 Jul 2013 10:20:48 -0600 as excerpted:
> On Jul 21, 2013, at 4:38 AM, Duncan <1i5t5.dun...@cox.net> wrote:
>>
>> What I'd suggest is to turn on the btrfs autodefrag mount option, and
>> to do it *BEFORE* you start installing stuff on the filesystem.
>
> Is there a g
On 07/21/2013 03:01 PM, Duncan wrote:
Chris Murphy posted on Sun, 21 Jul 2013 10:20:48 -0600 as excerpted:
On Jul 21, 2013, at 4:38 AM, Duncan <1i5t5.dun...@cox.net> wrote:
What I'd suggest is to turn on the btrfs autodefrag mount option, and
to do it *BEFORE* you start installing stuff on the
On Sunday, July 21, 2013 04:44:09 PM George Mitchell wrote:
> Unless auto-defrag can work around the
> in-use file issue, that could be a problem since some heavily used
> system files are open virtually all the time the system is up and
> running. Has this issue been investigated and if so are
On 07/21/2013 08:37 PM, Shridhar Daithankar wrote:
On Sunday, July 21, 2013 04:44:09 PM George Mitchell wrote:
Unless auto-defrag can work around the
in-use file issue, that could be a problem since some heavily used
system files are open virtually all the time the system is up and
running. Has
On Sunday, July 21, 2013 08:53:42 PM George Mitchell wrote:
> > system files typically are installed once and never rewritten in place, so
> > they should not be much fragmented to begin with.
> >
> > now their directory objects, is a different story and so is things like
> > systemd journal, log
You /really/ need to read up on the btrfs wiki.
The short answer is yes, btrfs does a LOT more metadata processing
due to the checksumming it does by default.
According to the wiki, checksumming has barely any influence, so I
guess the above advice is not really helpful?
https://btrfs.wiki.ker
The alloc_rbio() frees "raid_map" and "bbio" on error, so there is a
potential double free bug in raid56_parity_write(). The
raid56_parity_write() and raid56_parity_recover() functions should still
free "raid_map" and "bbio" on error if other errors occur though, so I
have added some more calls to
