All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Automatic snapshot system?
Date: Thu Nov 29 15:16:02 2001	[thread overview]
Message-ID: <ufa1yihs2cc.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: Petro's message of "Thu, 29 Nov 2001 13:00:07 -0800"

>>>>> "p" == petro  <petro@auctionwatch.com> writes:

p> Well, I won't get into the debate on whether it's better to
p> protect the users or educate them (ie easy to access backups make
p> users sloppy kind of argument),

Uh, well, I've been an administrator for 13 years and a computer user
for 24, and I still accidentally overwrite a file or delete a
directory on occasion.  And when this happens, I don't particularly
want to have to mess with the tape drive.  The the LVM system already
includes a method for making snapshots; why not make use of it?
Educating users doesn't really come into it.

p> Establish a cron-job to run at <work-start-time>, <work-start+4>
p> and <work-end>. This cron job calls a script that expires the old
p> snap and creates a new one.

Well, I understand how to do it.  I was simply asking if anyone had
already done it so I can save myself some work.  (It's actually mildly
complicated.  You have to parse various /proc files to get the LVM
state and figure out which snapshots you have active and whether any
of them have filled and thus become unusable.  You also have to update
/etc/fstab so a reboot doesn't lose your snapshots.)

 - J<

  reply	other threads:[~2001-11-29 15:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29  1:07 [linux-lvm] Automatic snapshot system? Jason L Tibbitts III
2001-11-29  2:46 ` Petro
2001-11-29 14:41   ` Jason L Tibbitts III
2001-11-29 14:58     ` Petro
2001-11-29 15:16       ` Jason L Tibbitts III [this message]
2001-11-30  2:53     ` Joe Thornber
2001-11-30  9:11       ` Jason L Tibbitts III
2001-12-03  8:18         ` Heinz J . Mauelshagen

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=ufa1yihs2cc.fsf@epithumia.math.uh.edu \
    --to=tibbs@math.uh.edu \
    --cc=linux-lvm@sistina.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.