linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Anselm Kruis <A.Kruis@science-computing.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshot safetynet?
Date: Tue Feb 19 02:36:02 2002	[thread overview]
Message-ID: <Pine.LNX.4.02.10202190931010.14840-100000@murnau.science-computing.de> (raw)
In-Reply-To: <NBBBKLKHMJHIJLHOGAOJIEOHJEAA.steve.wray@paradise.net.nz>

On Tue, 19 Feb 2002, Steve Wray wrote:

> Ok, heres a thought;
> Resizing filesystems is a risky operation,
> by and large, especially shrinking them.
> 
> So I had the thought;
> Take a snapshot of the filesystem to shrink,
> use fs tools and lvm tools to shrink it,
> if it goes wrong, restore the snapshot!

I'vd done something similar. I use a patch to enable writes on snapshots.
Once I had to shrink a root filesytem on LVM. I created an writeable
snapshot, rebooted with the snapshot as root filesystem. Thisway the real 
root fs wasn't mounted and I could shrink it without problems.

> 
> Will it work tho? I'm wondering it lvreduce
> will get confused about the snapshot or if
> the snapshot system will cope with such a huge
> change...
No problem. But I use a patched LVM to allow writeable snapshots.

> 
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> 

---
 Anselm Kruis                                 Tel. +49 (0)89-356386-74
 science + computing ag		              FAX  +49 (0)89-356386-37
 Ingolstädter Str. 22             mailto: A.Kruis@science-computing.de
 D-80807 München                 WWW: http://www.science-computing.de/

**********************************************************************
***     CeBIT 2002                                                 ***
***     Besuchen Sie uns auf der CeBIT vom 13.-20.03.2002          ***
***     auf dem Messegelände in Hannover, Halle 11                 ***
**********************************************************************

  reply	other threads:[~2002-02-19  2:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18 18:34 [linux-lvm] RH7.2 + kernel 2.4.17(or 16) + LVM 1.0.2 Chris Rutledge
2002-02-18 18:52 ` Anders Widman
2002-02-18 19:18   ` [OT]: " Kirby C. Bohling
2002-02-18 19:43     ` [linux-lvm] snapshot safetynet? Steve Wray
2002-02-19  2:36       ` Anselm Kruis [this message]
2002-02-18 22:26     ` [OT]: Re: [linux-lvm] RH7.2 + kernel 2.4.17(or 16) + LVM 1.0.2 Benjamin Scott

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=Pine.LNX.4.02.10202190931010.14840-100000@murnau.science-computing.de \
    --to=a.kruis@science-computing.de \
    --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 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).