From: xake@rymdraket.net
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm, config and commandline
Date: Thu, 27 Jan 2011 10:37:17 +0100 [thread overview]
Message-ID: <061e0b45500b99a3f38b4bfa88a9a591.squirrel@webmail.rymdraket.net> (raw)
I have a system with a script at bootup currently running something like
"lvm pvscan && lvm vgscan && lvm vgchange -ay" all with the option
"--config 'global { locking_dir = "/dev/.lvm" }'" since when the script
runs /var/lock is not in a writeable state. --ignorelockingfailures is
fine, but gives a message on stderr I do not want, but I still want to get
other error messages so "2>/dev/null" is not an option.
I realized however that if I run this as a script using lvm as interpreter
(running lvm once and the commands inside of lvm) I cut the time for this
script in half.
But with that I have the following problem:
# echo "pvscan --config 'global { locking_dir = "/dev/.lvm" }'" | lvm
/dev/stdin
lvm> pvscan --config 'global { locking_dir = /dev/.lvm }'
Parse error at byte 1 (line 1): unexpected token
Failed to set overridden configuration entries.
I want this:
# lvm pvscan --config 'global { locking_dir = "/dev/.lvm" }'
PV /dev/sde1 VG lillen-home lvm2 [698,63 GiB / 0 free]
PV /dev/md126p1 VG lillen lvm2 [596,18 GiB / 27,18 GiB free]
Total: 2 [1,26 TiB] / in use: 2 [1,26 TiB] / in no VG: 0 [0 ]
So how do I pass --config inside of lvm and still have it able to parse it?
Also, would it not also make sens to have --config an option working
directly on lvm (something like "lvm --config "something" <command>)?
next reply other threads:[~2011-01-27 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 9:37 xake [this message]
2011-01-27 16:24 ` [linux-lvm] lvm, config and commandline Milan Broz
2011-01-27 17:55 ` xake
2011-01-27 21:34 ` Milan Broz
2011-01-28 8:53 ` Peter Hjalmarsson
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=061e0b45500b99a3f38b4bfa88a9a591.squirrel@webmail.rymdraket.net \
--to=xake@rymdraket.net \
--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.