<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using lvm only on specific drives (Reading all physical volumes.  This may take a while&#8230;)</title>
	<atom:link href="http://ramblings.narrabilis.com/wp/using-lvm-only-on-specific-drives-reading-all-physical-volumes-this-may-take-a-while/feed/" rel="self" type="application/rss+xml" />
	<link>http://ramblings.narrabilis.com/wp/using-lvm-only-on-specific-drives-reading-all-physical-volumes-this-may-take-a-while/</link>
	<description>Scripts, settings, and fixes...</description>
	<lastBuildDate>Fri, 23 Jul 2010 17:37:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: uphill</title>
		<link>http://ramblings.narrabilis.com/wp/using-lvm-only-on-specific-drives-reading-all-physical-volumes-this-may-take-a-while/comment-page-1/#comment-21730</link>
		<dc:creator>uphill</dc:creator>
		<pubDate>Tue, 28 Jul 2009 12:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=157#comment-21730</guid>
		<description>Our systems are RedHat/Fedora/Centos based, the vgscan is issued from the initrd on our distro, so it should be in the initramfs on yours.  This is because the system needs to do the vgscan to find the lvm&#039;s and mount &#039;/&#039; before it can read &#039;/etc/init.d/lvm2&#039;.  On our system the /etc/lvm/lvm.conf is picked up by the call to mkinitrd, I assume something similar will happen on debian (I don&#039;t know much about debian, sorry), maybe check how the system updates itself after a kernel upgrade.</description>
		<content:encoded><![CDATA[<p>Our systems are RedHat/Fedora/Centos based, the vgscan is issued from the initrd on our distro, so it should be in the initramfs on yours.  This is because the system needs to do the vgscan to find the lvm&#8217;s and mount &#8216;/&#8217; before it can read &#8216;/etc/init.d/lvm2&#8242;.  On our system the /etc/lvm/lvm.conf is picked up by the call to mkinitrd, I assume something similar will happen on debian (I don&#8217;t know much about debian, sorry), maybe check how the system updates itself after a kernel upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://ramblings.narrabilis.com/wp/using-lvm-only-on-specific-drives-reading-all-physical-volumes-this-may-take-a-while/comment-page-1/#comment-21722</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 28 Jul 2009 06:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=157#comment-21722</guid>
		<description>Hi!

I am using Debian ... it looks like the vgscan is issued in /etc/init.d/lvm2. Do you have any idea if I also have to update the initramfs?

Alex</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>I am using Debian &#8230; it looks like the vgscan is issued in /etc/init.d/lvm2. Do you have any idea if I also have to update the initramfs?</p>
<p>Alex</p>
]]></content:encoded>
	</item>
</channel>
</rss>
