From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Question on shared storage volumes.
Date: Thu Jul 10 04:32:01 2003 [thread overview]
Message-ID: <20030710113012.C23240@sistina.com> (raw)
In-Reply-To: <3F0D2788.76BB0BCB@in.ibm.com>; from sachinp@in.ibm.com on Thu, Jul 10, 2003 at 02:14:56PM +0530
Sachin,
after M1 died, you should run "vgscan ; vgchange -ay HA_VG" on M2
to activate the VG there.
On Thu, Jul 10, 2003 at 02:14:56PM +0530, Sachin Sant wrote:
> I have a SCSI storage unit shared between two machines M1 and M2. On one
> of the machine M1 i create a volume group HA_VG , create a LV vol1 and
> filesystem using the LV vol1.
>
> --- >vgcreate HA_VG /dev/sdd /dev/sde /dev/sdf
> --- >lvcreate -i 3 -I 8 -L 100 -n vol1 HA_VG
> --- >mkfs /dev/HA_VG/vol1
> --- >mount /dev/HA_VG/vol1 /mnt
>
> Now for some reason machine M1 dies and the VG is not exported. Using
> the second machine M2 if i try to forcefully import the vg , vgimport
> command coredumps.
>
> --- >vgimport -f HA_VG /dev/sdd /dev/sde /dev/sdf
> Segmentation fault
>
> Should vgimport coredump here. I guess this is not the right way to
> recove the VG . [ I can recover the VG on machine M2 using vgscan /
> vgchange -a y HA_VG ]
>
> I believe the problem might be with the following piece of code in
> vgimport.c
>
> strncpy ( vg_name_this,
> pv_this[0]->vg_name,
> strlen ( pv_this[0]->vg_name) - strlen ( EXPORTED));
Right, it shouldn't get there, because the VG wasn't exported.
>
> Here the difference between strlen will be calculated as -1 in the above
> senario.
>
> May be the right way would be just print a error message instead of a
> core dump.
>
> Just let me know your thoughts.
>
> -Sachin
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** 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:[~2003-07-10 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 3:43 [linux-lvm] Question on shared storage volumes Sachin Sant
2003-07-10 4:32 ` Heinz J . 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=20030710113012.C23240@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.