Discuss January 2017

discuss@lists.centos.org

125 participants
116 discussions

Re: [CentOS] CentOS 7 install on one RAID 1 [not-so-SOLVED]
by Eugene Poole 26 Jan '17

26 Jan '17

First let me say I am not a true expert, but I am experienced. If this machine you purchased was some name brand, you must be speaking about hardware raid, true? If this is true, it normally presents you with what looks like a standard drive (/dev/sda) for every 2 drives configured as raid-1. Also, most name brand servers give you a bootable machine day one. If you are using software raid, you must have configured it yourself. Here is what my custom machine has: 2 - 120 GB SSD 2 - 4 TB spinning drives During my CentOS 7 install is where I performed the software raid-1 configuration. I never do the default partition configuration so here is my setup (used fdisk -l): Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0001d7e8 Device Boot Start End Blocks Id System /dev/sda1 2048 134604799 67301376 fd Linux raid autodetect /dev/sda2 134604800 184752127 25073664 fd Linux raid autodetect /dev/sda3 184752128 233191423 24219648 fd Linux raid autodetect /dev/sda4 233191424 234440703 624640 5 Extended /dev/sda5 * 233195520 234440703 622592 fd Linux raid autodetect Disk /dev/sdb: 120.0 GB, 120034123776 bytes, 234441648 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000085a6 Device Boot Start End Blocks Id System /dev/sdb1 2048 134604799 67301376 fd Linux raid autodetect /dev/sdb2 134604800 184752127 25073664 fd Linux raid autodetect /dev/sdb3 184752128 233191423 24219648 fd Linux raid autodetect /dev/sdb4 233191424 234440703 624640 5 Extended /dev/sdb5 * 233195520 234440703 622592 fd Linux raid autodetect Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes, 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: gpt # Start End Size Type Name 1 2048 1699579903 810.4G Linux RAID 2 1699579904 3399157759 810.4G Linux RAID 3 3399157760 3911510015 244.3G Linux RAID 4 3911510016 5611087871 810.4G Linux RAID Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes, 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk label type: gpt # Start End Size Type Name 1 2048 1699579903 810.4G Linux RAID 2 1699579904 3399157759 810.4G Linux RAID 3 3399157760 3911510015 244.3G Linux RAID 4 3911510016 5611087871 810.4G Linux RAID My df -h display shows me the following: /dev/md126 583M 317M 224M 59% /boot I have basically the definitions using CentOS 6 and CentOS 7 and it's my understanding you must have a /boot device. Also during installation of CentOS 7 when writing the MBR to the MD device (in my case md126) it writes the information to both sda and sdb. With CentOS 6, according to HowToForge there are extra steps required to get the MBR on both sda and sdb. I have not had to replace either of these SSD, but I have had to replace spinning drives on my CentOS 6 machines in the past. Gene On 1/26/2017 7:00 AM, centos-request(a)centos.org wrote: > > No. Brand new machine, pulled it out of the box and racked it. NOTHING on the > internal SSDs. Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No > partitions, nothing. However, when I bring it up, fdisk shows an MBR with no > partitions. I can, however, mount /dev/md127p3 as /mnt/sysimage, and all is there. > > Did I need to make a single partition, on each drive, and then make the RAID 1 > out of *those*? I don't think I need to have /boot not on a RAID. > > mark > > > > ------------------------------ > > -- Eugene Poole Woodstock, Georgia

1 0

CentOS 7 install on one RAID 1
by m.roth＠5-cent.us 26 Jan '17

26 Jan '17

Hi, folks, I'm building a new box, and I want three partitions - /boot, /, and swap, on *one* RAID 1, not three separate partitions. Other than <alt-f2> mdadm..., *is* there any way in the graphical installer to do this? All I see is a way to make three separate partitions. Pointers to links happily accepted. mark, back to googling

9 18

samba rpm deps - with yum downgrade = kind of a mayhem
by lejeczek 26 Jan '17

