filesystem error on one time


 Share

0

Recommended Posts

Hello, there

I have got three device`s in one room;

Image`s for this three device`s was burned to ssd card`s on this week (at 17.04.2019)

Today, in the same time (Apr 21 06:47:03) they all fall down with same error (form syslog):

 

Apr 21 06:20:52 localhost systemd[1]: Starting Daily apt upgrade and clean activities...
Apr 21 06:20:52 localhost systemd[1]: Started Daily apt upgrade and clean activities.
Apr 21 06:25:01 localhost CRON[8132]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 21 06:25:01 localhost CRON[8131]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Apr 21 06:30:01 localhost CRON[8283]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Apr 21 06:35:01 localhost CRON[8347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 21 06:45:01 localhost CRON[8454]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Apr 21 06:45:01 localhost CRON[8455]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 21 06:47:01 localhost CRON[8484]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))
Apr 21 06:47:03 localhost kernel: [192981.845014] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530053: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=28672, inode=4294967295, rec_len=65535, name_len=255, size=4096
Apr 21 06:47:03 localhost kernel: [192981.941193] Aborting journal on device mmcblk0p1-8.
Apr 21 06:47:03 localhost kernel: [192981.953977] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
Apr 21 06:47:03 localhost kernel: [192981.964478] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530052: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=24576, inode=4294967295, rec_len=65535, name_len=255, size=4096

 

in kern log i see same error:

Apr 21 06:47:03 localhost kernel: [192981.845014] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530053: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=28672, inode=4294967295, rec_len=65535, name_len=255, size=4096
Apr 21 06:47:03 localhost kernel: [192981.941193] Aborting journal on device mmcblk0p1-8.
Apr 21 06:47:03 localhost kernel: [192981.953977] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
Apr 21 06:47:03 localhost kernel: [192981.964478] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530052: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=24576, inode=4294967295, rec_len=65535, name_len=255, size=4096

 

Environment:

BOARD=orangepipc2
BOARD_NAME="Orange Pi PC2"
BOARDFAMILY=sun50iw2
VERSION=5.67
LINUXFAMILY=sunxi64
BRANCH=next
ARCH=arm64
IMAGE_TYPE=custom
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image

 

 

In syslog I gote line bofore error = 

Apr 21 06:47:01 localhost CRON[8484]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))

can it be that cron.weekly was do something wrong?

How you think, what was going wrong?

Link to post
Share on other sites

Armbian is a community driven open source project. Do you like to contribute your code?

Guest
This topic is now closed to further replies.
 Share

0