From: "Harald Heigl" <Harald_Heigl@gmx.at>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] What happens with full snapshots
Date: Sat, 13 Feb 2010 08:13:16 +0100 [thread overview]
Message-ID: <002f01caac7c$03ceb100$0b6c1300$@at> (raw)
In-Reply-To: <1266002536.24951.1@raydesk1.bettercgi.com>
> > But I also think about trying this:
> > http://linuxsoftware.co.nz/blog/2008/03/11/lvm-snapshot-with-no-free-
> diskspa
> > ce
> > Do you see any problems here (besides that this snapshot will be
> > definitely
> > lost)? As said the "real changed data" will be on the disk, just the
> > snapshot is lost ...
>
> That's an interesting idea, to use ramdisk to hold the
> snapshot while taking a backup if no disk space is available....
Perhaps I give it a try, vgcfgrestore should do the trick or reactivating
the ramdisk should do it too. Without it the extended vg isn't complete that
seems logical to me. Depending on the type of data you will need a
rescuesystem, but I hold an pxeboot "rescuecd" on my router, so this is no
great problem.
> It seems that vgcfgbackup is for creating backups and lvmdump
> is for diagnostic purposes. However, lvm automatically creates
> backups before and after every change (by default?). See:
I looked throught the lvm.conf and also the respecting man page:
archive - Whether or not tools automatically archive existing
metadata into archive_dir before making changes to it.
backup - Whether or not tools make an automatic backup into
backup_dir after changing metadata.
So for my fedora the default is 10 archives (minimum 30 days), archive and
backup activated.
So before a change an archive of the metadata seems to go into
/etc/lvm/archive and after the change new metadata goes into /etc/lvm/backup
A vgcfgbackup saves the files in /etc/lvm/backup too, if no parameter is
given.
So It seems a backup of /etc (what I just do regularly) should be fine.
> Note - I am not an LVM developer or expert.
No problem, I use lvm just normal since fedora 8 (must be two years or so)
and never had a problem, did some little resizes of lv before, but nothing
more. Did understand the general concept of lvm but for know I wanted to dig
somehow deeper and explore all the possibilities I have. Doing also
sometimes weird stuff :-), not only with lvm. An extensive user like you is
just welcome. I think I have to do a little more tests. Thanks again.
prev parent reply other threads:[~2010-02-13 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 14:56 [linux-lvm] What happens with full snapshots Harald Heigl
2010-02-12 15:37 ` Ray Morris
2010-02-12 16:41 ` Harald Heigl
2010-02-12 19:22 ` Ray Morris
2010-02-13 7:13 ` Harald Heigl [this message]
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='002f01caac7c$03ceb100$0b6c1300$@at' \
--to=harald_heigl@gmx.at \
--cc=linux-lvm@redhat.com \
/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).