3. Grep was hanging up on some device files so...
root@ICTM1612S02H2:/# find / -xdev -type f -print0 |xargs -0 grep -H
"set-log-level"
Binary file /usr/bin/systemd-analyze matches
/usr/share/bash-completion/completions/systemd-analyze:
[LOG_LEVEL]='set-log-level'
/usr/share/apport/symptoms/_audio_data.py:
command_output(['pacmd','set-log-level','4'])
/usr/share/apport/symptoms/_audio_data.py:
command_output(['pacmd','set-log-level','1'])
/usr/share/zsh/vendor-completions/_systemd-analyze:_systemd_analyze_set-log-level()
{
/usr/share/zsh/vendor-completions/_systemd-analyze: 'set-log-level:Set
systemd log threshold'
4. What kind of system is this...It is a Dell PowerEdge R730, baremetal non-VM
system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1569930
Title:
Continuous messages from systemd: dm disk appears twice
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
I have 4 servers running the latest 16.04 updates from the development
branch (as of right now).
Each server is connected to NetApp storage using iscsi software
initiator. There are a total of 56 volumes spread across two NetApp
arrays. Each volume has 4 paths available to it which are being
managed by device mapper.
While running IO to the iscsi targets my system log is flooded with
messages that look like this:
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-scsi\x2d360080e500029092400008d765605fa52.device: Dev
dev-disk-by\x2did-scsi\x2d360080e500029092400008d765605fa52.device appeared
twice with different sysfs paths
/sys/devices/platform/host21/session8/target21:0:0/21:0:0:9/block/sdbh and
/sys/devices/virtual/block/dm-59
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d765605fa52.device: Dev
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d765605fa52.device appeared
twice with different sysfs paths
/sys/devices/platform/host19/session6/target19:0:0/19:0:0:9/block/sdcd and
/sys/devices/virtual/block/dm-59
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-scsi\x2d360080e50002909240000993956f4a1cb.device: Dev
dev-disk-by\x2did-scsi\x2d360080e50002909240000993956f4a1cb.device appeared
twice with different sysfs paths
/sys/devices/platform/host21/session8/target21:0:0/21:0:0:121/block/sdej and
/sys/devices/virtual/block/dm-37
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-wwn\x2d0x60080e50002909240000993956f4a1cb.device: Dev
dev-disk-by\x2did-wwn\x2d0x60080e50002909240000993956f4a1cb.device appeared
twice with different sysfs paths
/sys/devices/platform/host19/session6/target19:0:0/19:0:0:121/block/sdfk and
/sys/devices/virtual/block/dm-37
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-scsi\x2d360080e500029092400008d805605fa8b.device: Dev
dev-disk-by\x2did-scsi\x2d360080e500029092400008d805605fa8b.device appeared
twice with different sysfs paths
/sys/devices/platform/host20/session7/target20:0:0/20:0:0:19/block/sdel and
/sys/devices/virtual/block/dm-50
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d805605fa8b.device: Dev
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d805605fa8b.device appeared
twice with different sysfs paths
/sys/devices/platform/host19/session6/target19:0:0/19:0:0:19/block/sdew and
/sys/devices/virtual/block/dm-50
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-scsi\x2d360080e500029092400008d785605fa5e.device: Dev
dev-disk-by\x2did-scsi\x2d360080e500029092400008d785605fa5e.device appeared
twice with different sysfs paths
/sys/devices/platform/host18/session5/target18:0:0/18:0:0:11/block/sdcb and
/sys/devices/virtual/block/dm-35
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d785605fa5e.device: Dev
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d785605fa5e.device appeared
twice with different sysfs paths
/sys/devices/platform/host20/session7/target20:0:0/20:0:0:11/block/sdcj and
/sys/devices/virtual/block/dm-35
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-scsi\x2d360080e500029092400008d7a5605fa6a.device: Dev
dev-disk-by\x2did-scsi\x2d360080e500029092400008d7a5605fa6a.device appeared
twice with different sysfs paths
/sys/devices/platform/host20/session7/target20:0:0/20:0:0:13/block/sdcw and
/sys/devices/virtual/block/dm-44
Apr 8 11:48:36 ICTM1612S02H2 systemd[1]:
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d7a5605fa6a.device: Dev
dev-disk-by\x2did-wwn\x2d0x60080e500029092400008d7a5605fa6a.device appeared
twice with different sysfs paths
/sys/devices/platform/host21/session8/target21:0:0/21:0:0:13/block/sdcf and
/sys/devices/virtual/block/dm-44
It seems that systemd doesn't know what to do with dm devices and its
"disk-by" simlinks.
This is being tracked in NetApp bug tracker CQ number 860309.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569930/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
