From: "Jesús Guerrero" <i92guboj@terra.es>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Writing a bash script or thinking about it anyway.
Date: Tue, 22 Dec 2009 16:36:48 +0100 [thread overview]
Message-ID: <fd69eae4bb0d33dd3c3190b8105712fc@localhost> (raw)
In-Reply-To: <200912221651.08955.alan.mckinnon@gmail.com>
On Tue, 22 Dec 2009 16:51:08 +0200, Alan McKinnon
<alan.mckinnon@gmail.com>
wrote:
> On Tuesday 22 December 2009 16:21:08 Christian Könitzer wrote:
>> a question to b):
>> Can you tell me a fs that supports snappshots (I'm planing to set up a
>> new server so you can choose a new fs... (now I am using reiserfs)) and
>> maybe how to use it (link)? So if you say "or LSM" does this mean I can
>> achieve this also woth LVM? How?
>> thx...
>
> None of the traditional filesystems (ext2|3, reiser) support snapshots.
> ZFS<
> Btrfs do, possibly ext4 also (the last is a hunch only).
That's basically true. However btrfs is quite experimental still, and I
have no serious experience with ZFS, it kind of turns me back the fact that
it's a FUSE based fs, though it's certainly possible to use it even for a
root system provided that your kernel can load the module at bootup
(initrd), I have no idea if there's any downside. I don't have either any
notice about snapshotting in ext4 (I remember the plan being discussed but
I don't think it has been finally implemented, I'd like to be wrong on this
one though).
> LVM snapshots a volume, not the filesystem on it. So it tracks extents
> that
> have changed, not individual files. For backup purposes though, volume
and
> fs
> snapshots are equivalent.
>
> Snapshots with LVM are easy as pie:
>
> - create a new volume which is a snapshot of an existing one
> - mount the snapshot somewhere
> - copy,backup,etc as you like. The volume is read-only so you can't
break
> it
> - umount snapshot
> - destroy snapshot
>
> The LVM man pages contain a wealth of data, as does Google and the LVM
> documentation at redhat.com
Yep, just googling for something along the lines of "lvm snapshot backup"
should give you enough info to start researching. However, for this to be a
possibility you first need to convert your system to use lvm.
--
Jesús Guerrero
next prev parent reply other threads:[~2009-12-22 15:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 3:22 [gentoo-user] Writing a bash script or thinking about it anyway Dale
2009-12-22 3:53 ` Francisco Ares
2009-12-22 4:16 ` Dale
2009-12-22 4:32 ` Francisco Ares
2009-12-22 5:02 ` Neil Walker
2009-12-22 5:09 ` Dale
2009-12-23 1:45 ` Francisco Ares
2009-12-25 23:21 ` Dale
2009-12-22 10:34 ` Jesús Guerrero
2009-12-22 11:20 ` Christian Könitzer
2009-12-22 12:11 ` Jesús Guerrero
2009-12-22 14:21 ` Christian Könitzer
2009-12-22 14:51 ` Alan McKinnon
2009-12-22 15:36 ` Jesús Guerrero [this message]
2009-12-22 19:01 ` Stroller
2009-12-23 6:58 ` Dirk Heinrichs
2009-12-22 18:56 ` Stroller
2009-12-22 23:25 ` Willie Wong
2009-12-22 11:16 ` Stroller
2009-12-22 23:30 ` Willie Wong
2009-12-22 15:08 ` Ward Poelmans
2009-12-22 15:39 ` Neil Bothwick
2009-12-22 15:57 ` Ward Poelmans
2009-12-23 0:33 ` [gentoo-user] " »Q«
2009-12-25 23:19 ` Dale
2009-12-27 21:09 ` »Q«
2009-12-23 12:29 ` [gentoo-user] " Alex Schuster
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=fd69eae4bb0d33dd3c3190b8105712fc@localhost \
--to=i92guboj@terra.es \
--cc=gentoo-user@lists.gentoo.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