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: Wed, 30 Apr 2008 13:23:40 -0400 [thread overview]
Message-ID: <4818AB1C.9030809@verizon.net> (raw)
In-Reply-To: <1c748a490804300809s304f7fdfx55aeb0fd9c6cc7ab@mail.gmail.com>
Larry,
There was only maybe ten minutes between the time the backup finished
and the hang. The system was very quiet at the time. The backups run
overnight when there is almost no system activity. I had only recently
begun using snapshots and I was surprised to see a machine get into this
state while running a backup w/snapshot. I use a 256M ramdisk as the
snapshot vol. Prior to introducing snapshots this machine had run
without any problems during backups. I could not tell what exactly
caused the hang. There was no indication that the snapshot had run out
of space and I doubt that it did. The issue for me is that no matter
what happened to cause a hang that LVM should never get into a state
where it cannot start the system. The backup had completed backing up
the root filesystem (which was last) when the hang occurred. What that
did was to leave the volume that contained the root filesystem in an
inconsistent state at reboot since the snapshot logvol was not removed.
LVM should have recognized that the inconsistency was due to a snapshot
logvol and corrected the problem at boot and brought up the VolGroup
sans snapshot device since it's worthless at that point anyway. My
concern is that there is a bug somewhere in the snapshot mechanism.
I've seen other people report what they said were corruption problems
resulting from snapshots.
Regards,
Gerry
Larry Dickson wrote:
> Gerry, for the benefit of the rest of us who are depending on snapshot -
>
> Was there much writing and/or reading going on between the time your
> backup was made, and the time of the hang?
>
> I know that snapshot works by putting an extra load on every write to
> the origin volume. Is there any reason, known to knowledgeable LVM
> designers on this list, why this should lead to "hundreds of errors"
> when a system hang takes place? I assume stuff got caught in a
> half-committed state, but _hundreds_... ???
>
> Thanks,
>
> Larry
>
next prev parent reply other threads:[~2008-04-30 17:24 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 [this message]
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
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=4818AB1C.9030809@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.