From: Oystein Viggen <oysteivi@tihlde.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: What do the arguments of btrfs filesystem defragment do?
Date: Thu, 16 Dec 2010 09:41:50 +0100 [thread overview]
Message-ID: <037hfaxg6p.fsf@msgid.viggen.net> (raw)
In-Reply-To: 1292441925-sup-1105@think
* [Chris Mason]=20
> Excerpts from Erik Logtenberg's message of 2010-12-15 14:26:49 -0500:
>>=20
>> The use case is a filesystem used for backups, which are rsynced
>> nightly, after which a new snapshot is made. After something like 45
>> days, the old snapshots are removed. I am assuming that this way, af=
ter
>> 45 days all files will be compressed naturally, but this is only
>> beneficial if snapshots still fully work. If instead it results in
>> storing the compressed form of every file 45 times on disk, then it
>> won't help much.
>
> Yes, you'll end up with a fully compressed and fully shared setup aft=
er
> 45 days.
How would that happen? Rsync only rewrites files if they have changed.
If compression happens only when a file is written to, any files that
were written uncompressed will remain uncompressed until they change on
the source filesystem (triggering a rewrite on the backup drive).
Unless there's some magic I'm missing, expiring the old snapshots from
before -o compress won't really affect anything.
=D8ystein
--=20
Outgoing mail is certified Virus Free.
=2E.of course, the virus would tell you the same thing..
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-16 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 16:06 What do the arguments of btrfs filesystem defragment do? Erik Logtenberg
2010-12-15 19:08 ` Chris Mason
2010-12-15 19:14 ` Erik Logtenberg
2010-12-15 19:20 ` Chris Mason
2010-12-15 19:26 ` Erik Logtenberg
2010-12-15 19:57 ` Chris Mason
2010-12-16 8:41 ` Oystein Viggen [this message]
2010-12-16 20:48 ` David Nicol
2010-12-15 19:18 ` Goffredo Baroncelli
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=037hfaxg6p.fsf@msgid.viggen.net \
--to=oysteivi@tihlde.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.