Re: [CentOS] Question regarding cent OS 7.8.2003 compatibility with large SAS disks
On Thu, Sep 24, 2020 at 9:26 PM Amey Abhyankar wrote: > Hello, > > I have a blade server with SAS HDD's of 12TB in total. > 3 HDD's of 4TB each. > > Is it possible to install Cent OS 7.8.2003 on 12TB disk space? > I will be installing Cent OS on the bare metal HW. > > the SAS hardware has to be SAS2 or newer, as SAS1 had a maximum physical drive size of around 2tb and the boot volume has to be GPT as MBR has a 2TB limit. otherwise, sky is the limit, however, what the other guys say, I do NOT put my OS on my data raids, its usually on its own mirror of two small drives. I also tend to avoid "hardware" raid cards, and prefer HBA cards that present the drives as plain SAS devices, then use the OS's native storage management for raid (mdraid + LVM for Linux, ZFS on FreeBSD, etc).. I generally spec raid 10 for performance data, and raid 6 or 60 for bulk data. raid5 is frowned on these days, disks are so big, and rebuild times are long enough that the risk of a double failure is fairly high. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Question regarding cent OS 7.8.2003 compatibility with large SAS disks
Hi, We have servers with 500 Tb in line with SAS attachment on a SAN without any problem! It’s perhaps a firmware problem with your SAS card, no? > Le 25 sept. 2020 à 06:25, Amey Abhyankar a écrit : > > Hello, > > I have a blade server with SAS HDD's of 12TB in total. > 3 HDD's of 4TB each. > > Is it possible to install Cent OS 7.8.2003 on 12TB disk space? > I will be installing Cent OS on the bare metal HW. > > I referred = https://wiki.centos.org/About/Product > But slightly confused with the 'maximum file size' row for ext4 FS. > > Thanks & Regards, > Amey. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Pierre Malard Responsable architectures système GeoSUD IRD - UMR Espace-Dev - UMS CPST Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- signature.asc Description: Message signed with OpenPGP ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Question regarding cent OS 7.8.2003 compatibility with large SAS disks
what I typically rather do is install the OS on a way smaller drive, that way if the OS drive is trashed, the data array is still there, also, it is easier to create a clean install that way. (of course a partition could work too). On 9/24/20 10:34 PM, Amey Abhyankar wrote: On Fri, 25 Sep 2020 at 09:57, R C wrote: I have done it numerous times. Thanks Digimer & R C for the quick help. I am going to touch the blade servers after a gap of decade hence I was in doubt :-) The Cloud computing era has wiped my knowledge about server HW & OS compatibility :-/ Regards, Amey. On 9/24/20 10:25 PM, Amey Abhyankar wrote: Hello, I have a blade server with SAS HDD's of 12TB in total. 3 HDD's of 4TB each. Is it possible to install Cent OS 7.8.2003 on 12TB disk space? I will be installing Cent OS on the bare metal HW. I referred = https://wiki.centos.org/About/Product But slightly confused with the 'maximum file size' row for ext4 FS. Thanks & Regards, Amey. ___ 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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Question regarding cent OS 7.8.2003 compatibility with large SAS disks
On Fri, 25 Sep 2020 at 09:57, R C wrote: > > I have done it numerous times. Thanks Digimer & R C for the quick help. I am going to touch the blade servers after a gap of decade hence I was in doubt :-) The Cloud computing era has wiped my knowledge about server HW & OS compatibility :-/ Regards, Amey. > > On 9/24/20 10:25 PM, Amey Abhyankar wrote: > > Hello, > > > > I have a blade server with SAS HDD's of 12TB in total. > > 3 HDD's of 4TB each. > > > > Is it possible to install Cent OS 7.8.2003 on 12TB disk space? > > I will be installing Cent OS on the bare metal HW. > > > > I referred = https://wiki.centos.org/About/Product > > But slightly confused with the 'maximum file size' row for ext4 FS. > > > > Thanks & Regards, > > Amey. > > ___ > > 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] Question regarding cent OS 7.8.2003 compatibility with large SAS disks
On 2020-09-25 12:25 a.m., Amey Abhyankar wrote: > Hello, > > I have a blade server with SAS HDD's of 12TB in total. > 3 HDD's of 4TB each. > > Is it possible to install Cent OS 7.8.2003 on 12TB disk space? > I will be installing Cent OS on the bare metal HW. > > I referred = https://wiki.centos.org/About/Product > But slightly confused with the 'maximum file size' row for ext4 FS. > > Thanks & Regards, > Amey. That's not a problem at all. In the server world, 12 TB is actually fairly small. :) -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Question regarding cent OS 7.8.2003 compatibility with large SAS disks
I have done it numerous times. On 9/24/20 10:25 PM, Amey Abhyankar wrote: Hello, I have a blade server with SAS HDD's of 12TB in total. 3 HDD's of 4TB each. Is it possible to install Cent OS 7.8.2003 on 12TB disk space? I will be installing Cent OS on the bare metal HW. I referred = https://wiki.centos.org/About/Product But slightly confused with the 'maximum file size' row for ext4 FS. Thanks & Regards, Amey. ___ 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] Question regarding cent OS 7.8.2003 compatibility with large SAS disks
Hello, I have a blade server with SAS HDD's of 12TB in total. 3 HDD's of 4TB each. Is it possible to install Cent OS 7.8.2003 on 12TB disk space? I will be installing Cent OS on the bare metal HW. I referred = https://wiki.centos.org/About/Product But slightly confused with the 'maximum file size' row for ext4 FS. Thanks & Regards, Amey. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] system sounds
Hello, after an update, Centos 7, I don't have any system sounds anymore? Sound works, for video etc. (sound left/right speaker test works) is there a setting that I am missing that somehow got messed up? thanks, Ron ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up
On 24/09/2020 16:28, Simon Matter wrote: On 24/09/2020 13:41, Simon Matter wrote: I've been dealing with issues like this for a while - systems with multiple interfaces, some of which do not come up for quite a while, and I need to wait for all to be up before running certain tasks. Still haven't found anything very satisfactory. All good points. Thank you for that douse of reality. I'm just wondering, is there a chance to make this work reliable without modifying the source code of systemd? Simon Polling? If "some of [them] do not come up for quite a while" it would not be a problem to add another couple of seconds, I guess. It might be against an "event driven" aproach, but it would work and you can add all sorts of tests to make sure everything is ready for your job (eg. including reachability of remote services, etc.) Sounds like a job for shell scripts then - or how do you integrate it with systemd? I still have a lot of such stuff waiting here for being ported to the new systemd world and I still don't really know how to do it best. For pretty standard things it's easy to use systemd unit files but as soon as it gets more complicated, bash scripting feels much easier to me than systemd unit scripting :-( Exactly: Write a service that is just a script waiting for all the things to come up and to be ready. Then do the real thing. I guess you could use that script as a target to reach and you could then wait for *that* in other services. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up
> On 24/09/2020 13:41, Simon Matter wrote: >>> I've been dealing with issues like this for a while - systems with multiple interfaces, some of which do not come up for quite a while, and I need to wait for all to be up before running certain tasks. Still haven't found anything very satisfactory. >>> All good points. Thank you for that douse of reality. >> I'm just wondering, is there a chance to make this work reliable without >> modifying the source code of systemd? >> >> Simon >> > Polling? If "some of [them] do not come up for quite a while" it would > not be a problem to add another couple of seconds, I guess. > > It might be against an "event driven" aproach, but it would work and you > can add all sorts of tests to make sure everything is ready for your job > (eg. including reachability of remote services, etc.) Sounds like a job for shell scripts then - or how do you integrate it with systemd? I still have a lot of such stuff waiting here for being ported to the new systemd world and I still don't really know how to do it best. For pretty standard things it's easy to use systemd unit files but as soon as it gets more complicated, bash scripting feels much easier to me than systemd unit scripting :-( Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up
On 24/09/2020 13:41, Simon Matter wrote: I've been dealing with issues like this for a while - systems with multiple interfaces, some of which do not come up for quite a while, and I need to wait for all to be up before running certain tasks. Still haven't found anything very satisfactory. All good points. Thank you for that douse of reality. I'm just wondering, is there a chance to make this work reliable without modifying the source code of systemd? Simon Polling? If "some of [them] do not come up for quite a while" it would not be a problem to add another couple of seconds, I guess. It might be against an "event driven" aproach, but it would work and you can add all sorts of tests to make sure everything is ready for your job (eg. including reachability of remote services, etc.) Peter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up
> On Wed, 23 Sep 2020 at 23:39, Orion Poplawski wrote:
>
>> On 9/23/20 7:07 AM, Stephen John Smoogen wrote:
>> > On Wed, 23 Sep 2020 at 04:33, Carlos Lopez wrote:
>> >
>> >> Hi all,
>> >>
>> >>
>> >> With SystemD, how can I make certain service dependent on certain
>> network
>> >> interfaces being up?
>> >>
>> >> For example, I have an 802.1ad bond interface I need to wait on for
>> being
>> >> up (this interface has no ip address assigned, it is used to capture
>> >> networks packets with a tcpdump’s script). Every time this service
>> fails
>> >> because bond interface is not up.
>> >>
>> >>
>> >>
>> >> I have configured the service as:
>> >>
>> >>
>> >> [Unit]
>> >>
>> >> Description=tcpdump capture script
>> >>
>> >> After=network.target
>> >>
>> >> Wants=network-online.target
>> >>
>> >>
>> >>
>> >> But it doesn’t work …. Any tip or trick?
>> >>
>> >>
>> >>
>> >
>> > So the network just calls the scripts and exits so they can take a
>> while
>> to
>> > get working. I think this website covers what you want to do
>> >
>> >
>> https://unix.stackexchange.com/questions/257888/systemd-wait-for-network-interface-to-be-up-before-running-service
>> >
>> > systemctl list-units --no-pager | grep subsystem-net
>> >
>> > Then look for the device which matches the one you are listening to.
>> Change
>> > the After=network.target to
>> >
>> >
>> > BindsTo=sys-devices-virtual-net-.device
>> > After=sys-devices-virtual-net-.device
>> >
>> > where is the interface you found (aka eth2, br9, bond0 etc)
>>
>> Hmm, there seems to be several layers here.
>>
>> I think sys-devices-.device is "started" when appears
>> in the kernel:
>>
>> Sep 23 19:37:25 kernel: virtio_net virtio0 ens3: renamed from eth0
>>
>> # systemctl status sys-subsystem-net-devices-ens3.device
>> ● sys-subsystem-net-devices-ens3.device - Virtio network device
>> Loaded: loaded
>> Active: active (plugged) since Wed 2020-09-23 19:37:25 MDT
>>
>> This is not what most people would consider "up" - i.e. have an IP
>> address. ens3 doesn't get it's IP address until much later.
>>
>>
>
> Oh good point. I didn't think about that.
>
>
>> This works for Carlos though because he doesn't need an IP address -
>> just the device existing.
>>
>>
> It may or may not.. I just realized that the device may need to get
> recognized by a switch etc which on a bond may take time.
>
>
>> I have no idea how it worked for the stackexchange poster. Apparently
>> because "lan0" is a virtual device as well
>> ("sys-devices-virtual-net-lan0") that they need, not a more "physical"
>> device like "net-devices-ens3", and it gets an IP address at the same
>> time as creation.
>>
>> I've been dealing with issues like this for a while - systems with
>> multiple interfaces, some of which do not come up for quite a while, and
>> I need to wait for all to be up before running certain tasks. Still
>> haven't found anything very satisfactory.
>>
>>
> All good points. Thank you for that douse of reality.
I'm just wondering, is there a chance to make this work reliable without
modifying the source code of systemd?
Simon
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Systemd service unit file needs to wait until a specific interface is up
On Wed, 23 Sep 2020 at 23:39, Orion Poplawski wrote:
> On 9/23/20 7:07 AM, Stephen John Smoogen wrote:
> > On Wed, 23 Sep 2020 at 04:33, Carlos Lopez wrote:
> >
> >> Hi all,
> >>
> >>
> >> With SystemD, how can I make certain service dependent on certain
> network
> >> interfaces being up?
> >>
> >> For example, I have an 802.1ad bond interface I need to wait on for
> being
> >> up (this interface has no ip address assigned, it is used to capture
> >> networks packets with a tcpdump’s script). Every time this service fails
> >> because bond interface is not up.
> >>
> >>
> >>
> >> I have configured the service as:
> >>
> >>
> >> [Unit]
> >>
> >> Description=tcpdump capture script
> >>
> >> After=network.target
> >>
> >> Wants=network-online.target
> >>
> >>
> >>
> >> But it doesn’t work …. Any tip or trick?
> >>
> >>
> >>
> >
> > So the network just calls the scripts and exits so they can take a while
> to
> > get working. I think this website covers what you want to do
> >
> >
> https://unix.stackexchange.com/questions/257888/systemd-wait-for-network-interface-to-be-up-before-running-service
> >
> > systemctl list-units --no-pager | grep subsystem-net
> >
> > Then look for the device which matches the one you are listening to.
> Change
> > the After=network.target to
> >
> >
> > BindsTo=sys-devices-virtual-net-.device
> > After=sys-devices-virtual-net-.device
> >
> > where is the interface you found (aka eth2, br9, bond0 etc)
>
> Hmm, there seems to be several layers here.
>
> I think sys-devices-.device is "started" when appears
> in the kernel:
>
> Sep 23 19:37:25 kernel: virtio_net virtio0 ens3: renamed from eth0
>
> # systemctl status sys-subsystem-net-devices-ens3.device
> ● sys-subsystem-net-devices-ens3.device - Virtio network device
> Loaded: loaded
> Active: active (plugged) since Wed 2020-09-23 19:37:25 MDT
>
> This is not what most people would consider "up" - i.e. have an IP
> address. ens3 doesn't get it's IP address until much later.
>
>
Oh good point. I didn't think about that.
> This works for Carlos though because he doesn't need an IP address -
> just the device existing.
>
>
It may or may not.. I just realized that the device may need to get
recognized by a switch etc which on a bond may take time.
> I have no idea how it worked for the stackexchange poster. Apparently
> because "lan0" is a virtual device as well
> ("sys-devices-virtual-net-lan0") that they need, not a more "physical"
> device like "net-devices-ens3", and it gets an IP address at the same
> time as creation.
>
> I've been dealing with issues like this for a while - systems with
> multiple interfaces, some of which do not come up for quite a while, and
> I need to wait for all to be up before running certain tasks. Still
> haven't found anything very satisfactory.
>
>
All good points. Thank you for that douse of reality.
> --
> Orion Poplawski
> Manager of NWRA Technical Systems 720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane or...@nwra.com
> Boulder, CO 80301 https://www.nwra.com/
>
>
--
Stephen J Smoogen.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nmcli: unwanted secondary ip-address
> > Actually, we fixed it by killing the dhcclient and and reconnecting > (nmcli con down ... and nmcli con up ... ). > > We are using similar configs and everything is done by using the nmcli, > but we are not facing similar issues there. > > So at this point, I really would like to understand that behaviour. Why is there a dhcclient running at all if you have manual settings? What has started dhcclient? Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] nmcli: unwanted secondary ip-address
Dear Mark, thanks for the additional hints. On 22/09/2020 17:26, Mark Milhollan wrote: On Tue, 22 Sep 2020, Felix Kölzow wrote: A secondary ip address seems to be automatically added to a nic which causes several issues in our setup. # nmcli con show NAME UUID TYPE DEVICE eno4 dbd95c24-1ed7-4292-8dba-3934bd1476a0 ethernet eno4 6: eno4: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:26:b9:78:87:d7 brd ff:ff:ff:ff:ff:ff inet 192.168.2.98/24 brd 192.168.2.255 scope global noprefixroute eno4 valid_lft forever preferred_lft forever inet *192.168.137.223/24* brd 192.168.137.255 scope global dynamic eno4 <<- THIS IS UNWANTED valid_lft 604778sec preferred_lft 604778sec inet6 fe80::9257:5654:b211:8dea/64 scope link noprefixroute valid_lft forever preferred_lft forever You failed to show the configuration of eno4's profile in Network Manager (nmcli con show eno4). You can use 'nmcli con edit' (or nmtui) to modify the profile to eliminate the assignment of the unwanted address -- if it is in automatic mode (which seems to be the case) then you may need to fix your DHCP server instead. If there is no chance that Network Manager is assigning the extra address then you will have to hunt around your system for the program or script that is doing so. /mark You failed to show the configuration of eno4's profile in Network Manager (nmcli con show eno4). Yes, indeed, it was missing. The method is set to manual (additional marked), see below. # nmcli con edit eno4 ===| nmcli interactive connection editor |=== nmcli> p === Connection profile details (eno4) === connection.id: eno4 connection.uuid: dbd95c24-1ed7-4292-8dba-3934bd1476a0 connection.stable-id: -- connection.type: 802-3-ethernet connection.interface-name: eno4 connection.autoconnect: yes connection.autoconnect-priority: 0 connection.autoconnect-retries: -1 (default) connection.multi-connect: 0 (default) connection.auth-retries: -1 connection.timestamp: 1600932622 connection.read-only: no connection.permissions: -- connection.zone: -- connection.master: -- connection.slave-type: -- connection.autoconnect-slaves: -1 (default) connection.secondaries: -- connection.gateway-ping-timeout: 0 connection.metered: unknown connection.lldp: default connection.mdns: -1 (default) connection.llmnr: -1 (default) connection.wait-device-timeout: -1 --- 802-3-ethernet.port: -- 802-3-ethernet.speed: 0 802-3-ethernet.duplex: -- 802-3-ethernet.auto-negotiate: no 802-3-ethernet.mac-address: -- 802-3-ethernet.cloned-mac-address: -- 802-3-ethernet.generate-mac-address-mask:-- 802-3-ethernet.mac-address-blacklist: -- 802-3-ethernet.mtu: auto 802-3-ethernet.s390-subchannels: -- 802-3-ethernet.s390-nettype: -- 802-3-ethernet.s390-options: -- 802-3-ethernet.wake-on-lan: default 802-3-ethernet.wake-on-lan-password: -- --- ipv4.method: manual <<<--- IS SET TO MANUAL ipv4.dns: 10.10.100.1,10.10.100.2 ipv4.dns-search: -- ipv4.dns-options: -- ipv4.dns-priority: 0 ipv4.addresses: 192.168.2.98/24 ipv4.gateway: -- ipv4.routes: -- ipv4.route-metric: -1 ipv4.route-table: 0 (unspec) ipv4.routing-rules: -- ipv4.ignore-auto-routes: yes ipv4.ignore-auto-dns: yes ipv4.dhcp-client-id: -- ipv4.dhcp-iaid: -- ipv4.dhcp-timeout: 0 (default) ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.dhcp-fqdn: -- ipv4.dhcp-hostname-flags: 0x0 (none) ipv4.never-default: yes ipv4.may-fail: yes ipv4.dad-timeout: -1 (default) --- ipv6.method: auto
