OPNsense Forum
Archive => 20.7 Legacy Series => Topic started by: GreenMatter on November 17, 2020, 02:48:44 pm
-
I've got some index error in Sensei DB. That made me to run fsck and results are:
root@OPNsense:~ # fsck -F /dev/gpt/rootfs
** /dev/gpt/rootfs (NO WRITE)
** Last Mounted on /mnt
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=1135285 OWNER=squid MODE=100644
SIZE=11580 MTIME=Nov 13 00:00 2020
CLEAR? no
UNREF FILE I=1135313 OWNER=squid MODE=100644
SIZE=16601 MTIME=Nov 15 00:00 2020
CLEAR? no
UNREF FILE I=1135766 OWNER=squid MODE=100644
SIZE=22340 MTIME=Nov 12 00:00 2020
CLEAR? no
UNREF FILE I=1135860 OWNER=squid MODE=100644
SIZE=32909 MTIME=Nov 11 00:00 2020
CLEAR? no
UNREF FILE I=1138321 OWNER=squid MODE=100644
SIZE=6454 MTIME=Nov 14 00:00 2020
CLEAR? no
UNREF FILE I=1138958 OWNER=root MODE=100640
SIZE=0 MTIME=Nov 17 14:38 2020
RECONNECT? no
CLEAR? no
UNREF FILE I=1138963 OWNER=root MODE=100640
SIZE=0 MTIME=Nov 17 14:38 2020
RECONNECT? no
CLEAR? no
UNREF FILE I=1140082 OWNER=squid MODE=100644
SIZE=19194 MTIME=Nov 17 00:00 2020
CLEAR? no
UNREF FILE I=1142433 OWNER=squid MODE=100644
SIZE=20867 MTIME=Nov 16 00:00 2020
CLEAR? no
** Phase 5 - Check Cyl groups
107662 files, 5957469 used, 4448233 free (18737 frags, 553687 blocks, 0.2% fragmentation)
How can I get them repaired?
-
Ok, I've run fsck in single user mode and all is fine.
It seems that fsck reference errors are "normal" when scan is performed on running system...