All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshot questions
Date: Fri Nov  2 16:39:01 2001	[thread overview]
Message-ID: <20011102153947.P746@lynx.no> (raw)
In-Reply-To: <0111021341411E.08803@khayes-lin>; from khayes@quicknet.net on Fri, Nov 02, 2001 at 01:41:41PM -0800

On Nov 02, 2001  13:41 -0800, Kyle Hayes wrote:
> I am confused by the claim (see below) that you need the same amount
> of space for the snapshot partition as you had on the original LV.

They are wrong.

> Under what circumstances do snapshots work?  I am confused by the
> claims that a snapshot partition is going to be "corrupt" as far as
> the OS is concerned.

You need to ensure that the the data/filesystem is "synced" at the
time that you create the snapshot.  With journaling filesystems,
you need to use the VFS locking.  With other filesystems, you
should be OK with a "sync" (which is done for you in the kernel).
For oracle, you need to put your tablespaces into hot backup mode.

> 1) lock all tables against writes.

Is this the same as hot backup?  At a company I used to work for, we
did live backups without any kind of outage.  Oracle would commit
the writes into a journal (or whatever, don't know the correct term)
and then commit them once the table was out of hot backup mode.  No
need to lock all writes.

Depending on your I/O and response requirements, you can do the backups
while your tables are in hot backup mode, without using snapshots at
all.  

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

  reply	other threads:[~2001-11-02 16:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D880FFC9CFDBA84FA13E9B166D06A123B647FB@daedalus.kenamea.co m>
2001-11-02 13:59 ` [linux-lvm] snapshot questions Brent Harding
2001-11-02 15:40   ` Kyle Hayes
2001-11-02 16:39     ` Andreas Dilger [this message]
2001-11-02 18:20       ` Kyle Hayes
2001-11-05  4:38         ` Jesus Manuel NAVARRO LOPEZ
2001-11-05 10:50           ` Kyle Hayes
2001-11-05 14:21             ` Andreas Dilger
2001-11-05  4:15     ` Jesus Manuel NAVARRO LOPEZ
2007-05-06  5:32 [linux-lvm] Snapshot questions Ed Martin
  -- strict thread matches above, loose matches on Subject: below --
2001-11-02 17:49 [linux-lvm] snapshot questions Kenny Gorman
2001-11-05 10:31 ` Jesus Manuel NAVARRO LOPEZ
2001-11-02 15:58 Kenny Gorman
2001-11-02 17:04 ` Kyle Hayes
2001-11-02 13:16 Kenny Gorman
2001-11-05  3:27 ` Jesus Manuel NAVARRO LOPEZ
2001-11-02 10:42 Kyle Hayes
2001-11-02 11:28 ` Andreas Dilger
2001-11-02 12:51 ` Jesus Manuel NAVARRO LOPEZ

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=20011102153947.P746@lynx.no \
    --to=adilger@turbolabs.com \
    --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.