[buug] lvm issue
Michael.Paoli at cal.berkeley.edu
Fri Sep 7 06:46:22 PDT 2007
> Have you confirmed that nothing (most notably PIDs) is still using
> any of the LVMs - e.g. nothing using those LVM filesystems (if still
> mounted) or LVM devices (such as a database using a raw LVM device
> file)? If those LVM files are in use, one will likely need to
> terminate those PIDs, or at least have those PIDs no longer using
> those files or filesystems.
Quoting John de la Garza <john at jjdev.com>:
> didn't work
> it got IO errors
> On Aug 31, 2007, at 2:35 PM, Sami Juvonen wrote:
> > vgreduce --removemissing
> > From the man page:
> > Removes all missing physical volumes from the volume group and makes
> > the volume group consistent again.
> > It's a good idea to run this option with --test first to find out
> > what it would remove before running it for real.
> > Any logical volumes and dependent snapshots that were partly on the
> > missing disks get removed completely. This includes those parts
> > that lie on disks that are still present.
> > If your logical volumes spanned several disks including the ones that
> > are lost, you might want to try to salvage data first by activating
> > your logical volumes with --partial as described in
> > lvm (8).
> > On 8/31/07, John de la Garza <john at jjdev.com> wrote:
> >> I had an external device hooked up to my box and it got removed
> >> without first deactivating the lvm volume group.
More information about the buug