All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Ward <jward@idealcorp.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Avoiding disk changes
Date: Wed, 04 Oct 2006 15:10:18 -0400	[thread overview]
Message-ID: <4524071A.9000007@idealcorp.com> (raw)

Question regarding disk changes for LVMs. Are there any known scenarios 
where the on disk information will change (automatically) after the 
device(s) are detected and probed by the system?

My scenario is, I want to plug my LVM drive(s) into a different machine 
(via external USB) for analysis. I want the drives to remain 100% 
unmodified.

I would like to setup my configuration such that no disk changes will 
occur.  Does anything within the LVM or DM realm modify the on-disk 
metadata under normal circumstances, or if a corrupted/broken LVM scheme 
is detected (partial or bad disk, etc.)?

In an attempt to gain absolute control over the detection and mounting 
process, I've set the global configuration file to test mode:

/etc/lvm/lvm.conf:
...
global {
...
	test = 1
...


After that, once I plug my device in, I set the LVM_SYSTEM_DIR env 
variable to point to my own configuration (because I don't want to 
twiddle with the system-wide one anymore than I have to).

I then use "vgchange --partial -a y" to access the new device, and 
create the /dev nodes.

In my custom lvm.conf (located in the $LVM_SYSTEM_DIR) I've set a few 
paranoid settings, including:

	filter = ... (only accept /dev/sd* devices)
	write_cache_state = 0
	backup = 0
	archive = 0
	locking_type = 0

	Setting test mode in this configuration wasn't allowing me to do the 
vgchange, so I left that off.

Hope this isn't too open ended of a question, short if diving into the 
source code, I've tried to research to what extent LVM might 
automatically twiddle bits on the drive.

Thanks in advance.

             reply	other threads:[~2006-10-04 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 19:10 John Ward [this message]
2006-10-05 10:36 ` [linux-lvm] Avoiding disk changes Fabien Jakimowicz
  -- strict thread matches above, loose matches on Subject: below --
2006-10-05 13:22 John Ward
2006-10-05 17:22 ` David Brown

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=4524071A.9000007@idealcorp.com \
    --to=jward@idealcorp.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.