<?xml version="1.0" encoding="utf-8"?>
<feed version="0.3" xmlns="http://purl.org/atom/ns#">
<link rel="alternate" type="text/html" href="https://gamma.unpythonic.net/"/>

<title>Jeff Epler's blog</title>
<modified>2012-10-14T21:23:15Z</modified>
<tagline>Photos, electronics, cnc, and more</tagline>
<author><name>Jeff Epler</name><email>jepler@unpythonic.net</email></author>
<entry>
<title>lvm + snapshots + uuid = assbitten</title>
<issued>2012-10-14T21:23:15Z</issued>
<modified>2012-10-14T21:23:15Z</modified>
<id>https://gamma.unpythonic.net/01350249795</id>
<link rel="alternate" type="text/html" href="https://gamma.unpythonic.net/01350249795"/>
<content type="text/html" mode="escaped">

Something was strange after a recent reboot—a certain partition didn't seem to have its current contents in it.

&lt;p&gt;I soon discovered that instead of mounting the filesystem, an lvm snapshot of the filesystem was mounted instead

&lt;p&gt;This occurred because I had an fstab line of the form &lt;pre&gt;
UUID=821f....  /store/whatever
&lt;/pre&gt;
and &lt;strong&gt;both the original filesystem and the snapshot have the same UUID&lt;/strong&gt;!

&lt;p&gt;This is perhaps obvious when you think about what an lvm snapshot 
&lt;strong&gt;is&lt;/strong&gt;, but it sure led to an unexpected result!

&lt;p&gt;Lesson: when using lvm, specify mounts using the /dev/pvname/lvname notation
unless you're sure you'll never use snapshots.
</content>
</entry>
<entry>
<title>Linux RAID Misdetection (and fix)</title>
<issued>2011-08-13T17:58:53Z</issued>
<modified>2011-08-13T17:58:53Z</modified>
<id>https://gamma.unpythonic.net/01313258333</id>
<link rel="alternate" type="text/html" href="https://gamma.unpythonic.net/01313258333"/>
<content type="text/html" mode="escaped">
Earlier this year, I began using a setup with LVM inside of a RAID5.
RAID5 gets me 2TB of storage from 3 1TB drives, with redundancy in the
case of the failure of a single disk, while LVM gets me the ability to
allocate and resize individual filesystems at will.  However, I had a
problem that prevented my system from booting unattended, which became
a big problem when there was a storm-related power failure while I
was out of town.</content>
</entry>
</feed>
