All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Ph. Marek" <marek@bmlv.gv.at>
Cc: ext3-users@redhat.com, linux-lvm@sistina.com
Subject: [linux-lvm] Re: ext3 on an logical volume - snapshot using how?
Date: Mon Apr  8 10:02:02 2002	[thread overview]
Message-ID: <20020408160246.H9970@redhat.com> (raw)
In-Reply-To: <3.0.6.32.20020408155317.0090b210@pop3.bmlv.gv.at>; from marek@bmlv.gv.at on Mon, Apr 08, 2002 at 03:53:17PM +0200

Hi,

On Mon, Apr 08, 2002 at 03:53:17PM +0200, Ph. Marek wrote:
 
> I'm using LVM and ext3 and am very satisfied with it.
> 
> But now I have the following problem:
> I have a filesystem on a LV which is in use -
> files are created, modified and so on.
> To do a backup I'd like to create a snapshot
> of this volume which gets backup'd  and then dropped.

> 	mount: wrong fs type, bad option, bad superblock on /dev/vg/snapshot,
> 	       or too many mounted file systems
> 	> EXT3-fs: INFO: recovery required on readonly filesystem.
> 	> EXT3-fs: write access unavailable, cannot proceed.

> If the snapshot wasn't ro I'd do a tune2fs or e2fsck or something.

There is a "VFS-lock" patch distributed with the LVM sources, which
adds code to LVM to tell filesystems to quiesce themselves for a
snapshot.  This results in a filesystem which can be mounted safely
without recovery.

Ext3 already supports this functionality, but the LVM code in the main
kernel does not have the code to call it.  The VFS-lock patch adds
that code.

Cheers,
 Stephen

  reply	other threads:[~2002-04-08 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08  8:49 [linux-lvm] ext3 on an logical volume - snapshot using how? Ph. Marek
2002-04-08 10:02 ` Stephen C. Tweedie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08  9:21 [linux-lvm] " Rechenberg, Andrew

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=20020408160246.H9970@redhat.com \
    --to=sct@redhat.com \
    --cc=ext3-users@redhat.com \
    --cc=linux-lvm@sistina.com \
    --cc=marek@bmlv.gv.at \
    /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.