From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Every now and then LVM is not recognized - LVM2 on RAID10
Date: Wed, 23 Jul 2008 19:35:14 +0200 [thread overview]
Message-ID: <20080723173514.GC30203@soda.linbit> (raw)
In-Reply-To: <48871F04.9090002@exxs.net>
On Wed, Jul 23, 2008 at 02:07:32PM +0200, exxs.net - matevz sernc-urban wrote:
> Dear LVM-Users,
>
> i am running into a very interesting situation today, that our LVM
> metadata is recognized only sometimes. LVM was running fine for some
> weeks and now from today on running pvscan 10 times one after another i
> get about 4 positive and 6 negative results (its somehow a coincidence
> that LVM is recognized).
>
> * WORKING STATE:
> server$ pvscan
> PV /dev/md2 VG mainvg lvm2 [909.59 GB / 299.59 GB free]
> Total: 1 [909.59 GB] / in use: 1 [909.59 GB] / in no VG: 0 [0 ]
>
> * NOT-WORKING STATE:
> server$ pvscan
> No matching physical volumes found
>
> notice: Same behaviour with vgscan and lvscan.
>
> Our Setup:
> * RAID-10 /dev/md2 on /dev/sd[a-d]5
> cat /proc/mdstat
> Personalities : [raid1] [raid10]
> md2 : active raid10 sdb5[1] sda5[0] sdd5[3] sdc5[2]
> 953778688 blocks 64K chunks 2 far-copies [4/4] [UUUU]
>
> * LVM2 on top of /dev/md2 (no separate lvm partition)
> lvm metadata backup is present and it is exactly the same as backups we
> did months ago
>
> I will attach the lvm2 metadata file to this message (vg name: mainvg)
>
> WORKING STATE:
> server$ pvscan -vv
> Setting global/locking_type to 1
> File-based locking selected.
> Setting global/locking_dir to /var/lock/lvm
> Locking /var/lock/lvm/P_global WB
> Wiping cache of LVM-capable devices
> /dev/sndstat: stat failed: No such file or directory
> Wiping internal VG cache
> Walking through all physical volumes
> /dev/md2: size is 1907557376 sectors
> /dev/md2: lvm2 label detected
> PV /dev/md2 VG mainvg lvm2 [909.59 GB / 299.59 GB free]
> Total: 1 [909.59 GB] / in use: 1 [909.59 GB] / in no VG: 0 [0 ]
> Unlocking /var/lock/lvm/P_global
>
> NOT-WORKING STATE:
> server$ pvscan -vv
> Setting global/locking_type to 1
> File-based locking selected.
> Setting global/locking_dir to /var/lock/lvm
> Locking /var/lock/lvm/P_global WB
> Wiping cache of LVM-capable devices
> /dev/sndstat: stat failed: No such file or directory
> Wiping internal VG cache
> Walking through all physical volumes
> /dev/md2: size is 1907557376 sectors
> /dev/md2: No label detected
> No matching physical volumes found
> Unlocking /var/lock/lvm/P_global
>
>
> Any hints?
>
> Where should it look regarding "/dev/md2: No label detected" vs.
> "/dev/md2: lvm2 label detected"??
>
> It seems like RAID-10 is not sync'ed well maybe? But, mdstat reports all
> disks are up.
just a shot in the dark:
for dev in /dev/sd{a,b,c,d}5; do
md5=$(dd if=$dev iflag=direct bs=1M count=1 | md5sum)
echo "$dev: $md5"
done
echo check > /sys/block/md2/md/sync_action
Lars
next prev parent reply other threads:[~2008-07-23 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 12:07 [linux-lvm] Every now and then LVM is not recognized - LVM2 on RAID10 exxs.net - matevz sernc-urban
2008-07-23 17:35 ` Lars Ellenberg [this message]
2008-07-24 15:36 ` exxs.net - matevz sernc-urban
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=20080723173514.GC30203@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=linux-lvm@redhat.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.