From: Jesse Molina <jesse@opendreams.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] trouble adding a disk to exisiting lvm
Date: Wed Jul 9 19:11:01 2003 [thread overview]
Message-ID: <3F0CAEDA.6050007@opendreams.net> (raw)
In-Reply-To: <3F0C9623.8070409@xs4all.nl>
It would be very helpful if you were to include useful information such
as the output that fsck spewed at you, some general data about your LVs
and this troublesome drive, or even a log of the entire event that you
tried if you have it.
Otherwise, you can scan your palm and we can try to read that for you. =)
I like to run something like badblocks, Bonnie++, and smartmontools,
before I trust a new drive. Write a little script, let it run, and see
if it fouls up over a 24-48 hour period. Then you can blame it on
software later if something goes wrong.
Gert van der Knokke wrote:
> Hi,
>
> Probably this is a known problem but anyway as I'm new to the subject of
> LVM I give it a go.
>
> We set up on a server machine an initial LVM consisting of two 80 Gb
> drives dangling on a Promise RAID controller (just using them as
> /dev/hde and /dev/hdg, aka two separate IDE devices, no raid magic
> involved)
> This worked as a charm and the resulting LVM was setup with ext3
> filesystem without a hitch. The LVM was filled with data from other IDE
> devices (source) and when these were copied (they were FAT32 volumes)
> these source drives were emptied and with fdisk the partition table was
> emptied too.
>
> Pvcreate was done on the first drive to be added and after vgscan and
> vgextend an fsck -f was done on the lvm volume before resize2fs was done.
> All this still went without problems, remounting the extended volume
> gave no errors.
>
> The volume was unmounted and the next drive was to be added, same
> procedure (partition table clear with fdisk, pvcreate, vgscan, vgextend)
> but then as fsck was run a huge pile of numbers came up with at the end
> the question fix<y>? And I aborted this by Ctrl-C to keep the
> filesystem as it were.
>
> I guess the adding of the third drive issued this problem, did resize2fs
> foul up ? Is the whole volume at risk ?
>
> Regards,
> Gert
>
>
>
>
>
> _______________________________________________
> 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/
--
# Jesse Molina
# Mail = jesse@opendreams.net
# Page = page-jesse@opendreams.net
# Cell = 1.407.970.0280
# Web = http://www.opendreams.net/jesse/
next prev parent reply other threads:[~2003-07-09 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 17:25 [linux-lvm] trouble adding a disk to exisiting lvm Gert van der Knokke
2003-07-09 19:11 ` Jesse Molina [this message]
2003-07-10 13:39 ` Gert van der Knokke
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=3F0CAEDA.6050007@opendreams.net \
--to=jesse@opendreams.net \
--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.