[SOLVED] EXT4-fs (dm-10): write access unavailable, skipping orphan cleanup

[lethargos]

root@svorng11:~# dmesg | grep orphan
[3851856.698684] EXT4-fs (dm-10): write access unavailable, skipping orphan cleanup
pveversion
pve-manager/5.2-1/0fcd7879 (running kernel: 4.15.17-2-pve)


The same thing appeared in the linux console for dm 6, 8, 9, and 11. dm-10 and dm-11 don't exist. dm-9 is a shut down container and dm-7 and dm-8 are two functional containers.
Am I supposed to be worried? The server did report there was a problem with a spare SSD, but I don't think that should be a problem. The raid itself is fine.

 

[tbardin]

Hi same here !

 

[Harald Treis]

Hi,
don't worry, vzdump creates read-only snapshots to backup lxc containers.

This is no errror: "That error message just means that the block device has been marked read-only."
Look here: https://www.spinics.net/lists/linux-ext4/msg60036.html

Kind regards,
Harry

 

[LeifSec]

As harmless errors (and warnings) in logs may mask "real" errors: How can I disable the error message / filter it in journald?

Of course another solution would be to filter the message in my monitoring system / log analysis so that it does not show up there. But it it would be better to eliminate the error at the source / close to the source / on the corresponding machine.

 

[J-dub]

As harmless errors (and warnings) in logs may mask "real" errors: How can I disable the error message / filter it in journald?

Of course another solution would be to filter the message in my monitoring system / log analysis so that it does not show up there. But it it would be better to eliminate the error at the source / close to the source / on the corresponding machine.

From freedesktop

LogFilterPatterns=
Define an extended regular expression to filter log messages based on the MESSAGE= field of the structured message. If the first character of the pattern is "~", log entries matching the pattern should be discarded. This option takes a single pattern as an argument but can be used multiple times to create a list of allowed and denied patterns. If the empty string is assigned, the filter is reset, and all prior assignments will have no effect.

Because the "~" character is used to define denied patterns, it must be replaced with "\x7e" to allow a message starting with "~". For example, "~foobar" would add a pattern matching "foobar" to the deny list, while "\x7efoobar" would add a pattern matching "~foobar" to the allow list.

Log messages are tested against denied patterns (if any), then against allowed patterns (if any). If a log message matches any of the denied patterns, it will be discarded, whatever the allowed patterns. Then, remaining log messages are tested against allowed patterns. Messages matching against none of the allowed pattern are discarded. If no allowed patterns are defined, then all messages are processed directly after going through denied filters.

Filtering is based on the unit for which LogFilterPatterns= is defined, meaning log messages coming from systemd(1) about the unit are not taken into account. Filtered log messages won't be forwarded to traditional syslog daemons, the kernel log buffer (kmsg), the systemd console, or sent as wall messages to all logged-in users.

Added in version 253.

Not a real example (just an idea):

nano /etc/systemd/system/<kernel?>.service.d/10-journalfilter.conf

[Service]
LogFilterPatterns=~EXT4-fs
LogFilterPatterns=~(rbd5)

Or maybe this not all accurate example?:

systemctl edit smb.service

### Editing /etc/systemd/system/<EXT4-fs?>.service.d/override.conf
### Anything between here and the comment below will become the contents of the drop-in file

[Service]
LogFilterPatterns=~EXT4-fs\/pve-manager/5.2-1/0fcd7879
LogFilterPatterns=~"write access"
LogFilterPatterns=~pveversion

### Edits below this comment will be discarded

Systemd developers explain it