Something was strange after a recent reboot—a certain partition didn't seem to have its current contents in it.
I soon discovered that instead of mounting the filesystem, an lvm snapshot of the filesystem was mounted instead
This occurred because I had an fstab line of the form
UUID=821f.... /store/whateverand both the original filesystem and the snapshot have the same UUID!
This is perhaps obvious when you think about what an lvm snapshot is, but it sure led to an unexpected result!
Lesson: when using lvm, specify mounts using the /dev/pvname/lvname notation unless you're sure you'll never use snapshots.
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.
All older entries
Website Copyright © 2004-2021 Jeff Epler