From: Heinz J. Mauelshagen <Heinz.Mauelshagen@t-online.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM 2.2 snapshot bug
Date: Tue, 7 Nov 2000 12:16:00 +0000 [thread overview]
Message-ID: <20001107121600.A18914@srv.t-online.de> (raw)
In-Reply-To: <Pine.LNX.4.05.10011071151180.21541-100000@humbolt.nl.linux.org>; from riel@conectiva.com.br on Tue, Nov 07, 2000 at 11:55:42AM +0100
Hi Rik,
this is already fixed in the LVM 0.9 source.
Thanks,
Heinz -- The LVM guy --
On Tue, Nov 07, 2000 at 11:55:42AM +0100, Rik van Riel wrote:
> Hi,
>
> I think I found an {easy to fix, very annoying} bug in the
> 2.2.<ver>aa derived kernel LVM drivers (which, most likely,
> is also in Heinz' drivers).
>
> On snapshot creation, the snapshot block device (/dev/vg0/snap1)
> is NOT made a read-only device, so ext3 tries to do journal
> recovery when the snapshot device is mounted...
>
> (leading to all kinds of nasty oopses)
>
> It should be easy enough to do an set_device_ro() on the LVM
> snapshot, shouldn't it?
Yes, that's what i do in 0.9.
>
> That would fix the oopses I've been seeing and would make
> the snapshot "more useful" ... I hope a fix will be available
> soon since I want to use this feature for NL.linux.org :)
I'll take care of that.
>
> regards,
>
> Rik
> --
> The Internet is not a network of computers. It is a network
> of people. That is its real strength.
>
> http://www.conectiva.com/ http://www.surriel.com/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Bartningstr. 12
64289 Darmstadt
Germany
Mauelshagen@Sistina.com +49 6151 7103 86
FAX 7103 96
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2000-11-07 12:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 10:55 [linux-lvm] LVM 2.2 snapshot bug Rik van Riel
2000-11-07 12:16 ` Heinz J. Mauelshagen [this message]
2000-11-07 14:42 ` Rik van Riel
2000-11-07 13:21 ` [linux-lvm] " Andrea Arcangeli
2000-11-07 14:56 ` Rik van Riel
2000-11-07 16:45 ` Andrea Arcangeli
2000-11-07 17:04 ` Stephen C. Tweedie
2000-11-07 19:51 ` Andrea Arcangeli
2000-11-07 20:36 ` Andreas Dilger
2000-11-08 11:11 ` Stephen C. Tweedie
2000-11-08 16:16 ` Andrea Arcangeli
2000-11-08 19:08 ` Andreas Dilger
2000-11-08 11:10 ` Stephen C. Tweedie
2000-11-08 16:53 ` Andrea Arcangeli
2000-11-07 23:04 ` Rik van Riel
2000-11-08 7:55 ` Heinz Mauelshagen
2000-11-08 13:44 ` Rik van Riel
2000-11-08 16:31 ` Andrea Arcangeli
[not found] ` <898720000.973701988@coffee>
2000-11-08 17:04 ` Andrea Arcangeli
2000-11-08 19:11 ` Andreas Dilger
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=20001107121600.A18914@srv.t-online.de \
--to=heinz.mauelshagen@t-online.de \
--cc=Mauelshagen@sistina.com \
--cc=linux-lvm@msede.com \
--cc=riel@conectiva.com.br \
/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).