linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <breeves@redhat.com>
To: Martin Wilmes <martin.wilmes@java-cup.de>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Broken hard disk
Date: Fri, 13 Oct 2006 17:33:18 +0100	[thread overview]
Message-ID: <452FBFCE.9030204@redhat.com> (raw)
In-Reply-To: <200610130553.24145.martin.wilmes@java-cup.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Wilmes wrote:
> On Friday, 13. October 2006 00:53, Bryn M. Reeves wrote:
>> You can add move 'v's to increase the verbosity of vgscan to see what
>> it's scanning - do you have any device filters configured in /etc/lvm.conf?
> 
> No filters, everything is commented out (unchanged).
> 
> vgscan -vvv now generates ouput for hda:
> 
> ...
>       /dev/hda1: size is 208782 sectors
>         Closed /dev/hda1
>       /dev/hda1: size is 208782 sectors
>         Opened /dev/hda1 RO O_DIRECT
>         /dev/hda1: block size is 1024 bytes
>         Closed /dev/hda1
>         Using /dev/hda1
>         Opened /dev/hda1 RO O_DIRECT
>         /dev/hda1: block size is 1024 bytes
>       /dev/hda1: No label detected
>         Closed /dev/hda1
>         /dev/loop1: Skipping (sysfs)
>         /dev/cloop1: Skipping: Unrecognised LVM device type 240
> ...

What about hda2? According to your fdisk output, that's the PV on this disk.

Does hda2 appear in /proc/partitions?

>> It'd also be good to see what pvscan shows, for e.g.:
> 
> pvscan -vvv outputs:
> 

Likewise - all I can see here is hda1 - that's a type 0x83 (Linux)
partition, rather than the 0x8e (Linux LVM) partition that we're
interested in here.

Can you put the complete output of vgscan -vvv and pvscan -vvv somewhere
on the web and post the links here?

You can use a pastedump service like http://p.opsat.net/new if you don't
have access to somewhere to host this.

Cheers,

Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFFL7/O6YSQoMYUY94RAmxzAJkBGN5IDouPjSKCk44l8MCuN0XNjQCg2SB5
J7s5pP0VJTRzpLtgRJ5Ylxs=
=MwUj
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-10-13 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 21:50 [linux-lvm] Broken hard disk Martin Wilmes
2006-10-12 22:53 ` Bryn M. Reeves
2006-10-13  3:53   ` Martin Wilmes
2006-10-13 16:33     ` Bryn M. Reeves [this message]
2006-10-13 18:46       ` Martin Wilmes

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=452FBFCE.9030204@redhat.com \
    --to=breeves@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=martin.wilmes@java-cup.de \
    /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).