On Fri, 23 May 2014 00:34:25 +0200, Stefan G. Weichinger wrote:
I'm working on this btrfs malarkey and have a question about best
practice. It is recommended to leave the root volume empty and
create a subvolume for the root filesystem which is set with btrfs
subvolume set-default, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 27.05.2014 09:59, schrieb Neil Bothwick:
Alternative: mount the subvol via option subvolid etc in fstab
if you plan to mount different snapshots, for example.
I went with set-default for the root subvolume, if I need the root
volume I
On Tuesday 27 May 2014 11:57:58 Stefan G. Weichinger wrote:
Am 27.05.2014 09:59, schrieb Neil Bothwick:
Alternative: mount the subvol via option subvolid etc in fstab
if you plan to mount different snapshots, for example.
I went with set-default for the root subvolume, if I need the
On Tue, May 27, 2014 at 7:25 AM, Mick michaelkintz...@gmail.com wrote:
Also how big is each snapshot of / and why are these necessary on an hourly
basiszfs ?
Btrfs is COW, so snapshots only consume space as files change. If you
have a read-only filesystem and snapshot it hourly the only space
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 27.05.2014 13:25, schrieb Mick:
I recall that zfs needed a lot of RAM = 8M, is it the same with
BTRFS?
I assume you mean 8GB ?
As far as I know and researched: no, btrfs is less memory hungry and
was designed to even work fine on small devices
On Tue, 27 May 2014 12:57:58 +0200, Stefan G. Weichinger wrote:
Trust me to overlook the easy way of doing things, I was looking for
an equivalent to zfs rename and never considered mv.
It feels somehow wrong to only mv them, right? ;-)
It's just too easy, there must be a catch :)
So
On Tue, 27 May 2014 12:25:48 +0100, Mick wrote:
I recall that zfs needed a lot of RAM = 8M, is it the same with BTRFS?
If you means 8GB, it doesn't. I am/was using it on several systems with
4GB. you can control the amount of memory used for its caches.
--
Neil Bothwick
If you consult
On Tue, 27 May 2014 07:38:01 -0400, Rich Freeman wrote:
Snapshotting hourly would mostly be a convenience - in theory it
should get you time-machine-like functionality just like hourly
backups would, but with far less overhead and space use.
In practice I stopped doing this, as btrfs can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 27.05.2014 13:49, schrieb Neil Bothwick:
I have zfs-snapshot making snapshots at 15 minute, hourly, daily,
monthly and weekly intervals - and it cleans up after itself. There
isn't anything quite like that for btrfs, so I'm knocking up a
On Tue, May 27, 2014 at 7:49 AM, Neil Bothwick n...@digimed.co.uk wrote:
I have zfs-snapshot making snapshots at 15 minute, hourly, daily, monthly
and weekly intervals - and it cleans up after itself. There isn't
anything quite like that for btrfs, so I'm knocking up a python script to
take
Am 27.05.2014 14:12, schrieb Rich Freeman:
There is snapper, which is even in the tree now. It isn't 100%
flexible but supports any number of hourly, daily, monthly, and yearly
snapshots, with retention policies for each.
no systemd-unitfiles yet, correct? I merged it and took a quick look,
On Tue, May 27, 2014 at 8:58 AM, Stefan G. Weichinger li...@xunil.at wrote:
Am 27.05.2014 14:12, schrieb Rich Freeman:
There is snapper, which is even in the tree now. It isn't 100%
flexible but supports any number of hourly, daily, monthly, and yearly
snapshots, with retention policies for
On Tuesday, May 27, 2014 12:57:58 PM Stefan G. Weichinger wrote:
Am 27.05.2014 09:59, schrieb Neil Bothwick:
So far, btrfs looks good on my laptop - time to think about putting
it on my desktop.
Yeah, good luck with that. I am quite happy with btrfs so far ... no
problems or disadvantages
On Tue, May 27, 2014 at 10:09 AM, J. Roeleveld jo...@antarean.org wrote:
I am still happily using LVM with snapshots. Those are instantaneous as well
and I can then backup the snapshot, which on my server takes between 2 hours
(incremental) and 3 weeks (full)
When a snapshot is backed up, it
I'm working on this btrfs malarkey and have a question about best
practice. It is recommended to leave the root volume empty and create a
subvolume for the root filesystem which is set with btrfs subvolume
set-default, which I have done.
What is the recommended way to create subvolumes that are
Am 22.05.2014 18:12, schrieb Neil Bothwick:
I'm working on this btrfs malarkey and have a question about best
practice. It is recommended to leave the root volume empty and
create a subvolume for the root filesystem which is set with btrfs
subvolume set-default, which I have done.
16 matches
Mail list logo
