From: Craig Tierney <ctierney@hpti.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Can no longer mount lvm striped volume
Date: Thu May 2 13:50:02 2002 [thread overview]
Message-ID: <20020502124850.B4053@hpti.com> (raw)
In-Reply-To: <Pine.SGI.4.33.0205021333290.5694922-100000@erc2000.erc.wisc.edu>; from jmoser@erc.wisc.edu on Thu, May 02, 2002 at 01:34:40PM -0500
As Homer would say 'Doh!'.
I am still having some other problems, but this error
was fixed by mounting the logical volume and not the
volume group.
Wrong: mount -t ext3 /dev/sdd_vol2 /export/sdd_vol2
Correct: mount -t ext3 /dev/sdd_vol2/lv1 /export/sdd_vol2
I was still having problems with the scan message, but
after I fixed that I didn't run the mounting scripts I
mounted by hand and messed up.
Craig
On Thu, May 02, 2002 at 01:34:40PM -0500, John Moser wrote:
>
> > [root@x06 /root]# mount -t ext3 /dev/sdd_vol2/ /export/sdd_vol2
> > mount: /dev/sdd_vol2/ is not a block device
> >
> > IO nodes have gone down in the past due to
> > power interruptions, but I have never had
> > this catastrophic of a problem. I have 16 volume
> > groups, and 3 or 4 appear to be affected.
>
> Have you tried a simple:
>
> vgchange -a y
>
> ? Similar situation happened to me before, and I just needed to activate
> the volume group.
>
> -John
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Craig Tierney (ctierney@hpti.com)
next prev parent reply other threads:[~2002-05-02 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 13:20 [linux-lvm] Can no longer mount lvm striped volume Craig Tierney
2002-05-02 13:33 ` John Moser
2002-05-02 13:50 ` Craig Tierney [this message]
2002-05-06 5:30 ` Heinz J . Mauelshagen
2002-05-02 14:09 ` Craig Tierney
2002-05-02 14:34 ` Patrick Caulfield
2002-05-02 14:47 ` Craig Tierney
2002-05-02 16:05 ` Craig Tierney
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=20020502124850.B4053@hpti.com \
--to=ctierney@hpti.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.