From: Greg Freemyer <freemyer-ml@NorcrossGroup.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] snapshots and reiserfs
Date: Thu, 08 Apr 2004 18:48:15 -0400 [thread overview]
Message-ID: <1081464495.25994.6.camel@david.internal.NorcrossGroup.com> (raw)
In-Reply-To: <20040408181835.GA11818@earth.solarsys.private>
On Thu, 2004-04-08 at 14:18, Mark M. Hoffman wrote:
> Hello:
>
> Sometimes, but not always, I am unable to mount a snapshot.
> When it fails, I see the following lines in my logs...
>
> 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 am using RedHat 9 with the following stock packages:
>
> kernel-smp-2.4.20-30.9
> lvm-1.0.3-12
> reiserfs-utils-3.6.4-5
>
> I have not tried the combination of snapshots & reiserfs with
> earlier RedHat packages so I don't know if this is a regression.
>
> After some STFW, I thought I might need a "VFS lock" patch.
> However, it looks like this was already included by RedHat...
> in kernel-smp-2.4.20-30.9.src.rpm there is already this patch:
> linux-2.4.18-lvm-VFSlock.patch.
>
> Is there anything else I can try or look at?
>
> 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.
>
> Thanks and regards,
XFS used to have this problem about a year ago.
For xfs the issue was that xfs mount attempted a journal replay even
when the mount was read-only. XFS now skips journal replay on read-only
mounts.
You should ask on a reiserfs list if they skip journal replay on
read-only mounts or not.
Greg
--
Greg Freemyer
next prev parent reply other threads:[~2004-04-08 22:49 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 [this message]
2004-04-10 8:28 ` Craig Ringer
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=1081464495.25994.6.camel@david.internal.NorcrossGroup.com \
--to=freemyer-ml@norcrossgroup.com \
--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