Linux LVM users
 help / color / mirror / Atom feed
From: Kenny Gorman <kenny@kenamea.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Continued error with snapshots (unable to init journal)
Date: Wed Dec 12 16:25:02 2001	[thread overview]
Message-ID: <3C17D4D2.5020204@kenamea.com> (raw)

I posted before, but since I have upgraded my SuSE 2.4.7-64GB system to 
include reiserfs-3.x.0k_pre9-43 and lvm-1.0.0.2_rc2-27.  I am still 
getting the below error in /var/log/messages every once in a while 
during mount of the snapshot volume.

Does anyone know what this is about?

Dec 11 18:20:02 ino kernel: reiserfs: checking transaction log (device 
3a:01) ...
Dec 11 18:20:02 ino kernel: clm-2076: device is readonly, unable to 
replay log
Dec 11 18:20:02 ino kernel: Replay Failure, unable to mount
Dec 11 18:20:02 ino kernel: reiserfs_read_super: unable to initialize 
journal space

Thanks,
Kenny Gorman
DBA
Kenamea

             reply	other threads:[~2001-12-12 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 16:25 Kenny Gorman [this message]
2001-12-13  2:22 ` [linux-lvm] Continued error with snapshots (unable to init journal) Patrick Caulfield

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=3C17D4D2.5020204@kenamea.com \
    --to=kenny@kenamea.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