From: Gerry Reno <greno@verizon.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] F7 will not boot after running backup w/snapshot
Date: Thu, 01 May 2008 16:57:23 -0400 [thread overview]
Message-ID: <481A2EB3.40703@verizon.net> (raw)
In-Reply-To: <481A2BB4.7080504@Media-Brokers.com>
Charles Marcus wrote:
> On 5/1/2008 4:36 PM, Gerry Reno wrote:
>> Without knowing the exact cause of the hang there is no way to know
>> if the ramdisk was at issue. I doubt it myself, I ran a whole series
>> of backups last night using the ramdisk snapshot and everything went
>> fine.
>
> Actually, I'm not talking about the hang as much as I am the problem
> you had recovering from it...
>
> My questions is, had the snapshot volume been on a regular hard drive,
> would you have had the same problems recovering from the situation.
>
I don't think anyone could possibly say.
There was corruption involved and that could have occurred for lots of
reasons. My thought is that even if the ramdisk were not present on the
next boot there should be no reason for that to cause corruption. There
were no lvm mods made to the rw snapshot which means in essence it was
read-only. The VG did not mount and nothing wrote to any filesystem on
the VG which means the corruption is probably totally unrelated or is a
bug. LVM should be robust enough to fully recover from this without any
corruption. It just should have discarded the old snapshot. The
original volume should not be affected. But as I said, I suspect there
may be a bug. Probably some scenario is not being handled in the code.
Gerry
next prev parent reply other threads:[~2008-05-01 20:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 0:53 [linux-lvm] F7 will not boot after running backup w/snapshot Gerry Reno
2008-04-30 2:29 ` Gerry Reno
2008-04-30 3:51 ` Gerry Reno
2008-04-30 14:00 ` Gerry Reno
2008-04-30 15:09 ` Larry Dickson
2008-04-30 17:23 ` Gerry Reno
2008-04-30 18:19 ` Gerry Reno
2008-04-30 18:28 ` Charles Marcus
2008-04-30 20:24 ` Gerry Reno
2008-04-30 21:19 ` Milan Broz
2008-04-30 22:30 ` Gerry Reno
2008-05-01 15:48 ` malahal
2008-05-01 16:30 ` Mikulas Patocka
2008-05-01 18:15 ` Gerry Reno
2008-05-01 18:38 ` Charles Marcus
2008-05-01 19:37 ` Gerry Reno
2008-05-01 19:42 ` Charles Marcus
2008-05-01 19:53 ` Gerry Reno
2008-05-01 20:03 ` Charles Marcus
2008-05-01 20:21 ` Gerry Reno
2008-05-01 20:25 ` Alasdair G Kergon
2008-05-01 20:30 ` Gerry Reno
2008-05-01 20:34 ` Charles Marcus
2008-05-01 20:36 ` Gerry Reno
2008-05-01 20:44 ` Charles Marcus
2008-05-01 20:57 ` Gerry Reno [this message]
2008-05-01 21:59 ` Alasdair G Kergon
2008-05-01 22:12 ` Gerry Reno
2008-05-01 23:50 ` Gerry Reno
2008-05-02 0:38 ` Stuart D. Gathman
2008-05-02 0:47 ` Stuart D. Gathman
2008-05-02 2:03 ` Gerry Reno
2008-05-02 8:14 ` Marek Podmaka
2008-05-02 14:00 ` Gerry Reno
2008-05-02 14:14 ` Charles Marcus
2008-05-02 14:25 ` Larry Dickson
2008-05-02 14:45 ` Marek Podmaka
2008-05-02 14:38 ` Stuart D. Gathman
2008-05-02 14:47 ` Bryn M. Reeves
2008-05-02 15:05 ` Marek Podmaka
2008-05-02 15:17 ` Stuart D. Gathman
2008-05-02 15:30 ` Gerry Reno
2008-05-02 15:36 ` Bryn M. Reeves
2008-05-03 2:27 ` Mikulas Patocka
2008-05-04 0:45 ` [linux-lvm] Temporary shapshots Stuart D. Gathman
2008-05-05 14:30 ` Larry Dickson
2008-05-05 14:45 ` Charles Marcus
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=481A2EB3.40703@verizon.net \
--to=greno@verizon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.