26 Jan '17

hi guys, gals do you see this: ~]$ yum downgrade samba Resolving Dependencies --> Running transaction check ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-client-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: libwbclient = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 ---> Package samba.x86_64 0:4.4.4-12.el7_3 will be erased --> Running transaction check ---> Package libwbclient.i686 0:4.4.4-9.el7 will be installed ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 ---> Package samba.x86_64 0:4.4.4-12.el7_3 will be erased ---> Package samba-client-libs.i686 0:4.4.4-9.el7 will be installed --> Processing Dependency: samba-common = 4.4.4-9.el7 for package: samba-client-libs-4.4.4-9.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: samba-client-libs-4.4.4 ..and process fails. chained are i686 arch? Is it only us(centos) or redhat's bugzilla should be notified. Samba downgrade used to work I remember. bw. L.

2 4

SELinux file permissions
by Tim Smith 25 Jan '17

25 Jan '17

Hi, I'm trying to grant dovecot the ability to manage its socket within the postfix spool directory. I have added the below to file_contexts.local : /var/spool/postfix/private/dovecot-auth system_u:system_r:dovecot_t:s0 However, running "restorecon -v /var/spool/postfix/private/dovecot-auth" gives me the following error : restorecon: lstat(/var/spool/postfix/private/dovecot-auth) failed: No such file or directory I cannot create the socket file in advance, because dovecot manages it, and if you "touch" the file, dovecot complains. Where am I going wrong ? Thanks ! Tim

4 5

I'm making the change to a new OS
by TE Dukes 24 Jan '17

24 Jan '17

Decided to upgrade to 7.x. It's been a good ride 6.x, but you're living in the past. Everything is backed up, just waiting on my new 4TB HD to arrive for a fresh install. See ya'll on the other side!!

3 4

CentOS dojo in Brussels 3rd Feb
by Karanbir Singh 24 Jan '17

24 Jan '17

hi everyone, just a quick reminder that we only have a few more places available at the CentOS Dojo next week Friday : https://wiki.centos.org/Events/Dojo/Brussels2017 If you are in the area, or able to make it into the area, do come by. regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

CentOS-announce Digest, Vol 143, Issue 10
by centos-announce-request＠centos.org 23 Jan '17

23 Jan '17

1 0

Re: [CentOS] [CentOS-virt] Increase CPU usage on HV after upgrade (7.2 -> 7.3)
by Subscriber 22 Jan '17

22 Jan '17

Hello Sandro, Friday, January 20, 2017, 6:54:02 PM, you wrote: > On Thu, Jan 19, 2017 at 3:40 PM, Subscriber <ml-lists(a)agoris.net.ua> wrote: > Hello Sandro, > Thursday, January 19, 2017, 12:12:25 PM, you wrote: >> Discussed with KVM guys, here's the answer: >> 1% per VM seems to much on idle VM; if the VM is not idle you are >> getting better performance in exchange. For idle VMs the difference >> should be roughly 0.1% per VM. > I compared the graphics load on the CPU before and after the upgrade. > After the upgrade is clearly increased CPU System time load. In all > of this mode and load VM themselves became approximately the same. > Can you share exact version of kvm, libvirt and qemu-kvm / qemu-kvm-ev you're using? kvm_intel In CentOS 7.2.1511: kernel-3.10.0-327.36.3.el7.x86_64 qemu-kvm-1.5.3-105.el7_2.7.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 After upgrade from 7.2.1511 to 7.3.1611: It was (after upgrading to this version, I noticed described in the first report the situation): kernel-3.10.0-514.2.2.el7.x86_64 qemu-kvm-1.5.3-126.el7.x86_64 libvirt-daemon-kvm-2.0.0-10.el7_3.2.x86_64 Now (as of 2017/01/22): kernel-3.10.0-514.6.1.el7.x86_64 qemu-kvm-1.5.3-126.el7_3.3.x86_64 libvirt-daemon-kvm-2.0.0-10.el7_3.4.x86_64 It takes 1-2 days for monitoring, to determine whether the situation has changed since the last update.

