On Tue, 22 Mar 2022, Ben Koenig wrote:
The error has everything you need to know.
Ben,
That's assuming I know how to interpret it ... which I didn't.
Logwatch is reporting that a driver for EXT4 reported that an error
occurred on device dm-0. This error was recoverable so it didn't bring the
entire system down. The actual error is still in the log file where it was
originally reported.
The first instance of this error was seen at 16477870.
It did not repeat.
16477870 is a UNIX time stamp minus the last 2 digits.
$ date -d @1647787000
Sun Mar 20 07:36:40 PDT 2022
At approximately 7PM Sunday, March 20, 2022 your system experienced a
recoverable filesystem error. You may want to look for the original error
message since logwatch is stripping out a lot of the details.
Has your dm-0 storage volume been exhibiting any errant behavior? ;-)
Not to my knowledge since I don't know to what dm-0 points. The ext4 file
systems on this host are /dev/sda3 (/), /dev/sdb{1,2.3},
/dev/probox_gv/data_store
(logical volumn mounted on /media/hd1), and /dev/md0 (/media/backup).
dirvish quit working last Thursday but I found and fixed that problem
yesterday morning, so it was not active Sunday evening. It could have been
the LV; I had to rebuild that and restore its contents from the backup.
Thanks,
Rich
