From: Joe Harvell <joe.harvell@tekcomms.com>
To: linux-lvm@redhat.com
Cc: matthew patton <pattonme@yahoo.com>
Subject: Re: [linux-lvm] pvs complains of missing PVs that are not missing
Date: Wed, 9 Oct 2013 18:04:20 -0500 [thread overview]
Message-ID: <5255E0F4.7000205@tekcomms.com> (raw)
In-Reply-To: <1381356552.67129.YahooMailNeo@web181504.mail.ne1.yahoo.com>
Le 09/10/2013 17:09, matthew patton a �crit :
> clear LVM's cache (or just disable it in lvm.conf), rescan pv, vg, lv. make sure udev is creating the necessary hooks.
>
I'm not sure how to disable the cache. Here are my relevant settings in
/etc/lvm/lvm.conf:
# If set, the cache of block device nodes with all associated symlinks
# will be constructed out of the existing udev database content.
# This avoids using and opening any inapplicable non-block devices or
# subdirectories found in the device directory. This setting is applied
# to udev-managed device directory only, other directories will be
scanned
# fully. LVM2 needs to be compiled with udev support for this
setting to
# take effect. N.B. Any device node or symlink not managed by udev in
# udev directory will be ignored with this setting on.
obtain_device_list_from_udev = 1
# The results of the filtering are cached on disk to avoid
# rescanning dud devices (which can take a very long time).
# By default this cache is stored in the /etc/lvm/cache directory
# in a file called '.cache'.
# It is safe to delete the contents: the tools regenerate it.
# (The old setting 'cache' is still respected if neither of
# these new ones is present.)
# N.B. If obtain_device_list_from_udev is set to 1 the list of
# devices is instead obtained from udev and any existing .cache
# file is removed.
cache_dir = "/etc/lvm/cache"
cache_file_prefix = ""
# You can turn off writing this cache file by setting this to 0.
write_cache_state = 1
And as expected based on my setting for obtain_device_list_from_udev,
there is no /etc/lvm/cache directorypresent:
joey@akita ~ $ sudo nano -w /etc/lvm/lvm.conf
Mot de passe :
joey@akita ~ $ ls -al /etc/lvm/
total 68
drwxr-xr-x 5 root root 4096 7 oct. 14:12 .
drwxr-xr-x 74 root root 4096 9 oct. 11:21 ..
drwx------ 2 root root 4096 8 oct. 22:21 archive
drwx------ 2 root root 4096 8 oct. 22:21 backup
-rw-r--r-- 1 root root 45697 9 oct. 17:27 lvm.conf
drwxr-xr-x 2 root root 4096 8 oct. 19:24 profile
next prev parent reply other threads:[~2013-10-09 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 21:29 [linux-lvm] pvs complains of missing PVs that are not missing Joe Harvell
2013-10-09 21:49 ` Joe Harvell
[not found] ` <1381356552.67129.YahooMailNeo@web181504.mail.ne1.yahoo.com>
2013-10-09 23:04 ` Joe Harvell [this message]
[not found] ` <5255D815.1090704@tekcomms.com>
[not found] ` <1381361455.80237.YahooMailNeo@web181502.mail.ne1.yahoo.com>
2013-10-10 15:04 ` Joe Harvell
2013-10-10 18:38 ` Peter Rajnoha
2013-10-10 18:48 ` Peter Rajnoha
2013-10-10 19:48 ` Joe Harvell
-- strict thread matches above, loose matches on Subject: below --
2013-10-23 4:26 Shi Jin
2013-10-23 16:43 ` Joe Harvell
2013-10-24 9:35 ` Zdenek Kabelac
2013-10-24 15:30 ` Joe Harvell
2013-10-24 16:26 ` Alasdair G Kergon
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=5255E0F4.7000205@tekcomms.com \
--to=joe.harvell@tekcomms.com \
--cc=linux-lvm@redhat.com \
--cc=pattonme@yahoo.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.