I have an LVM2 RAID5 array running as my tertiary in house backup, it has
been running on old reclamed 1TB drives for a couple of months now. I will
report back if I see any problems.
On Wed, Jan 10, 2024 at 3:40 PM Rich Shepard
wrote:
> On Wed, 10 Jan 2024, Michael Ewan wrote:
>
> > Curious.
On Wed, 10 Jan 2024, Michael Ewan wrote:
Curious. I have never had an LVM2 failure that was not caused by an
underlying hardware issue. Did you try creating a mirrored LV?
Michael,
No.
Rich
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
wrote:
> On Wed, 10 Jan 2024, Michael Ewan wrote:
>
> > This is why I use LVM2 for everything related to mounted driv
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 Volume
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,
Have I missed anything?
Yep. I learned that Slackware does not have e2label, but does have tune2fs.
By trial-and-error I learned that the label name is double quoted so I used
tune2fs -L "label" device-name
and added lables to the two data storage drives in the Probox.
Also learned that wh
