similar to: systemd-udevd not applying ATTR to block device at boot

Hi everyone, I have a udev rule file that contains a singular rule: SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ENV{DEVTYPE}=="disk", ATTR{queue/scheduler}:="noop" When I use a Google Cloud instance and boot it, things work as expected and /dev/sda (a persistent disk) uses the noop scheduler. If the instance also has a

Hi to all I have a supermicro server with LSI 3108 with - 2x300GB SAS spin drive in raid1 (virtual drive 0) - 2x300GB SAS spin drive in raid1 (virtual drive 1) - 2x200GB Intel SSD DC S3710 drives configured as JBOD in LSI bios In the IPMI storage health status eveything looks fine until I boot into Centos 7.1 (unfortunatelly I didn't try other OS, but also I'm not interested in other)

The mtx binary requires my tape library to be assigned a sg# driver, but the kernel periodically renumbers the sg devices. Normally, we would write a udev rule to manually assign a persistent name, but it looks like things have changed as I can't seem to get a match on CEntOS7. I'd appreciate any feedback or pointers to help me get my rule working. My two attempts are below. cat

Hi, I have upgraded an Asterisk installation with a Xorcom BRI Astribank that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no longer initialized. When I reload the udev rules, I see that the rules seems to be correctly loaded: udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file However, these rules do not seem to be triggered: # udevadm trigger

Dne 17.9.2019 v 16:14 Ralf Prengel napsal(a): > > > Am 17.09.2019 um 13:05 schrieb Miroslav Geisselreiter: >> I have brand new PC with this components: >> CPU Intel? Pentium G5400, LGA1151 >> motherboard ASUS PRIME B360M-C >> 16 GB RAM >> HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) >> NIC Intel X550-T1 Ethernet Converged Network

CentOS Errata and Bugfix Advisory 2017:3324 Upstream details at : https://access.redhat.com/errata/RHBA-2017:3324 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 90bd9b96021ad618cde8609b30cebacf2e746f25418e259fa7d57cc9965d1c49 libvirt-3.2.0-14.el7_4.4.x86_64.rpm

CentOS Errata and Enhancement Advisory 2018:0405 Upstream details at : https://access.redhat.com/errata/RHEA-2018:0405 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 81164e5236795d49af78522b24efa7b49235382e2457f3d43c00f069020857b3 fence-agents-all-4.0.11-66.el7_4.4.x86_64.rpm

CentOS Errata and Bugfix Advisory 2017:2941 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2941 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: bbb053ff5961c79e958b2d1a7237ddd67765ec8d337f845a91778601d2c1876b libgudev1-219-42.el7_4.4.i686.rpm

Dear Tom, Thank you very much for thinking about this. Please see my replies below. -Ben > Are you using the EPEL R 3.2.3 builds? I'm not sure what the question means, but I'm pretty sure the answer is no. I know I built the versions of R I used from source code (i.e., ./configure followed by make). > What version of Centos 7? 7.2? [bwittner at kagoshima ~]$ cat

CentOS Errata and Bugfix Advisory 2017:2947 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2947 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a8b71d1a6787a5170d9fd7aa6f1e2568521a96c56016519e973532773b191b35 pacemaker-1.1.16-12.el7_4.4.x86_64.rpm

CentOS Errata and Bugfix Advisory 2017:2929 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2929 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 19bdebfd8975d2012e50c587422fec59b598c4c516d9410346b508642b4c0e32 kmod-20-15.el7_4.4.x86_64.rpm a23d713ebceedfbfb20190b2db8f20976ee01740a1e32b58940c49755cf5a923

https://bugzilla.netfilter.org/show_bug.cgi?id=1746 Bug ID: 1746 Summary: Connection Tracking - TC_DROP in SK_BUFF Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: critical Priority: P5 Component: nf_conntrack Assignee:

https://bugzilla.netfilter.org/show_bug.cgi?id=1747 Bug ID: 1747 Summary: Connection Tracking - TC_DROP in SK_BUFF Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: critical Priority: P5 Component: nf_conntrack Assignee:

CentOS Errata and Security Advisory 2017:3368 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:3368 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 7350789e250a5d7d740e5ff20179d4c5c2a0859d6216aa24afdee661aa6515f8 qemu-img-1.5.3-141.el7_4.4.x86_64.rpm

On 11/06/2017 01:01 PM, Thomas Roth wrote: > Hi all, > > when I check for updates with yum, it gives me a list of packages, with > some additional info, e.g. > > ?--> systemd-sysv-219-42.el7_4.1.x86_64 from @updates removed (updateinfo) > ?--> systemd-sysv-219-42.el7_4.4.x86_64 from updates removed (updateinfo) > > > yum info will tell me that I have 4.1 of

Hi all, when I check for updates with yum, it gives me a list of packages, with some additional info, e.g. --> systemd-sysv-219-42.el7_4.1.x86_64 from @updates removed (updateinfo) --> systemd-sysv-219-42.el7_4.4.x86_64 from updates removed (updateinfo) yum info will tell me that I have 4.1 of this package installed, and that 4.4 is available - from the repo updates. What is the

On Thursday, 13 April 2017 16:55:26 CEST Pavel Butsykin wrote: > Add udev_settle_file() to run 'udevadm settle' with --exit-if-exists option. It > will slightly reduce the waiting-time for pending events if we need to wait > for events related to a particular device/file. > > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > daemon/daemon.h | 2

hi all, latest kmod update 20-15.el7_4.6 is broken on our systems, while previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). the issue is with modules from mellanox kmod rpms that are symlinked in the weak-updates dir. the config files in /etc/depmod.d look ok (and do work with previous version): dist.conf has weak-updates after built-in, and mellanox kmod rpms ship a

I'm getting a lot of this at boottime: udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11707) udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11709) udev still not settled. Waiting. udevadm settle - timeout of 0

Hi all, Sorry for bothering you in this dev mailing list, I'm using libguestfs to customize some vm using as bases the ubuntu cloud images. But I noticed that it takes a lot and then fails when trying to install a packet. Same behaviour on Ubuntu 18.04 and Centos 7.5 Ubuntu: virt-customize 1.36.13 libvirtd (libvirt) 4.0.0 Centos: virt-customize 1.36.10rhel=7,release=6.el7_5.2,libvirt