Re: [CentOS] Was, Re: raid 5 install, is ZFS
On Jul 1, 2019, at 9:44 AM, mark wrote: > > it was on Ubuntu, but that shouldn't make a difference, I would think Indeed not. It’s been years since the OS you were using implied a large set of OS-specific ZFS features. There are still differences among the implementations, but the number of those is getting smaller as the community converges on ZoL as the common base. Over time, the biggest difference among ZFS implementations will be time-based: a ZFS pool created in 2016 will have fewer feature flags than one created in 2019, so the 2019 pool won’t import on older OSes. > I pulled one drive, to simulate a drive failure, and it > rebuilt with the hot spare. Then I pushed the drive I'd pulled back in... > and it does not look like I've got a hot spare. zpool status shows > config: I think you’re expecting more than ZFS tries to deliver here. Although it’s filesystem + RAID + volume manager, it doesn’t also include storage device management features. If you need this kind of thing to just happen automagically, you probably want to configure zed: https://zfsonlinux.org/manpages/0.8.0/man8/zed.8.html But, if you can spare human cycles to deal with it, you don’t need zed. What’s happened here is that you didn’t tell ZFS that the disk is no longer part of the pool, so that when it came back, ZFS says, “Hey, I recognize that disk! It belonged to me once. It must be mine again.” But then it goes and tries to fit it into the pool and finds that there are no gaps to stick it into. So, one option is to remove that replaced disk from the pool, then reinsert it as the new hot spare: $ sudo zpool remove export1 sdb $ sudo zpool add export1 spare sdb The first command removes the ZFS header info from the disk, and the second puts it back on, marking it as a spare. Alternately, you can relieve your prior hot spare (sdl) from its new duty — “new sdb” — putting sdb back in its prior place: $ sudo zpool replace export1 sdl sdb That does a full resilver of the replacement disk, a cost you already paid for with the hot spare failover, but it does have the advantage of keeping the disks in alphabetical order by /dev name, as you’d probably expect. But, rather than get exercised about whether putting sdl between sda and sdc makes sense, I’d strongly encourage you to get away from raw /dev/sd? names. The fastest path in your setup to logical device names is: $ sudo zpool export export1 $ sudo zpool import -d /dev/disk/by-serial export1 All of the raw /dev/sd? names will change to /dev/disk/by-serial/* names, which I find to be the most convenient form for determining which disk is which when swapping out failed disks. It doesn’t take a very smart set of remote “hands” at a site to read serial numbers off of disks to determine which is the faulted disk. The main problem with that scheme is that pulling disks to read their labels works best with the pool exported. If you want to be able to do device replacement with the pool online, you need some way to associate particular disks with their placement in the server’s drive bays. To get there, you’d have to be using GPT-partitioned disks. ZFS normally does that these days, creating one big partition that’s optimally-aligned, which you can then label with gdisk’s “c” command. Having done that, then you can do “zfs import -d /dev/disk/by-partlabel” instead, which gets you the logical disk naming scheme I’ve spoken of twice in the other thread. If you must use whole-disk vdevs, then I’d at least write the last few digits of each drive’s serial number on the drive cage or the end of the drive itself, so you can just tell the tech “remove the one marked ab212”. Note by the way that all of this happened because you reintroduced a ZFS-labeled disk into the pool. That normally doesn’t happen. Normally, a replacment is a brand new disk, without any ZFS labeling on it, so you’d jump straight to the “zpool add” step. The prior hot spare took over, so now you’re just giving the pool a hot spare again. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] How to restore the old network interface name?
Hallo, I need the device eth0 for one tool using centos 7.6. Using this tutorial https://www.certdepot.net/rhel7-restore-old-network-interface-name/ doesn t work. Thanks for a hint. Ralf ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 173, Issue 1
Send CentOS-announce mailing list submissions to
centos-annou...@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-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@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-2019:1603 Critical CentOS 7 firefox Security Update
(Johnny Hughes)
2. CESA-2019:1626 Important CentOS 7 thunderbird Security Update
(Johnny Hughes)
3. CEEA-2019:1612 CentOS 7 microcode_ctl Enhancement Update
(Johnny Hughes)
4. CESA-2019:1619 Important CentOS 7 vim SecurityUpdate
(Johnny Hughes)
5. CESA-2019:1604 Critical CentOS 6 firefox Security Update
(Johnny Hughes)
6. CESA-2019:1624 Important CentOS 6 thunderbird Security Update
(Johnny Hughes)
--
Message: 1
Date: Mon, 1 Jul 2019 15:53:24 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2019:1603 Critical CentOS 7 firefox
SecurityUpdate
Message-ID: <20190701155324.ga30...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2019:1603 Critical
Upstream details at : https://access.redhat.com/errata/RHSA-2019:1603
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
08d2604423c6a69b2a32c0356784acc9e0f21cb277a7f78da828e8367f5d9c72
firefox-60.7.2-1.el7.centos.i686.rpm
2e7d25bb455d5c0474656115c3fb6864f1887988b78e7697f69e2a77d5be5da0
firefox-60.7.2-1.el7.centos.x86_64.rpm
Source:
59bb4421beed2b74a7df4222f7c9decf996914c8b0731f1b175900a5dbe2bd2b
firefox-60.7.2-1.el7.centos.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 2
Date: Mon, 1 Jul 2019 15:54:02 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2019:1626 Important CentOS 7
thunderbird Security Update
Message-ID: <20190701155402.ga30...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2019:1626 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2019:1626
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
3def848ee0e2f0c98b8c94eeddaf6768e3385c1b69ff751ff7205a1613f1ddf4
thunderbird-60.7.2-2.el7.centos.x86_64.rpm
Source:
48f315bc83bbaf08dd7b2e7a413760bea001b471499e5200b4e42ebfaa19e1f9
thunderbird-60.7.2-2.el7.centos.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 3
Date: Mon, 1 Jul 2019 15:54:45 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEEA-2019:1612 CentOS 7 microcode_ctl
Enhancement Update
Message-ID: <20190701155445.ga31...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Enhancement Advisory 2019:1612
Upstream details at : https://access.redhat.com/errata/RHEA-2019:1612
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
fdc9dc05c868dd21990e27415fc46ba47907c308a2ac721e090674f79270ad25
microcode_ctl-2.1-47.5.el7_6.x86_64.rpm
Source:
7ccb912f8c7a6fd6e59732c364877856e9b8d8b93166597d597d88452cb2c902
microcode_ctl-2.1-47.5.el7_6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 4
Date: Mon, 1 Jul 2019 15:55:11 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2019:1619 Important CentOS 7 vim
SecurityUpdate
Message-ID: <20190701155511.ga31...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2019:1619 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2019:1619
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
afcc9e1a04ec14de245e51c4e6dd12e437d957e25a781d608b722736270c2a04
vim-common-7.4.160-6.el7_6.x86_64.rpm
a72bf35b8146ccfc708da2c074c5201553eb147194f6067fe0c69a24b53d2155
vim-enhanced-7.4.160-6.el7_6.x86_64.rpm
9be5f369745afc73c69050c226b286b0ae460634e1f612a7fa1d035d4bb4b1fa
vim-filesystem-7.4.160-6.el7_6.x86_64.rpm
6f12c145f92c8a73fca7d0a34877325b6d258cc246d39edb5b726a7229ca9240
vim-min
Re: [CentOS] How to restore the old network interface name?
On Tue, Jul 02, 2019 at 11:56:03AM +0200, Ralf Prengel wrote: > I need the device eth0 for one tool using centos 7.6. > Using this tutorial > https://www.certdepot.net/rhel7-restore-old-network-interface-name/ doesn t > work. This Red Hat documentation explains how the naming works: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-understanding_the_device_renaming_procedure You don't need to set kernel parameters to set the interface name. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Anyone with RedHat Subscription?
Does Anyone with a RedHat subscription able to give a hint as to what the solution to the following knowledgebase article is: https://access.redhat.com/solutions/2801051 I'm having a similar issue with an SFP on a Centos host, and am searching for a way to view Optical RX/TX Power on the SFP. From the switch side, I'm not seeing any RX Power from the Centos host. Thanks in advance Giles ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anyone with RedHat Subscription?
This is kinda of why it makes sense to purchase at least one license. I would start with a loop back test on both ends. Dirty ports happen. Did you grab the most recent version of ethtool and build it? > -Original Message- > From: CentOS On Behalf Of Giles Coochey > Sent: Tuesday, July 2, 2019 9:19 AM > To: CentOS mailing list > Subject: [CentOS] Anyone with RedHat Subscription? > > Does Anyone with a RedHat subscription able to give a hint as to what > the solution to the following knowledgebase article is: > > https://access.redhat.com/solutions/2801051 > > I'm having a similar issue with an SFP on a Centos host, and am > searching for a way to view Optical RX/TX Power on the SFP. > > From the switch side, I'm not seeing any RX Power from the Centos host. > > Thanks in advance > > Giles > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anyone with RedHat Subscription?
Their "resolution" is: Update to RHEL 7 to get the more recent ethtool output format. You should be able to build a newer ethtool from source (or depending on your NIC manufacturer, they may supply a tool with more recent features. Solarflare, for example, provides 'sfctool', basically new ethtool features for old kernels). Thanks, Scott On Tue, Jul 2, 2019 at 8:19 AM Giles Coochey wrote: > Does Anyone with a RedHat subscription able to give a hint as to what > the solution to the following knowledgebase article is: > > https://access.redhat.com/solutions/2801051 > > I'm having a similar issue with an SFP on a Centos host, and am > searching for a way to view Optical RX/TX Power on the SFP. > > From the switch side, I'm not seeing any RX Power from the Centos host. > > Thanks in advance > > Giles > > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- DISCLAIMER: NOTICE REGARDING PRIVACY AND CONFIDENTIALITY The information contained in and/or accompanying this communication is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this information, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy of any e-mail and any printout thereof. Electronic transmissions cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. Simplex Trading, LLC and its affiliates reserves the right to intercept, monitor, and retain electronic communications to and from its system as permitted by law. Simplex Trading, LLC is a registered Broker Dealer with CBOE and a Member of SIPC. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anyone with RedHat Subscription?
On 02/07/2019 14:35, Scott Silverman wrote: Their "resolution" is: Update to RHEL 7 to get the more recent ethtool output format. You should be able to build a newer ethtool from source (or depending on your NIC manufacturer, they may supply a tool with more recent features. Solarflare, for example, provides 'sfctool', basically new ethtool features for old kernels). I was a bit economical with the situation in full in my original post. This system is using third-party repo's, i.e. neither Centos / RedHat, although it is clearly based on Centos. The repo's do not have any development tool-chains, so we would have to put together another system, build ethtool on that, create an rpm and then invalidate the third-parties warranty by installing it on the production system. I think we'll just boot into diagnostic mode and see what we can discern from there. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anyone with RedHat Subscription?
On 02/07/2019 14:28, Jason Pyeron wrote: This is kinda of why it makes sense to purchase at least one license. I would start with a loop back test on both ends. Dirty ports happen. Did you grab the most recent version of ethtool and build it? OK, so this is a third party product that is built on Centos/RHEL, the product provider does not allow us to install/modify stuff. So we're stuck with the tools on the system and cannot make/build modifications on it, so in fact we have no Centos nor RedHat in this environment, so I was just curious to hear upstream's view on what a possible solution might be. We have a plan to do many things as part of the diagnosis, but I'm currently performing an information gathering exercise to discern the other of our future steps. I have received an answer to my query that the optical RX/TX inforrmation is only available on RHEL 7 and not on RHEL 6. We will therefore look to boot this host into diagnostic mode for further troubleshooting. -Original Message- From: CentOS On Behalf Of Giles Coochey Sent: Tuesday, July 2, 2019 9:19 AM To: CentOS mailing list Subject: [CentOS] Anyone with RedHat Subscription? Does Anyone with a RedHat subscription able to give a hint as to what the solution to the following knowledgebase article is: https://access.redhat.com/solutions/2801051 I'm having a similar issue with an SFP on a Centos host, and am searching for a way to view Optical RX/TX Power on the SFP. From the switch side, I'm not seeing any RX Power from the Centos host. Thanks in advance Giles ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anyone with RedHat Subscription?
On 7/2/19 6:18 AM, Giles Coochey wrote: Does Anyone with a RedHat subscription able to give a hint as to what the solution to the following knowledgebase article is: https://access.redhat.com/solutions/2801051 You only need a Red Hat account, not subscription. I can read it after logging in my Red Hat account, and I have no subscription of any product. With a free Red Hat account you can also get free RHEL for development purposes (do read the terms). -- Elliot ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anyone with RedHat Subscription?
On Tue, Jul 2, 2019 at 8:28 AM Jason Pyeron wrote: > This is kinda of why it makes sense to purchase at least one license. > Red Hat does now offer free developer subscriptions which includes access to the Red hat Customer Portal. You officially need a business or enterprise email address, which I verified when they rejected my personal gmail address the first time. It recommended that I change it to a business or enterprise one, but instead I just used a gmail supported + alias ( me+red...@gmail.com ), which Red hat accepted. ( https://gmail.googleblog.com/2008/03/2-hidden-ways-to-get-more-from-your.html ) It's very worthwhile to have a Red Hat Dev Subscription so you can try newer releases before they get released downstream by CentOS and others, and also to get access to otherwise hidden subscriber content. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] How to restore the old network interface name?
Might look into 70-persistent-net.rules in addition to the article below (do
your web research for that and CentOS 7), it's a file you probably have to
create (not necessarily auto-generated as some documentation says) under
/etc/udev/rules.d. There have been two known formats for that file and a given
format doesn't work in all cases. Here are the formats I've seen, hope it
helps (everything below is literal except what's contained in the less/greater
than delimiters):
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="",
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME=""
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="",
ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME=""
Note the missing KERNEL==... in the latter form.
From: CentOS on behalf of Ralf Prengel
Sent: Tuesday, July 2, 2019 4:56 AM
To: CentOS mailing list
Subject: [EXTERNAL] [CentOS] How to restore the old network interface name?
Hallo,
I need the device eth0 for one tool using centos 7.6.
Using this tutorial
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.certdepot.net%2frhel7-restore-old-network-interface-name%2f&c=E,1,_N-6Ga7-RXX-iwhg9-7842nyxrBXlZ3jmvPHUhIYBoIRbfi51krljOSNJKWZlazwotUW4gPX0NsSZ6l6Sjdtdaba3SAt1YES6sfHIll53M2YxmPjTrrb98aASA,,&typo=1
doesn t work.
Thanks for a hint.
Ralf
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Harriscomputer
Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
[cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com
This message has been sent on behalf of a company that is part of the Harris
Operating Group of Constellation Software Inc. These companies are listed
here
[CentOS] using RedHat binary packages?
Hi folks, AFAIK CentOS uses RedHat's source RPMs for building the next CentOS release. I am not sure about the bootstrap procedure and the infra- structure packages, so lets put these corner cases aside. RedHat's "regular" binary and source packages are based on open source (GPL2, GPL3, Apache license, whatever). For building the binary RPMs other open source RPMs with compatible license conditions are used. My question is: Are RedHat's binary RPMs "poisoned" somehow, making it impossible for CentOS to redistribute RedHat's *binary* packages without going to jail? Every insightful comment is highly appreciated. Regards Harri ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
