From: Peter Chant <pete@petezilla.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: All free space eaten during defragmenting (3.14)
Date: Sun, 01 Jun 2014 21:39:18 +0100 [thread overview]
Message-ID: <538B8F76.9090500@petezilla.co.uk> (raw)
In-Reply-To: <pan$d1ec3$d22b3db$8681b9b1$d9742e40@cox.net>
I have a question that has arisen from reading one of Duncan's posts:
On 06/01/2014 01:56 AM, Duncan wrote:
> Here's the deal. Due to scaling issues the original snapshot aware
> defrag code was recently disabled, so defrag now doesn't worry about
> snapshots, only defragging whatever is currently mounted. If you have a
> lot of fragmentation and are using snapshots, the defrag will copy all
> those fragmented files in ordered to defrag them, thus duplicating their
> blocks and doubling their required space. Based on the title alone,
> that's what I /thought/ happened, and given what you did /not/ say, I
> actually still think it is the case and the below assumes that, tho I'm
> no longer entirely sure.
The above implies to me that snapshots should not normally be mounted?
I may have misread the intent.
* * *
My thought is that I have a btrfs to hold data on my system, it contains
/home in a subvolume and also subvolumes for various other things. I
take daily, hourly and weekly snapshots and my script does delete old
ones after a while.
I also mount the base/default btrfs file system on /mnt/data-pool. This
means that my snapshots are available in their own subdirectory, so I
presume this means that they are mounted, if not in their own right, at
least they are as part of the default subvolume. Given the
defragmentation discussion above should I be doing this or should my
setup ensure that they are not normally mounted?
I'm not aware of how you would create a subvolume that was outside of a
mounted part of the file system 'tree' - so if I did not want my
subvolumes mounted and I wanted snapshots then I'd have to mount the
default subvolume, make snapshots, and then unmount it? This seems a
bit clumsy and I'm not convinced that this is a sensible plan. I don't
think this is right, can anyone confirm or deny?
I do note I get pauses every so often for a second or two or three while
I believe btrfs is doing 'stuff'. Although annoying I do find I am
prepared to live with this as the subvolumes and snap-shotting are
valuable to me.
Pete
--
Peter Chant
next prev parent reply other threads:[~2014-06-01 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 7:19 All free space eaten during defragmenting (3.14) Szőts Ákos
2014-06-01 0:56 ` Duncan
2014-06-01 1:56 ` Duncan
2014-06-01 20:39 ` Peter Chant [this message]
2014-06-01 22:47 ` Duncan
2014-06-02 20:54 ` Peter Chant
2014-06-03 4:46 ` Duncan
2014-06-03 22:21 ` Peter Chant
2014-06-04 9:21 ` Duncan
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=538B8F76.9090500@petezilla.co.uk \
--to=pete@petezilla.co.uk \
--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).