1 0

CentOS-announce Digest, Vol 143, Issue 9
by centos-announce-request＠centos.org 22 Jan '17

22 Jan '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2017:0180 Critical CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) 2. CESA-2017:0180 Critical CentOS 7 java-1.8.0-openjdk Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sat, 21 Jan 2017 15:53:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0180 Critical CentOS 6 java-1.8.0-openjdk Security Update Message-ID: <20170121155344.GA61934(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0180 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0180.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e04f0af0db6bf5966115be1c780071d3c25c5bbb91b2293d561a6fa15d1631aa java-1.8.0-openjdk-1.8.0.121-0.b13.el6_8.i686.rpm 864d94e6e625bc5a1c1917d7daadb5cb18d23edbd83a959e81f3e933a96127cc java-1.8.0-openjdk-debug-1.8.0.121-0.b13.el6_8.i686.rpm 14a0f1360afffd36590ddafbc3c85c2070ab29441431a35f424d533d4689e42f java-1.8.0-openjdk-demo-1.8.0.121-0.b13.el6_8.i686.rpm 0b27c5e7c38290daf4b10a3afd8088c2b98d32018dafdbe11fb85cb401ac99a1 java-1.8.0-openjdk-demo-debug-1.8.0.121-0.b13.el6_8.i686.rpm d7ec3be372b0b762035137aa79932ff4adba3113d15ddfc1728469c362d7bea6 java-1.8.0-openjdk-devel-1.8.0.121-0.b13.el6_8.i686.rpm e93b86d265215f0f7eed95889f479881b26436934ea1dcf7bfbb896c37e1579c java-1.8.0-openjdk-devel-debug-1.8.0.121-0.b13.el6_8.i686.rpm e7ec1b932abf317c54744e4053209ab525d129db5c4a55cf5aef2afaf894da3e java-1.8.0-openjdk-headless-1.8.0.121-0.b13.el6_8.i686.rpm ac9e8aeec13ad539b2ce43dda728936102a6dcf3337ec002d5fec1b22cba32b8 java-1.8.0-openjdk-headless-debug-1.8.0.121-0.b13.el6_8.i686.rpm ea03e4503f1d19fc9e07e4cf72abfe77cdca5a9fbf480f7361dbb474f750b724 java-1.8.0-openjdk-javadoc-1.8.0.121-0.b13.el6_8.noarch.rpm d27d67a2828310000afcda45aece8be486a4d07a24917618e2bbb1fd383b31c2 java-1.8.0-openjdk-javadoc-debug-1.8.0.121-0.b13.el6_8.noarch.rpm 156ed32eaf641980040ea33925b5325d89c9eea3d67bfb27835d66aaae5d1c8a java-1.8.0-openjdk-src-1.8.0.121-0.b13.el6_8.i686.rpm 72056b3acfc35e1512d431d170bf0bfb3ec41e014d63a37d44a947a3dd566e63 java-1.8.0-openjdk-src-debug-1.8.0.121-0.b13.el6_8.i686.rpm x86_64: 882720170cdd2b723de69104217ba3bfb6f9a88c1f42b4ab1f71d540974d7aca java-1.8.0-openjdk-1.8.0.121-0.b13.el6_8.x86_64.rpm 226b4196d0aeb6e69c68b79a25c761ff6a68002b8461d67eda8396c945fe7380 java-1.8.0-openjdk-debug-1.8.0.121-0.b13.el6_8.x86_64.rpm 25de4d1e1d3154aa6c96d23d2fe3e8c6b422ebd45e1d8d83f150f63b2b82bb2d java-1.8.0-openjdk-demo-1.8.0.121-0.b13.el6_8.x86_64.rpm 46839bfcaadc731258cf7f0434f0f9f4e3bc3ac869a60196b78f36dbfdd12602 java-1.8.0-openjdk-demo-debug-1.8.0.121-0.b13.el6_8.x86_64.rpm d99419b905892f7a4682cb6727a41b9c4c4a033efa9e78216f6c134b6633ee3b java-1.8.0-openjdk-devel-1.8.0.121-0.b13.el6_8.x86_64.rpm 02f44a59db465a34b851188016ed34f4e7086b5626728e7b3937cb0ad802ba4f java-1.8.0-openjdk-devel-debug-1.8.0.121-0.b13.el6_8.x86_64.rpm db7da24a1dd722fdcb576491fae25fe01c4ac85e19ffb039b0cd7aade82897de java-1.8.0-openjdk-headless-1.8.0.121-0.b13.el6_8.x86_64.rpm 4efccbc0830a05709ffa58a8d7124a52ef58e5c6ed57747fe5c63a0088ffdc4c java-1.8.0-openjdk-headless-debug-1.8.0.121-0.b13.el6_8.x86_64.rpm ea03e4503f1d19fc9e07e4cf72abfe77cdca5a9fbf480f7361dbb474f750b724 java-1.8.0-openjdk-javadoc-1.8.0.121-0.b13.el6_8.noarch.rpm d27d67a2828310000afcda45aece8be486a4d07a24917618e2bbb1fd383b31c2 java-1.8.0-openjdk-javadoc-debug-1.8.0.121-0.b13.el6_8.noarch.rpm 50f40ffa84e6f61c9e8de385618530246b14db4080b20efb43ae38aa3e52ac39 java-1.8.0-openjdk-src-1.8.0.121-0.b13.el6_8.x86_64.rpm b20148d489829fd3236174b32d6057a1d6b3a77cfaccd261825c68ca1952e73e java-1.8.0-openjdk-src-debug-1.8.0.121-0.b13.el6_8.x86_64.rpm Source: 893dd0e503edfbf2bbf0018a0c019bf55d9259a8aef8f3a768832870f7678673 java-1.8.0-openjdk-1.8.0.121-0.b13.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Sat, 21 Jan 2017 15:55:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0180 Critical CentOS 7 java-1.8.0-openjdk Security Update Message-ID: <20170121155544.GA64488(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0180 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0180.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b002bc39803820082dabc431b991958f9397bc317248e981f77530cf8428c717 java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.i686.rpm 460180c36d7248c993ed1c7efd333fe7c9819dc9be1b12208ddd3071c140a55a java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64.rpm e248153a1904ea792d4815c47960c5a73e59abc1c4cf5cec464bd453bc7762e6 java-1.8.0-openjdk-accessibility-1.8.0.121-0.b13.el7_3.x86_64.rpm 5d2c4f7cb529dcd1763a9ae648d447edbc5f07a01c54423a69cb0d140de0c6a6 java-1.8.0-openjdk-accessibility-debug-1.8.0.121-0.b13.el7_3.x86_64.rpm ecba68f71f2cbcb197c41220b648694e847a0437d2b24499a65107dadcdb3510 java-1.8.0-openjdk-debug-1.8.0.121-0.b13.el7_3.i686.rpm a87f43a746f505fc2827afa5ace424006850d07dc2647b79b534281898a5718f java-1.8.0-openjdk-debug-1.8.0.121-0.b13.el7_3.x86_64.rpm 39833c95afbc018e7a91c9a2476cb5055ca32fc2fcc6b60d79408e34b81f8ca1 java-1.8.0-openjdk-demo-1.8.0.121-0.b13.el7_3.x86_64.rpm ca5a4add5dbd60bac513d89e7e915660d31d1b8c4ce7f273990a1f45f387a931 java-1.8.0-openjdk-demo-debug-1.8.0.121-0.b13.el7_3.x86_64.rpm a0c638d96cbbcb3acea1b71f51adc571ff6a09c7c0c8d9cb519e654fce15cd07 java-1.8.0-openjdk-devel-1.8.0.121-0.b13.el7_3.i686.rpm 9e1bb8b701666ff38b321f8b7a152df363bf4f6ea0276f98bd540d151a901278 java-1.8.0-openjdk-devel-1.8.0.121-0.b13.el7_3.x86_64.rpm b9122db5db773a07675bfd042aff7b248ec7f4cdc905b78ce43b2d8fde466b31 java-1.8.0-openjdk-devel-debug-1.8.0.121-0.b13.el7_3.i686.rpm 4acc1c716632d0dc135a0ca0ed2d8de29e5813d62c9ef579bd2783191f254850 java-1.8.0-openjdk-devel-debug-1.8.0.121-0.b13.el7_3.x86_64.rpm 8f92a775f9a1056256baf5b132cbf4a61d12e3db79ae4b33dd7c6da80cd0e82f java-1.8.0-openjdk-headless-1.8.0.121-0.b13.el7_3.i686.rpm 820b3b25e699f6dc0768fee7f8362ea5bf3770046dfdbdfc2d1e7bd6d56946f8 java-1.8.0-openjdk-headless-1.8.0.121-0.b13.el7_3.x86_64.rpm e2e99c6977af60e940b6b6e74a35d744742a2a85cf9a2779c5f141375be2393d java-1.8.0-openjdk-headless-debug-1.8.0.121-0.b13.el7_3.i686.rpm e47d2e31358e70ebc3b83f8f32b986df3c293b465ba46da4c91f05a7c1c8e8cf java-1.8.0-openjdk-headless-debug-1.8.0.121-0.b13.el7_3.x86_64.rpm 77c3b0a2194e7239009c8f68f136e7eeeb2ce4ed287a6d9c52ff01dfc3655718 java-1.8.0-openjdk-javadoc-1.8.0.121-0.b13.el7_3.noarch.rpm f0b418e75b930fb391bbb05021d638e1569d83b85603c49267708adcef8777ed java-1.8.0-openjdk-javadoc-debug-1.8.0.121-0.b13.el7_3.noarch.rpm d06e1bfe81fd73e1c143a5bc22d5ad881794acc186408ba142fefdc3128a151d java-1.8.0-openjdk-javadoc-zip-1.8.0.121-0.b13.el7_3.noarch.rpm c68200d318c1b4c803e2b4822ba74963d955c737397e259f2c32c87127048b45 java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.121-0.b13.el7_3.noarch.rpm 2d57cd90202ef0aa603585c9f5e2e9cba72e1c07aa324de697cc307dd4f17121 java-1.8.0-openjdk-src-1.8.0.121-0.b13.el7_3.x86_64.rpm e99b31852e84ff9e81784d68a53204b4f6168f0fde26f209c0eb56c41755e6ae java-1.8.0-openjdk-src-debug-1.8.0.121-0.b13.el7_3.x86_64.rpm Source: 6df0ee7bf1488263efafcc84765297e4b970ad8f1ca5291ae90f2d43536ec7f3 java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 143, Issue 9 ***********************************************

1 0

CentOS 7 and Areca ARC-1883I SAS controller: JBOD or not to JBOD?
by Peter Peltonen 22 Jan '17

22 Jan '17

Hi, Does anyone have experiences about ARC-1883I SAS controller with CentOS7? I am planning to have RAID1 setup and I am wondering if I should use the controller's RAID functionality which has 2GB cache or should I go with JBOD + Linux software RAID? The disks I am going to use are 6TB Seagate Enterprise ST6000NM0034 7200rpm SAS/12Gbit 128 MB If hardware RAID is preferred, the controller's cache could be updated to 4GB and I wonder how much performance gain this would give me? Thanks! Peter

8 14

← Newer
1
2
3
4
5
6
7
...
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2017