Hi all!
I've recently noticed that recent versions of LVM include RAID capabilities, so that one could presumably implement (e.g.) RAID-1 without having to use Linux Software RAID.
Given the complexity of LBM, I'm wondering how practical and how safe this is (compared to Linux Software RAID), and also if anyone here knows more about it than I do (which isn't much), and especially if anyone here has actually used it??
I'd appreciate any feedback from y'all! :)
Thanks, Fred.
On Sat, Mar 28, 2015 at 08:48:52AM -0400, Fred Smith wrote:
Hi all!
I've recently noticed that recent versions of LVM include RAID capabilities, so that one could presumably implement (e.g.) RAID-1 without having to use Linux Software RAID.
Given the complexity of LBM, I'm wondering how practical and how safe
oops: LVM
this is (compared to Linux Software RAID), and also if anyone here knows more about it than I do (which isn't much), and especially if anyone here has actually used it??
I'd appreciate any feedback from y'all! :)
Thanks, Fred.
Hi,
in Cent OS 7
after a power on, I experienced multiple errors
in the device-mapper mirror: device lookup error and EXT4-fs error_lookup 1437 deleted inode reference
I assume these are the VMs
Is this always going to happen when I reboot the system?
Will I experience data loss or corruption from this?
Best,
Stephen
On 3/28/2015 7:51 AM, Stephen wrote:
in Cent OS 7
after a power on, I experienced multiple errors
in the device-mapper mirror: device lookup error and EXT4-fs error_lookup 1437 deleted inode reference
does this have anything to do with Fred Smith's question about Using LVM to implement RAID ??
please start a new thread for a new topic, with an appropriate subject, don't reply to an unrelated post.
It's a matter of user space tools preference. Both mdadm, and lvm tools use the Linux md driver code to implement RAID on the backend; but have completely different user facing tools and on-disk metadata. So it's best to be familiar with the troubleshooting and recovery process for each more than create, because that's where people get into trouble the most with both sets of tools. This thread might help:
https://www.centos.org/forums/viewtopic.php?f=47&t=51349
Or ZFS.. http://zfsonlinux.org/
On 29 March 2015 at 03:37, Chris Murphy lists@colorremedies.com wrote:
It's a matter of user space tools preference. Both mdadm, and lvm tools use the Linux md driver code to implement RAID on the backend; but have completely different user facing tools and on-disk metadata. So it's best to be familiar with the troubleshooting and recovery process for each more than create, because that's where people get into trouble the most with both sets of tools. This thread might help:
https://www.centos.org/forums/viewtopic.php?f=47&t=51349
-- Chris Murphy _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Or indeed btrfs but the raid stuff in there is not yet complete. #ZFSFTW
On 29 March 2015 at 03:45, Andrew Holway andrew.holway@gmail.com wrote:
Or ZFS.. http://zfsonlinux.org/
On 29 March 2015 at 03:37, Chris Murphy lists@colorremedies.com wrote:
It's a matter of user space tools preference. Both mdadm, and lvm tools use the Linux md driver code to implement RAID on the backend; but have completely different user facing tools and on-disk metadata. So it's best to be familiar with the troubleshooting and recovery process for each more than create, because that's where people get into trouble the most with both sets of tools. This thread might help:
https://www.centos.org/forums/viewtopic.php?f=47&t=51349
-- Chris Murphy _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, Mar 28, 2015 at 07:37:41PM -0600, Chris Murphy wrote:
It's a matter of user space tools preference. Both mdadm, and lvm tools use the Linux md driver code to implement RAID on the backend; but have completely different user facing tools and on-disk metadata. So it's best to be familiar with the troubleshooting and recovery process for each more than create, because that's where people get into trouble the most with both sets of tools. This thread might help:
Thanks Chris, that looks like good info.
-
Andrew Holway -
Chris Murphy -
Fred Smith -
John R Pierce -
Stephen