linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: Chris Mason <mason@suse.com>, reiserfs-list@namesys.com
Cc: linux-lvm@sistina.com
Subject: [linux-lvm] Re: [reiserfs-list] mounting reiserfs snapshot fails
Date: Mon, 30 Apr 2001 00:31:29 -0400	[thread overview]
Message-ID: <01043000312901.00694@oscar> (raw)
In-Reply-To: <01043000231400.00694@oscar>

On Monday 30 April 2001 00:23, Ed Tomlinson wrote:

> > The bug is that reiserfs needs to try harder to wait for the current
> > transaction to end.  A slight change in the semantics there didn't get
> > carried into the reiserfs write_super_lockfs call (reiserfs_block_writes
> > used to be enough on its own).
> >
> > But, it only hits when LVM can create the snapshot faster than the next
> > reiserfs writer can commit the transaction, which doesn't happen often
> > for me.
>
> This is not fixing the problem here.  What else do you need to figure this
> one out?  I did verify that I built from souce with both the fix VFS
> locking the the reiserfs fix applied.  Symptoms remain the same,
> debugreiserfs is still finding a null block where it expects the sb.

Some more info.  

If I use: lvcreate -L1G -s -n snap /dev/lv/root /dev/hdg1
the snapshoot is corrupt

if I use: lvcreate -L1G -s -n snap /dev/lv/root /dev/hde1
the snapshoot works

The difference being that /dev/lv/root is on /dev/hde1.  hdg1 is basicly
empty right now.  Suspect there is still race in this process.

Ed

  reply	other threads:[~2001-04-30  4:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-13 17:29 [linux-lvm] mounting reiserfs snapshot fails Ed Tomlinson
2001-04-13 20:36 ` Chris Mason
2001-04-13 22:42   ` Ed Tomlinson
2001-04-14  0:23 ` Andreas Dilger
2001-04-14  0:53   ` [reiserfs-list] " Chris Mason
2001-04-18  1:38     ` Ed Tomlinson
2001-04-30  1:48 ` [linux-lvm] Re: [reiserfs-list] " Chris Mason
2001-04-30  4:23   ` Ed Tomlinson
2001-04-30  4:31     ` Ed Tomlinson [this message]
2001-04-30 11:43     ` Chris Mason

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=01043000312901.00694@oscar \
    --to=tomlins@cam.org \
    --cc=linux-lvm@sistina.com \
    --cc=mason@suse.com \
    --cc=reiserfs-list@namesys.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;
as well as URLs for NNTP newsgroup(s).