Linux LVM users
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] [BUG] segmentation fault on snapshot with beta8
Date: Fri, 27 Jul 2001 10:21:32 -0500	[thread overview]
Message-ID: <20010727102132.A4314@sistina.com> (raw)
In-Reply-To: <20010726122738.E052917573@oscar.casa.dyndns.org>; from tomlins@cam.org on Thu, Jul 26, 2001 at 08:27:38AM -0400

[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]

On Thu, Jul 26, 2001 at 08:27:38AM -0400, Ed Tomlinson wrote:
> tob is a wrapper script for afio that can installed from a debian
> package.  The snapshotted fs is reiserfs.  I have the vfs locking
> patch installed along with:
> 
> --------
> diff -Nru a/fs/reiserfs/super.c b/fs/reiserfs/super.c
> --- a/fs/reiserfs/super.c       Sun Apr 29 20:44:38 2001
> +++ b/fs/reiserfs/super.c       Sun Apr 29 20:44:38 2001
> @@ -80,7 +80,7 @@
>      reiserfs_prepare_for_journal(s, SB_BUFFER_WITH_SB(s), 1);
>      journal_mark_dirty(&th, s, SB_BUFFER_WITH_SB (s));
>      reiserfs_block_writes(&th) ;
> -    journal_end(&th, s, 1) ;
> +    journal_end_sync(&th, s, 1) ;
>    }
>    s->s_dirt = dirty;
>    unlock_kernel() ;
> --------

Hmm...trying to reproduce this on 2.4.6...and after applying the lvm 0.9.1
beta8 patch, the linux-2.4.4-VFS-lock patch and the above patch (in that
order), I still get this when trying to create and mount a snapshot:

reiserfs: checking transaction log (device 3a:00) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
reiserfs: checking transaction log (device 3a:01) ...
clm-2076: device is readonly, unable to replay log
Replay Failure, unable to mount
reiserfs_read_super: unable to initialize journal space

Is there some other patch or magic I need to do to get ReiserFS snapshots
working?  I thought the VFS-lock patch was supposed to fix that...

Regards,
-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
Error: Keyboard not attached. Press F1 to continue.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-07-27 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 12:27 [linux-lvm] [BUG] segmentation fault on snapshot with beta8 Ed Tomlinson
2001-07-27 15:21 ` AJ Lewis [this message]
2001-07-27 16:27   ` Ed Tomlinson
2001-07-30 13:35     ` AJ Lewis
2001-07-31 21:09       ` Ed Tomlinson

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=20010727102132.A4314@sistina.com \
    --to=lewis@sistina.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