You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the past week or so, my logger is flooded with the following message: udevd[timestamp]: inotify_add_watch(7, /dev/sdb, 10) failed: No such file or directory.
udev still seems to work, so the message seems harmless. But I would like to disable this message or fix whatever it's root cause is. I remember that, while dd'ing to /dev/sdb, I lost connection to that device. dd wrote the remaining data to /dev/sdb as tmpfs (which seems like wrong behavior to me). With a big chunk of my memory used up, I deleted /dev/sdb and now this message keeps spamming my logger.
udev still seems to detect devices and can create /dev/sdb when there is a new device. However, instead of fixing the previous error message udev spams inotify_add_watch(7, /dev/sdc, 10) failed: No such file or directory and will just change to sdd, sde when additional devices are added.
The text was updated successfully, but these errors were encountered:
For the past week or so, my logger is flooded with the following message:
udevd[timestamp]: inotify_add_watch(7, /dev/sdb, 10) failed: No such file or directory
.udev still seems to work, so the message seems harmless. But I would like to disable this message or fix whatever it's root cause is. I remember that, while
dd
'ing to /dev/sdb, I lost connection to that device.dd
wrote the remaining data to/dev/sdb
as tmpfs (which seems like wrong behavior to me). With a big chunk of my memory used up, I deleted/dev/sdb
and now this message keeps spamming my logger.udev still seems to detect devices and can create /dev/sdb when there is a new device. However, instead of fixing the previous error message udev spams
inotify_add_watch(7, /dev/sdc, 10) failed: No such file or directory
and will just change tosdd
,sde
when additional devices are added.The text was updated successfully, but these errors were encountered: