All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erkki Seppala <flux-btrfs@inside.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: What to do about snapshot-aware defrag
Date: Wed, 04 Jun 2014 12:19:05 +0300	[thread overview]
Message-ID: <m49fvjlghh2.fsf@coffee.modeemi.fi> (raw)
In-Reply-To: lmln77$ee0$1@ger.gmane.org

Martin <m_btrfs@ml1.co.uk> writes:

> The *ONLY* application that I know of that uses atime is Mutt and then
> *only* for mbox files!...

However, users, such as myself :), can be interested in when a certain
file has been last accessed. With snapshots I can even get an idea of
all the times the file has been accessed.

> *And go KISS and move on faster* better?

Well, it in uncertain to me if it truly is better that btrfs would after
that point no longer truly even support atime, if using it results in
blowing up snapshot sizes. They might at that point even consider just
using LVM2 snapshots (shudder) ;).

-- 
  _____________________________________________________________________
     / __// /__ ____  __               http://www.modeemi.fi/~flux/\   \
    / /_ / // // /\ \/ /                                            \  /
   /_/  /_/ \___/ /_/\_\@modeemi.fi                                  \/


  reply	other threads:[~2014-06-04  9:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 20:43 What to do about snapshot-aware defrag Josef Bacik
2014-05-30 22:00 ` Martin
2014-05-31 23:51   ` Brendan Hide
2014-06-01  1:52     ` Duncan
2014-06-02  3:07     ` Mitch Harder
2014-06-02 13:19       ` Josef Bacik
2014-06-02 13:22   ` Josef Bacik
2014-06-03 23:54     ` Martin
2014-06-04  9:19       ` Erkki Seppala [this message]
2014-06-04 13:15         ` Martin
2014-06-04 19:33           ` Chris Murphy

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=m49fvjlghh2.fsf@coffee.modeemi.fi \
    --to=flux-btrfs@inside.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.