linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ching <lsching17@gmail.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: enquiry about autodefrag option
Date: Thu, 20 Sep 2012 07:36:53 +0800	[thread overview]
Message-ID: <505A5715.9060309@gmail.com> (raw)
In-Reply-To: <5059D2D3.3050303@oracle.com>


>>> 2. AFAIK, "autodefrag" detects small random writes into files and
>>> queues them up for an automatic defrag process, so the filesystem will
>>> defragment itself while it's used.
>>>
>>>     If the system reboot/crash/remount-ro, will the autodefrag process
>>> continue after resume?
>>>
> For reboot, autodefrag will be waited to finish during umounting btrfs.
>
> For crash and remount-ro, it won't resume since it is not that necessary and we're all
> COWed so that the data is ok.
>
> And autodefrag will only take effect when taking the 'autodefrag' mount option.
>
> thanks,
> liubo
>
>

Can the loophole be fixed by tuning the autodefrag algorithm? e.g. also queue up small extents detected during read operation for the autodefrag process.

Is there any io niceness control for autodefrag process too? it will be nice if the idle class is used.


Actually, i try to write shell script to defrag entire FS monthy. but i soon find out it is hard to keep track of progress across reboot and avoid redefragging defragged file

For me, autodefrag is a killer feature. :)


  parent reply	other threads:[~2012-09-19 23:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 11:15 enquiry about autodefrag option (resent) ching
2012-09-19 11:28 ` enquiry about autodefrag option ching
2012-09-19 14:12   ` Liu Bo
2012-09-19 17:39     ` Martin Steigerwald
2012-09-20 14:05       ` David Sterba
2012-09-19 23:36     ` ching [this message]
2012-09-20 11:51       ` David Sterba
2012-09-20 21:03         ` ching
2012-09-24 15:50           ` David Sterba
  -- strict thread matches above, loose matches on Subject: below --
2012-09-17  6:12 ching lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=505A5715.9060309@gmail.com \
    --to=lsching17@gmail.com \
    --cc=bo.li.liu@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).