From: Alasdair G Kergon <agk@uk.sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] [Q] LVM snapshot volume extendable?
Date: Sun Jan 12 07:09:01 2003 [thread overview]
Message-ID: <20030112130953.A13785@uk.sistina.com> (raw)
In-Reply-To: <010901c2ba33$d3e5daf0$0f00a8c0@COMPAQ>; from oh@storageone.co.kr on Sun, Jan 12, 2003 at 09:12:07PM +0900
On Sun, Jan 12, 2003 at 09:12:07PM +0900, Sean Oh wrote:
> What I did in the shell scripts are 'lvextend -L+256M /dev/vg01/lv01_snap'
> with/without 'xfs_growfs /snap'.
The snapshot volume does not hold a filesystem - it is just a storage
area for deltas that enable the system to reconstruct a filesystem.
So you don't need to run xfs utilities on it to make more space. [But
of course some people might want to run them on writeable snapshots
(needs kernel patch) for testing the effect of utilities.]
Alasdair
--
agk@uk.sistina.com
next prev parent reply other threads:[~2003-01-12 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 6:11 [linux-lvm] [Q] LVM snapshot volume extendable? Sean Oh
2003-01-12 7:09 ` Alasdair G Kergon [this message]
2003-01-12 7:09 ` jon+lvm
2003-01-12 7:29 ` Sean Oh
2003-01-12 11:16 ` jon+lvm
2003-01-12 22:37 ` Sean Oh
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=20030112130953.A13785@uk.sistina.com \
--to=agk@uk.sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox