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 famil
Or indeed btrfs but the raid stuff in there is not yet complete. #ZFSFTW
On 29 March 2015 at 03:45, Andrew Holway wrote:
> Or ZFS.. http://zfsonlinux.org/
>
> On 29 March 2015 at 03:37, Chris Murphy wrote:
>
>> It's a matter of user space tools preference. Both mdadm, and lvm
>> tools use the L
Or ZFS.. http://zfsonlinux.org/
On 29 March 2015 at 03:37, 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 i
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 c
zep writes:
> > vagrant?
> >
> I'm unfamiliar with vagrant, but it's pretty easy to roll your own.
> email me off list if you'd like a copy of my Frankenstein scripts.
>
I should have provided a link: https://www.vagrantup.com/
vagrant does rather more than just running VM's - automated creat
Johnny Hughes writes:
> For the record ... using the latest Google Chrome on CentOS-7.1503 (our
> 7.1 release in testing right now), allows Netflix to play just fine on
> CentOS-7. What I have installed when I tested it:
>
> nss-3.16.2.3-5.el7.i686
> nss-3.16.2.3-5.el7.x86_64
> google-chrome-st
I am running irqbalance with default configuration on an Atom 330 machine.
This CPU has 2 physical cores + 2 SMT (aka Hyperthreading) cores.
As shown below the interrupt for the eth0 device is always on CPUs 0 and 1,
with CPUs 2 and 3 left idle. But why?
Maybe irqbalance prefers physical co
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
Several questions about the upcoming release:
1. Will this be happening WW14? If not, is there an ETA?
2. We have our next minor release that’s dependent on CentOS7.1. Are there
currently any ISOs available so we can do a risk build? We have an extensive
automation farm and doing manual
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 corrupt
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
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
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ..
13 matches
Mail list logo
