Arch Linux

mouseman

Member

From: Outta nowhere

Registered: 2014-04-04

Posts: 298

udisksd error creating watch for file

I'm getting this error in my logs. I'm not sure if this can be ignored or not? I've got 2 disks in RAID0 mounted under /data. The volume mounts and works fine. Mdadm --detail /dev/md0 says its fine.

Apr 09 09:25:01 somehost systemd[1]: Starting Disk Manager...
Apr 09 09:25:01 somehost udisksd[641]: udisks daemon version 2.1.3 starting
Apr 09 09:25:01 somehost udisksd[641]: Error creating watch for file /sys/devices/virtual/block/md0/md/sync_action: No such file or directory (g-file-error-quark, 4)
Apr 09 09:25:01 somehost udisksd[641]: Error creating watch for file /sys/devices/virtual/block/md0/md/degraded: No such file or directory (g-file-error-quark, 4)
Apr 09 09:25:01 somehost dbus[310]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Apr 09 09:25:01 somehost systemd[1]: Started Disk Manager.

On the CentOS forums I found someone with a similar message and they said sync_action was a feature that might not have been activated in the kernel. I suppose the same would count for degraded as well:
https://www.centos.org/forums/viewtopic … 8&start=20

Is this correct and is this something I can safely ignore?

Thanks!

Buddlespit

Member

From: Chesapeake, Va.

Registered: 2014-02-07

Posts: 507

Re: udisksd error creating watch for file

No, I don't think we should be ignoring this. This is a check for degradation, sync and there should also be something for trimming. I've never had these files and have been searching Google for an answer. If you've found something, please share.

---

An old man, trying to stay sane

imre

Member

Registered: 2016-03-28

Posts: 1

Re: udisksd error creating watch for file

Raid 0 doesn't provide any redundancy, so the kernel won't expose the corresponding redundancy sysfs attributes like sync_action and degraded. I think udisksd should be fixed, so that it doesn't try to open these files for raid 0 arrays.