Lessfs-1.0.7 is available for download.

This release fixes a problem where data copied from windows to lessfs (samba) would show the wrong nr of blocks. This would result in du reporting wrong disk usage numbers.

This entry was posted in Uncategorized. Bookmark the permalink.

5 Responses to Lessfs-1.0.7 is available for download.

  1. Tidder says:

    Thank you for the fix! I was getting ready to set up samba shares for backups until I read about the bug. Let me tell you, connecting to NFS shares through windows is no walk in the park! I’m excited to try this out with my samba shares, thank you!

  2. BrianX says:

    I did an upgrade from 1.0.6 to 1.0.7 and it rolled back my entire filesystem. Is this expected?

    Mar 29 00:24:33 sheevaplug lessfs[20984]: The selected data store is file_io.
    Mar 29 00:24:33 sheevaplug lessfs[20984]: Lessfs transaction support is enabled.
    Mar 29 00:24:33 sheevaplug lessfs[20984]: Lessfs uses a 24 bytes long hash.
    Mar 29 00:24:33 sheevaplug lessfs[20984]: Lessfs fsync does not sync the databases to the disk when fsync is called on an inode
    Mar 29 00:24:33 sheevaplug lessfs[20984]: cache 2048 data blocks
    Mar 29 00:24:33 sheevaplug lessfs[20984]: The tiger hash has been selected.
    Mar 29 00:24:33 sheevaplug lessfs[20984]: Rollback : truncate /media/dedupe/dta/blockdata.dta from 121144737140 to 0
    Mar 29 00:29:14 sheevaplug mklessfs[21010]: The selected data store is file_io.
    Mar 29 00:29:14 sheevaplug mklessfs[21010]: Lessfs transaction support is enabled.
    Mar 29 00:29:14 sheevaplug mklessfs[21010]: Lessfs uses a 24 bytes long hash.
    Mar 29 00:29:14 sheevaplug mklessfs[21010]: Lessfs fsync does not sync the databases to the disk when fsync is called on an inode
    Mar 29 00:29:14 sheevaplug mklessfs[21010]: cache 2048 data blocks
    Mar 29 00:29:14 sheevaplug mklessfs[21010]: The tiger hash has been selected.

    • maru says:

      Hi Brian,

      This is very unexpected and of course a rather critical event.

      Did you cleanly umount the filesystem before upgrading it?
      Have you enabled transactions after you upgraded?
      I tested some of the obvious scenario’s but I am unable to replicate this.

      Can you tell me exactly what you have done and share your config?

      Mark

      • maru says:

        I have found the problem.
        A metadata field is not present in older versions of lessfs. I could reproduce this bug by migrating from lessfs-1.0.0 without transaction support to lessfs-1.0.8 with transactions enabled.

        lessfs-1.0.8 fixes this problem by automatically adding the missing metadata when it detects the old structure.

        Mark.

  3. Pete says:

    It works! The Samba bug is gone. :)

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>