All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander Alberink <alberink@stamppot.demon.nl>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Severe problem: data lost while adding a partition
Date: Tue Feb 25 16:43:01 2003	[thread overview]
Message-ID: <3E5BF188.6000207@stamppot.demon.nl> (raw)
In-Reply-To: <264070000.1045520730@[192.168.200.4]>

Hi all,

Thanks for the reply. At the moment I have re-initialized the PV's via 
pvcreate -ff. However, trying to reconstruct a new volume group yields 
me the following output:

# vgcreate -v home /dev/hda[1,4,6,7]
vgcreate -- checking volume group name
vgcreate -- checking volume group directory existence
vgcreate -- locking logical volume manager
vgcreate -- checking volume group "home" existence
vgcreate -- counting all existing volume groups
vgcreate -- reading all physical volume data from disks
vgcreate -- checking if all given physical volumes in command line are new
vgcreate -- checking physical volumes name "/dev/hda1"
vgcreate -- checking physical volumes name "/dev/hda4"
vgcreate -- checking physical volumes name "/dev/hda6"
vgcreate -- checking physical volumes name "/dev/hda7"
vgcreate -- no valid physical volumes in command line
#

So apparently something is not OK. But what can that be? Any pointers 
would be appreciated!

>> I really appreciate your help in this. However, I am rather reluctant to
>> dive in and be hasty in my commands. I really don't want to destroy my
>> data.... As I understand it, pvcreate -ff would re-initialize the
>> physical volume. As I understand it, I will have to add them to a volume
>> group again. But will the filesystem still be intact after that then?
>>
>> Sorry if this sound like a beginner question to you. It very well might
>> be, but I'd rather be careful....
>
>
> Thing to understand is that LVM commands update a small
> header on the phyiscal volume. You can munge the LVM
> portion without touching your data at all. In this case
> the data has no way of knowing that anything happend to
> the LVM portion of life: they live in entirely different
> parts of the disk drive. 


Best regards,

Sander Alberink

  reply	other threads:[~2003-02-25 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-01 18:15 [linux-lvm] Severe problem: data lost while adding a partition Sander Alberink
2003-02-03  4:35 ` Heinz J . Mauelshagen
2003-02-06 15:49   ` Sander Alberink
2003-02-07  8:31     ` Heinz J . Mauelshagen
2003-02-17 16:12       ` Sander Alberink
2003-02-17 16:17         ` Steven Lembark
2003-02-25 16:43           ` Sander Alberink [this message]
2003-03-04 15:07             ` Sander Alberink
  -- strict thread matches above, loose matches on Subject: below --
2003-02-01 18:15 Sander Alberink

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=3E5BF188.6000207@stamppot.demon.nl \
    --to=alberink@stamppot.demon.nl \
    --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.