From: Heinz Mauelshagen <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM metadata corruption?
Date: Thu, 28 Jun 2001 11:04:17 -0500 [thread overview]
Message-ID: <20010628110417.B24904@sistina.com> (raw)
In-Reply-To: <20010628022307.A380@vestdata.no>; from lvm@ragnark.vestdata.no on Thu, Jun 28, 2001 at 02:23:07AM +0200
On Thu, Jun 28, 2001 at 02:23:07AM +0200, Ragnar Kj?rstad wrote:
> Hi
>
> We had a LVM problem that we believe was caused by corrupted
> LVM-metadata. Can anyone confirm if this is a likely explanation?
>
> 1. Installed LVM
> 2. Created a single vg on a single device with a single lv
> 3. Used without problems for a while
> 4. Added a new device
> 5. Add the device to the vg, extend the lv and the filesystem
> 6. We experienced scsi-problems at this time.
> 7. Fixed scsi termination
>
> After a reboot, mounting the filesystem(xfs) oopsed.
>
> lvdisplay -v segfaulted, but there was no backtrace.
>
> We recreated the lvm vg and lv, and the filesytem - everything worked
> fine.
>
>
> My theory is that the vgextend or lvextend corrupted the lvm-metadata
> because of the scsi-termination problem. LVM doesn't update the metadata
> using a transactional log, does it?
Ragnar,
no it doesn't so far.
That's a planned enhgancement for post 1.0.
> so if a write failed, the data will
> become corrupted? (yes, I know a copy is saved in the /etc/lvm files)
Yep, but this corruption could only take place, because the hardware
wasn't able to spot the data corruption.
With that kind of silent data corruption even transaction oriented models
will have problems while aiming to make nonatomic I/Os behave atomic.
They can't garantee either that no silent data corruption took place.
In order to avoid such trouble after changing the SCSI HW configurations you
could to write data to free areas on the disks and verify it multiple times
while imposing read load to the disks.
SCSI is pushable over the edge far too easy :-(
Regards,
Heinz -- The LVM Guy --
>
> Unfortenately we needed the system back online right away, so the
> metadata is no gone. No way of debugging it futher.
>
>
> Thank you.
>
>
>
> --
> Ragnar Kjorstad
> Big Storage
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-06-28 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 0:23 [linux-lvm] LVM metadata corruption? Ragnar Kjørstad
2001-06-28 0:41 ` Ragnar Kjørstad
2001-06-28 16:04 ` Heinz Mauelshagen [this message]
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=20010628110417.B24904@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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.