On Sat, 26 Mar 2011, Mike Snitzer wrote:
In the case of a snapshot, I believe the COW and origin blocks are written
in parallel. Snapshots are slow enough as it is. :-) So it is not
surprising that it loses consistency on power failure.
The cow is completed before the origin is written. In addition, the
snapshot volume offers full support for flush (barriers) to both the
origin and snapshot devices.
Your FUD about inconsistency due to the snapshot implementation needs
to be substantiated with something more than an incoherent guesswork
theory.
That said, anything is possible. But if you want real help you need to
be specific about which kernel you're using. What is your underlying
hardware (and caching mode)? And what it was you were doing at the time
of the power failure (running some FS benchmark? or what?).
Don't need help, just trying to understand the event. So from what you
said, the problem probably stems from the RAID1 resync, which could
make one PV "older" than the other.
LVM is EL5.5 via Centos: lvm2-2.02.56 (really old - yes I know). kernel-2.6.18
(with patches).
As I already said, the production system (on origin) was running a scheduled
database backup, which does involve copying about 2 gigs of data to another
directory on the origin. So the origin was likely heavily writing when
the power (and UPS) failed.
I'll mention again that these are linear LVs on top of md raid1.
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
