linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Christian Lahti <clahti@gmail.com>
Subject: Re: [linux-lvm] Fwd: file-based locking initialization failed after pvresize
Date: Fri, 31 May 2013 10:23:27 +0200	[thread overview]
Message-ID: <51A85DFF.6050406@redhat.com> (raw)
In-Reply-To: <CAEh524ZaPCWidwO6n8RukzDVBpWw9ENAu=X5gLysV-AopYRQag@mail.gmail.com>

Dne 31.5.2013 05:37, Christian Lahti napsal(a):
> Sorry forgot to copy the list.
>
> ---------- Forwarded message ----------
> From: *Christian Lahti* <clahti@gmail.com <mailto:clahti@gmail.com>>
> Date: Thu, May 30, 2013 at 8:36 PM
> Subject: Re: [linux-lvm] file-based locking initialization failed after pvresize
> To: matthew patton <pattonme@yahoo.com <mailto:pattonme@yahoo.com>>
>
>
> Thank you for your reply, I realize that I must have done something rather
> bone-headed and I am usually pretty clued.  That being said I am still in the
> same pickle I was in to begin with, something constructive would be
> fantastically appreciated.  If there were proper documentation *anywhere*
> google-able I would not have bothered the mailing list.  I am pretty sure the
> data must be in tact since this was done in single user mode and no writes to
> the disk/volume have occurred since the two commands were run, I have /etc/lvm
> in tact with information prior to and after the event.  If someone would be so
> kind as to please let me know exactly what information they might need, I will
> do my level best with minimum "back and forth" to provide such information to
> get out of said pickle.  And I furthermore promise not to do it again.

I'm mostly convinced you've probably already made some irreparable damage to 
your disk data - since the story is usually - Data are intact - I've done only 
this and that :) - but anyway it's probably better trying to resolve this 
interactively on #lvm irc channel.

The easiest way is to restore to the previous version of your metadata,
just before you've started your pvresize command  (which must have been loudly 
objecting to your command line options)

Also next time - when the tool is giving you WARNINGS - and you have no idea,
what it means - it's not a sign to go forward, but to STOP immediately...

Regards

Zdenek

  reply	other threads:[~2013-05-31  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 18:48 [linux-lvm] file-based locking initialization failed after pvresize Christian Lahti
2013-05-30 21:02 ` Christian Lahti
     [not found]   ` <1369952053.99499.YahooMailClassic@web181504.mail.ne1.yahoo.com>
     [not found]     ` <CAEh524ZjZRizYoEimXg0OsLxz2kD8HLu2bqw2V2RbjYKdggVxw@mail.gmail.com>
2013-05-31  3:37       ` [linux-lvm] Fwd: " Christian Lahti
2013-05-31  8:23         ` Zdenek Kabelac [this message]
2013-05-31  9:04         ` Gabriel Barazer
2013-05-31 15:42           ` Zdenek Kabelac
     [not found]   ` <CAKPhfZMihQUFpeG=Tv_8pLwedw4Ugbf9u0jUP=5PTXfbUQHVaQ@mail.gmail.com>
     [not found]     ` <CAKPhfZMctTqczVBVxzdqL__=uYsOCKzkKD1dLj1zj4Z_0ZoW0g@mail.gmail.com>
     [not found]       ` <CAKPhfZPiD3Dux_Z_DGpNz0hyi1sJTXexwbstPe=WdjMGGh4Hog@mail.gmail.com>
2013-05-31 11:45         ` [linux-lvm] " service hofman
2013-05-31 17:20 ` Christian Lahti

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=51A85DFF.6050406@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=clahti@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).