Linux LVM users
 help / color / mirror / Atom feed
From: "Sean Oh" <oh@storageone.co.kr>
To: linux-lvm@sistina.com
Subject: [linux-lvm] [Q] LVM snapshot volume extendable?
Date: Sun Jan 12 06:11:02 2003	[thread overview]
Message-ID: <010901c2ba33$d3e5daf0$0f00a8c0@COMPAQ> (raw)

Hi

I am using LVM 1.0.6, kernel 2.4.20 and XFS (from linux-2.4-xfs CVS).

My question is that is the snapshot volume extendable?

My environment is as follows:

/dev/vg01/lv01 ---> XFS, 2G
/dev/vg01/lv01_snap --> 256M, snapshot for /dev/vg01/lv01, mounted under
/snap with ro,nouuid,usrquota,grpquota,noatime

Now I have wrote a small shell scripts that if lv01_snap is more than 50%
full, automatically increase the lv01_snap. But it seems to me that it does
not work well..

What I did in the shell scripts are 'lvextend -L+256M /dev/vg01/lv01_snap'
with/without 'xfs_growfs /snap'.

After umounting the /snap and trying to remount /snap, it complaints as
below

XFS: recovery required required on read-only device
XFS: write access unavailabe, cannot proceed
XFS: log mount/recovery failed
XFS: log mount failed
mount: wrong fs type, bad option, bad superblock on /dev/vg01/lv01,
       or too many mounted file systems
       (aren't you trying to mount an extended partition,
       instead of some logical partition inside?)

BTW, extending the original lv01 works fine with lvextend and xfs_growfs.

Could someone please help?

Thanks in advance

             reply	other threads:[~2003-01-12  6:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12  6:11 Sean Oh [this message]
2003-01-12  7:09 ` [linux-lvm] [Q] LVM snapshot volume extendable? Alasdair G Kergon
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='010901c2ba33$d3e5daf0$0f00a8c0@COMPAQ' \
    --to=oh@storageone.co.kr \
    --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