Curious. I have never had an LVM2 failure that was not caused by an underlying hardware issue. Did you try creating a mirrored LV?
On Wed, Jan 10, 2024 at 12:37 PM Rich Shepard <[email protected]> wrote: > On Wed, 10 Jan 2024, Michael Ewan wrote: > > > This is why I use LVM2 for everything related to mounted drives and file > > systems. Physical volumes (PV) have a UUID (customizable), but > unnecessary > > in normal use since PV's are contained in Volume Groups (VG) and file > > systems are created on Logical Volumes (LV), both of which have arbitrary > > names, and which are then mounted. LVM2 keeps track of everything for > you, > > and you can even move a set of disks to another Linux box and have > > everything sorted out for you by vgscan. See this article for more > detail, > > > https://medium.com/@michaelewan/the-joy-of-using-the-logical-volume-manager-with-linux-f1768e5413ef > > Michael, > > Originally I had the two backup drives in an LV. But, it kept crashing. I > lost all existing data and I had to re-install and re-initialize each > dirvish bank. That there were 2 hard drives in the LV did not allow me to > restore from the good one to the one that failed. > > After the third time of this issue I disassembled the LV and reformatted > each drive with ext4. Two root crontab scripts run shortly after midnight > each day, one for incremental backups to /media/bkup1 the other to rsync > that to /media/bkup2. In 26 years I've had no issues with ext2, ext3, or > ext4 and my scripts run faithfully. > > Regards, > > Rich >
