No subject

---------------------------------
How low will we go? Check out Yahoo! Messenger’s low  PC-to-Phone call rates.
--0-418219649-1155703315=:57559
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<br><br><b><i>"gLaNDix (Jesse Kaufman)" &lt;glandix at lloydnet.org&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Tom+Dale wrote:<br>&gt; In fact, we had added the SATA drive to the LVM thinking that we <br>&gt; could pvmove the data and then remove the 320GB drive for use in<br>&gt; another box. It was not until we'd added it into the LVM that we<br>&gt; realized you cannot reduce an XFS volume group.<br><br>so you had already "grown" the XFS filesystem to use the entire space in <br>the volume group?  i didn't see that in the original post, so i was <br>assuming you hadn't resized the filesystem yet.  if not, then no data <br>will be on that drive and you can safely remove the physical volume from <br>the volume group.  otherwise, i'm not sure, since i don't have any <br>experience with XFS, just ReiserFS and ext3<br><br>-g-<br></blockquote>Right, I believe that we grown the volume group to
 include the new drive.&nbsp; I did not say that in my first message because LVM is all new to me so I'm not really sure how far we got, technically.&nbsp; Functionally, I know that we gave up before figuring out why MythTV only recognized the original disk space (excluding the new drive).<br><br>As newbies struggling to get a clue in the wee hours of Saturday morning, we adjourned at that point, planning to do more research later.&nbsp; When I checked things Saturday afternoon, I discovered the clicking sound of the new drive and suspected other trouble.<br><br>From the output of pvdisplay, it looks to me like most of the PEs are unavailable which I interpreted to mean that they are part of VolGroup00 and not available for assignment to another group.&nbsp; That's only a guess on my part.&nbsp; I'm hopeful that since MythTV didn't report the added space as available, perhaps no data was written there.&nbsp; More importantly, I'm hopeful that we can substitute an identical
 replacement disk, assign it the UUID from the failed one, and then at least be able to access the data on the original two physical volumes.&nbsp; We'll have to deal with our [larger than planned] logical volume in a separate step.&nbsp; Finally, we'll switch to ReiserFS having learned our lesson.<br><p>&#32;
		<hr size=1>How low will we go? Check out Yahoo! Messenger’s low <a href="http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com"> PC-to-Phone call rates.
--0-418219649-1155703315=:57559--