All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgchange doesn't enable found VGs
Date: Fri, 27 Feb 2009 15:19:45 -0500	[thread overview]
Message-ID: <1235765985.1193.49.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <20090227200000.GF6714@agk.fab.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

On Fri, 2009-02-27 at 20:00 +0000, Alasdair G Kergon wrote:
> On Fri, Feb 27, 2009 at 12:30:30PM -0500, Brian J. Murrell wrote:
> >     cache_dir = "/etc/lvm/cache"
> 
> The cache_dir must be *writeable*.

And persistent or just writable?

Interestingly enough, RHEL5.2's /etc/rwtab (the files and directories
that need to be made "magically" writable -- through bind mounting to
either persistent storage or tmpfs) has:

files   /etc/lvm/.cache

That's starting to look like a type methinks.

> If you're attempting to use read-only root, then move it somewhere else
> (is /var writeable? or make a ramfs) or delete that directory *and*
> change

Ahhh.  "a ramfs".  So persistence is not a requirement it seems.

b.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-27 20:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 15:36 [linux-lvm] vgchange doesn't enable found VGs Brian J. Murrell
2009-02-27 16:29 ` Bryn M. Reeves
2009-02-27 16:38   ` Brian J. Murrell
2009-02-27 17:02     ` Bryn M. Reeves
2009-02-27 17:30       ` Brian J. Murrell
2009-02-27 20:00         ` Alasdair G Kergon
2009-02-27 20:19           ` Brian J. Murrell [this message]
2009-02-27 20:31             ` Brian J. Murrell
2009-02-27 21: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=1235765985.1193.49.camel@pc.interlinx.bc.ca \
    --to=brian@interlinx.bc.ca \
    --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.