Linux LVM users
 help / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] snapshots and reiserfs
Date: Sat, 10 Apr 2004 16:28:32 +0800	[thread overview]
Message-ID: <1081585711.22388.7.camel@rasputin.localnet> (raw)
In-Reply-To: <20040408181835.GA11818@earth.solarsys.private>

On Fri, 2004-04-09 at 02:18, Mark M. Hoffman wrote:

> kernel: reiserfs: checking transaction log (device 3a:06) ...
> kernel: clm-2076: device is readonly, unable to replay log
> kernel: Replay Failure, unable to mount
> kernel: reiserfs_read_super: unable to initialize journal space

I upgraded my kernel to one provided by the Fedora project ( fedora.us,
not fedora.redhat.com ). This seemed to sort out the problem.

> I have not tried the combination of snapshots & reiserfs with
> earlier RedHat packages so I don't know if this is a regression.

I used to get it on RH8, with both ext3 and reiserfs (though more
commonly with reiserfs). Syncing before taking the snapshot can help,
but the only real fix is a kernel patch that makes sure the disk buffers
are flushed to disk before the snapshot is taken.

> Also, is it necessary that the filesystem be quiescent in order to
> create a snapshot?  I could temporarily remount readonly to create
> the snapshot, but I would like not to have to do that.

That would probably work too, but the VFS lock patch /really/ should do
the trick.

Craig Ringer

  parent reply	other threads:[~2004-04-10  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 18:18 [linux-lvm] snapshots and reiserfs Mark M. Hoffman
2004-04-08 18:57 ` Clint Byrum
2004-04-08 22:48 ` Greg Freemyer
2004-04-10  8:28 ` Craig Ringer [this message]
2004-04-10 18:23   ` Mark M. Hoffman
2004-04-12 12:42     ` Craig Ringer

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=1081585711.22388.7.camel@rasputin.localnet \
    --to=craig@postnewspapers.com.au \
    --cc=linux-lvm@redhat.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