[Lessfs-users] lessfs crashing with SIGABORT
Brought to you by:
mruijter
From: David N. <do...@ma...> - 2017-11-04 02:58:36
|
I am running lessfs for the first time. Attached is the cfg file the log file and a gdb analysis of the events leading up to the SIGABORT (in gdb a SIGUSER1 is generated instead, I'm not sure why. Maybe the SIGABOUT comes afterwards). # equery l -p lessfs * Searching for lessfs ... [-P-] [ ] sys-fs/lessfs-1.5.13:0 [IP-] [ ] sys-fs/lessfs-1.7.0:0 # lessfs --version ------------------------------------------------------- lessfs 1.7.0 Usage: lessfs [/path_to_config.cfg] [mount_point] <FUSE OPTIONS> Example : mklessfs /etc/lessfs.cfg lessfs /etc/lessfs.cfg /mnt A high performance example with big_writes. (Requires kernel 2.6.26 or higher and a recent version of fuse.) lessfs /etc/lessfs.cfg /fuse -o use_ino,readdir_ino,default_permissions,\ allow_other,big_writes,max_read=131072,max_write=131072 ------------------------------------------------------- (gdb) bt #0 0x00007ffff73fba87 in kill () at ../sysdeps/unix/syscall-template.S:84 #1 0x00000000004157ff in exitFunc () at lib_safe.c:230 #2 0x00000000004164d4 in s_open2 (pathname=pathname@entry=0x6441f0 "/mnt/md1/lessfs/dta/blockdata.dta/replog.dta", flags=flags@entry=262210, mode=mode@entry=448) at lib_safe.c:493 #3 0x000000000041fdc9 in bdb_open () at lib_bdb.c:331 #4 0x000000000040f06f in parseconfig (mklessfs=mklessfs@entry=0, force_optimize=force_optimize@entry=false) at lib_common.c:3728 #5 0x00000000004041bb in main (argc=<optimized out>, argv=0x7fffffffb338) at lessfs.c:2147 I realize that I'm using a larger hash value then is the max according to the manual (I tried changing this to the maximum value without result). The sha512sum uses 512 bits and there is not way around that so I am assuming that the docs are out of date with respect to that, if not please tell me. Thanks, David |