All of lore.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] benefit of lvmetad in simply daily snaps?
Date: Sun, 31 Mar 2013 10:15:33 -0700	[thread overview]
Message-ID: <51586F35.2080606@tlinx.org> (raw)



I was just noticing that there was an lvmetad available in the sources,
but that
my distro doesn't build/include it by default.  I'm wondering what it's
benefits
are.


Besides my system volumes, all my data & backup volumes are on lvm. 
Main thing
I've been using lvm for is to generate daily snapshots then using rsync to
create static snaps/day that I then mount and keep around for about a month.

I mount them in a dated directory under the root such that samba users
on windows
can see 'previous versions' of files that have changed over the past few
days-
month.  It's not designed to be a backup replacement, but more of a desktop
convenience.  With the pruning I end up with about 15 static snaps of my
main samba volume and, of course 1 active snap going, started daily.

So I'm not sure I have that much metadata to keep track of (my script reads
it in nightly in ms, to reconstruct it's view of things so it know what to
expire, where to try recovery from if it got interrupted in the middle of
making a snap copy, and whether or not the snaps need mounting after a
reboot.

So where would a lvmetad fit in or is my case too simple to really benefit?

Just sorta wondering why SuSE doesn't include/build it by default...

Thanks,

                 reply	other threads:[~2013-03-31 17:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51586F35.2080606@tlinx.org \
    --to=lvm@tlinx.org \
    --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 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.