For me lessfsck does crashed all the time, even when i do new a database and then run lessfsck, it still crashes:
# mklessfs /etc/lessfs.cfg # lessfsck -c /etc/lessfs.cfg Running lessfsck on a mounted filesystem will corrupt the databases. Press ctrl-c within 5 secondes when you are not sure that the filesystem is unmounted. ************************************************** * Running lessfsck on a tc data store. * ************************************************** Phase 1 : Check the directory structure. Phase 2 : Check for orphaned inodes. Phase 3 : Check for orphaned data blocks. *** glibc detected *** lessfsck: munmap_chunk(): invalid pointer: 0x0000000016410680 *** ======= Backtrace: ========= /lib64/libc.so.6(cfree+0x1b6) lessfsck /lib64/libc.so.6(__libc_start_main+0xf4) lessfsck ======= Memory map: ======== 00400000-00421000 r-xp 00000000 fd:00 7231207 /usr/bin/lessfsck 00621000-00624000 rw-p 00021000 fd:00 7231207 /usr/bin/lessfsck 16410000-166ec000 rw-p 16410000 00:00 0 3442000000-344212d000 r-xp 00000000 fd:00 2424865 /lib64/libcrypto.so.0.9.8e 344212d000-344232c000 --p 0012d000 fd:00 2424865 /lib64/libcrypto.so.0.9.8e 344232c000-344234d000 rw-p 0012c000 fd:00 2424865 /lib64/libcrypto.so.0.9.8e 344234d000-3442351000 rw-p 344234d000 00:00 0 3442400000-3442445000 r-xp 00000000 fd:00 2424871 /lib64/libssl.so.0.9.8e 3442445000-3442644000 --p 00045000 fd:00 2424871 /lib64/libssl.so.0.9.8e 3442644000-344264a000 rw-p 00044000 fd:00 2424871 /lib64/libssl.so.0.9.8e 3550400000-3550475000 r-xp 00000000 fd:00 7231253 /usr/lib64/libtokyocabinet.so.8.26.0 3550475000-3550675000 --p 00075000 fd:00 7231253 /usr/lib64/libtokyocabinet.so.8.26.0 3550675000-3550677000 rw-p 00075000 fd:00 7231253 /usr/lib64/libtokyocabinet.so.8.26.0 36d5000000-36d5022000 r-xp 00000000 fd:00 7231222 /usr/lib64/libfuse.so.2.8.1 36d5022000-36d5221000 --p 00022000 fd:00 7231222 /usr/lib64/libfuse.so.2.8.1 36d5221000-36d5233000 rw-p 00021000 fd:00 7231222 /usr/lib64/libfuse.so.2.8.1 3eef400000-3eef41c000 r-xp 00000000 fd:00 2424880 /lib64/ld-2.5.so 3eef61b000-3eef61c000 r-p 0001b000 fd:00 2424880 /lib64/ld-2.5.so 3eef61c000-3eef61d000 rw-p 0001c000 fd:00 2424880 /lib64/ld-2.5.so 3eef800000-3eef94c000 r-xp 00000000 fd:00 2425130 /lib64/libc-2.5.so 3eef94c000-3eefb4c000 --p 0014c000 fd:00 2425130 /lib64/libc-2.5.so 3eefb4c000-3eefb50000 r-p 0014c000 fd:00 2425130 /lib64/libc-2.5.so 3eefb50000-3eefb51000 rw-p 00150000 fd:00 2425130 /lib64/libc-2.5.so 3eefb51000-3eefb56000 rw-p 3eefb51000 00:00 0 3eefc00000-3eefc02000 r-xp 00000000 fd:00 2425133 /lib64/libdl-2.5.so 3eefc02000-3eefe02000 --p 00002000 fd:00 2425133 /lib64/libdl-2.5.so 3eefe02000-3eefe03000 r-p 00002000 fd:00 2425133 /lib64/libdl-2.5.so 3eefe03000-3eefe04000 rw-p 00003000 fd:00 2425133 /lib64/libdl-2.5.so 3ef0000000-3ef0016000 r-xp 00000000 fd:00 2425131 /lib64/libpthread-2.5.so 3ef0016000-3ef0215000 --p 00016000 fd:00 2425131 /lib64/libpthread-2.5.so 3ef0215000-3ef0216000 r-p 00015000 fd:00 2425131 /lib64/libpthread-2.5.so 3ef0216000-3ef0217000 rw-p 00016000 fd:00 2425131 /lib64/libpthread-2.5.so 3ef0217000-3ef021b000 rw-p 3ef0217000 00:00 0 3ef0400000-3ef0482000 r-xp 00000000 fd:00 2425135 /lib64/libm-2.5.so 3ef0482000-3ef0681000 --p 00082000 fd:00 2425135 /lib64/libm-2.5.so 3ef0681000-3ef0682000 r-p 00081000 fd:00 2425135 /lib64/libm-2.5.so 3ef0682000-3ef0683000 rw-p 00082000 fd:00 2425135 /lib64/libm-2.5.so 3ef0800000-3ef0814000 r-xp 00000000 fd:00 7221322 /usr/lib64/libz.so.1.2.3 3ef0814000-3ef0a13000 --p 00014000 fd:00 7221322 /usr/lib64/libz.so.1.2.3 3ef0a13000-3ef0a14000 rw-p 00013000 fd:00 7221322 /usr/lib64/libz.so.1.2.3 3ef0c00000-3ef0c07000 r-xp 00000000 fd:00 2425137 /lib64/librt-2.5.so 3ef0c07000-3ef0e07000 --p 00007000 fd:00 2425137 Keskeytetty
lessfs-0.8.2 fixes this problem. It only occurs when lessfs is compiled with encryption support and encryption being disabled in the config file.
Mark.
Log in to post a comment.
For me lessfsck does crashed all the time, even when i do new a database and then run lessfsck, it still crashes:
# mklessfs /etc/lessfs.cfg
# lessfsck -c /etc/lessfs.cfg
Running lessfsck on a mounted filesystem will corrupt the databases.
Press ctrl-c within 5 secondes when you are not sure that the filesystem is unmounted.
**************************************************
* Running lessfsck on a tc data store. *
**************************************************
Phase 1 : Check the directory structure.
Phase 2 : Check for orphaned inodes.
Phase 3 : Check for orphaned data blocks.
*** glibc detected *** lessfsck: munmap_chunk(): invalid pointer: 0x0000000016410680 ***
======= Backtrace: =========
/lib64/libc.so.6(cfree+0x1b6)
lessfsck
/lib64/libc.so.6(__libc_start_main+0xf4)
lessfsck
======= Memory map: ========
00400000-00421000 r-xp 00000000 fd:00 7231207 /usr/bin/lessfsck
00621000-00624000 rw-p 00021000 fd:00 7231207 /usr/bin/lessfsck
16410000-166ec000 rw-p 16410000 00:00 0
3442000000-344212d000 r-xp 00000000 fd:00 2424865 /lib64/libcrypto.so.0.9.8e
344212d000-344232c000 --p 0012d000 fd:00 2424865 /lib64/libcrypto.so.0.9.8e
344232c000-344234d000 rw-p 0012c000 fd:00 2424865 /lib64/libcrypto.so.0.9.8e
344234d000-3442351000 rw-p 344234d000 00:00 0
3442400000-3442445000 r-xp 00000000 fd:00 2424871 /lib64/libssl.so.0.9.8e
3442445000-3442644000 --p 00045000 fd:00 2424871 /lib64/libssl.so.0.9.8e
3442644000-344264a000 rw-p 00044000 fd:00 2424871 /lib64/libssl.so.0.9.8e
3550400000-3550475000 r-xp 00000000 fd:00 7231253 /usr/lib64/libtokyocabinet.so.8.26.0
3550475000-3550675000 --p 00075000 fd:00 7231253 /usr/lib64/libtokyocabinet.so.8.26.0
3550675000-3550677000 rw-p 00075000 fd:00 7231253 /usr/lib64/libtokyocabinet.so.8.26.0
36d5000000-36d5022000 r-xp 00000000 fd:00 7231222 /usr/lib64/libfuse.so.2.8.1
36d5022000-36d5221000 --p 00022000 fd:00 7231222 /usr/lib64/libfuse.so.2.8.1
36d5221000-36d5233000 rw-p 00021000 fd:00 7231222 /usr/lib64/libfuse.so.2.8.1
3eef400000-3eef41c000 r-xp 00000000 fd:00 2424880 /lib64/ld-2.5.so
3eef61b000-3eef61c000 r-p 0001b000 fd:00 2424880 /lib64/ld-2.5.so
3eef61c000-3eef61d000 rw-p 0001c000 fd:00 2424880 /lib64/ld-2.5.so
3eef800000-3eef94c000 r-xp 00000000 fd:00 2425130 /lib64/libc-2.5.so
3eef94c000-3eefb4c000 --p 0014c000 fd:00 2425130 /lib64/libc-2.5.so
3eefb4c000-3eefb50000 r-p 0014c000 fd:00 2425130 /lib64/libc-2.5.so
3eefb50000-3eefb51000 rw-p 00150000 fd:00 2425130 /lib64/libc-2.5.so
3eefb51000-3eefb56000 rw-p 3eefb51000 00:00 0
3eefc00000-3eefc02000 r-xp 00000000 fd:00 2425133 /lib64/libdl-2.5.so
3eefc02000-3eefe02000 --p 00002000 fd:00 2425133 /lib64/libdl-2.5.so
3eefe02000-3eefe03000 r-p 00002000 fd:00 2425133 /lib64/libdl-2.5.so
3eefe03000-3eefe04000 rw-p 00003000 fd:00 2425133 /lib64/libdl-2.5.so
3ef0000000-3ef0016000 r-xp 00000000 fd:00 2425131 /lib64/libpthread-2.5.so
3ef0016000-3ef0215000 --p 00016000 fd:00 2425131 /lib64/libpthread-2.5.so
3ef0215000-3ef0216000 r-p 00015000 fd:00 2425131 /lib64/libpthread-2.5.so
3ef0216000-3ef0217000 rw-p 00016000 fd:00 2425131 /lib64/libpthread-2.5.so
3ef0217000-3ef021b000 rw-p 3ef0217000 00:00 0
3ef0400000-3ef0482000 r-xp 00000000 fd:00 2425135 /lib64/libm-2.5.so
3ef0482000-3ef0681000 --p 00082000 fd:00 2425135 /lib64/libm-2.5.so
3ef0681000-3ef0682000 r-p 00081000 fd:00 2425135 /lib64/libm-2.5.so
3ef0682000-3ef0683000 rw-p 00082000 fd:00 2425135 /lib64/libm-2.5.so
3ef0800000-3ef0814000 r-xp 00000000 fd:00 7221322 /usr/lib64/libz.so.1.2.3
3ef0814000-3ef0a13000 --p 00014000 fd:00 7221322 /usr/lib64/libz.so.1.2.3
3ef0a13000-3ef0a14000 rw-p 00013000 fd:00 7221322 /usr/lib64/libz.so.1.2.3
3ef0c00000-3ef0c07000 r-xp 00000000 fd:00 2425137 /lib64/librt-2.5.so
3ef0c07000-3ef0e07000 --p 00007000 fd:00 2425137 Keskeytetty
lessfs-0.8.2 fixes this problem. It only occurs when lessfs is compiled with encryption support and encryption being disabled in the config file.
Mark.