Re: [Lessfs-users] lessfs-1.6.0-alpha0 issues

[Nils K. <ni...@ib...>]

Hey there,

I had some time to investigate my problems a bit deeper,
it seems to me that the problem is with the database -
either I use Berkely DB (4.8 from Ubuntu repository) or hamsterdb 1.1.15
(self compiled) I get the same issues as described below.

Mark - any hints on which database version you use resp. compile options?

Cheers,
Nils

> Hi!
>
> I am using lessfs-1.6.0-alpha0 and I just wonder if it is only me suffering
> instability issues copy-/deleting files?
> I use berkelydb and qlz compression and of course I'd like to test the new
> feature multifile_io.
> Am I doing something incredible stupid or is it just not yet working  
> properly?
> Please see my configuration below.
> Basesystem is Ubuntu Oneric Ocelot.
>
> When I launch lessfs /etc/lessfs.cfg mnt/ -o debug
> FUSE library version: 2.8.4
> nullpath_ok: 0
> unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
> INIT: 7.16
> flags=0x0000007b
> max_readahead=0x00020000
>     INIT: 7.12
>     flags=0x00000031
>     max_readahead=0x00000080
>     max_write=0x00020000
>     unique: 1, success, outsize: 40
> unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56
> getattr /
>     unique: 2, success, outsize: 120
> unique: 3, opcode: LOOKUP (1), nodeid: 1, insize: 47
> LOOKUP /.Trash
> getattr /.Trash
>     unique: 3, error: -2 (No such file or directory), outsize: 16
> unique: 4, opcode: LOOKUP (1), nodeid: 1, insize: 52
> LOOKUP /.Trash-1000
> getattr /.Trash-1000
>     unique: 4, error: -2 (No such file or directory), outsize: 16
> <... snipp ...>
>
>
> nothing exiting happends, even when the thing crashes, it silenty
> dies, leaving
> no trace :-/
> The operation causing the crash mubles something like  rm: fts_read
> failed: Transport
> endpoint is not connected.
>
> Any suggestions? Thanks for your attention,
> Nils
>
>
> ###############################################################################
> # Enable informational messages about compression.
> DEBUG = 5
> HASHNAME=MHASH_TIGER192
> # The (chopped) hashlen in bytes, minimum is 20.
> HASHLEN = 24
> BLOCKDATA_IO_TYPE=multifile_io
> BLOCKDATA_PATH=/home/nils/data/dta/blockdata.dta
> #
> META_PATH=/home/nils/data/mta
> META_BS=1048576
> #
> CACHESIZE=512
> # Flush data to disk after X seconds.
> COMMIT_INTERVAL=10
> #
> LISTEN_IP=127.0.0.1
> LISTEN_PORT=100
> # Not more then 2 on most machines.
> MAX_THREADS=16
> DYNAMIC_DEFRAGMENTATION=on
> COREDUMPSIZE=2560000000
> # Consider SYNC_RELAX=1 or SYNC_RELAX=2 when exporting lessfs with NFS.
> SYNC_RELAX=0
> # When BACKGROUND_DELETE=on lessfs will spawn a thread to delete
> # a file as a background task. This is a recently added feature
> # and is therefore disabled by default.
> BACKGROUND_DELETE=on
> # Requires openssl and lessfs has to be configured with --with-crypto
> ENCRYPT_DATA=off
> # ENCRYPT_META on or off, default is off
> # Requires ENCRYPT_DATA=on and is otherwise ignored.
> ENCRYPT_META=off
> # You don't like fsck?
> ENABLE_TRANSACTIONS=on
> # Select a blocksize to fit your needs.
> BLKSIZE=131072
> COMPRESSION=qlz
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Lessfs-users mailing list
> Les...@li...
> https://lists.sourceforge.net/lists/listinfo/lessfs-users
>