Error in compression of standalone volume, java.io.IOException: not implemented

[David Truog]

So I deleted a VM disk and wanted to compact to recover the space, but I get the following error.  This is a standalone volume.  The volume was not mounted at the time as per instructions.  Any suggestions would be appreciated.

mount.sdfs -v vms -c -m "/VirtualBox VMs/"
Running Program SDFS Version 2.0.11
reading config file = /etc/sdfs/vms-volume-cfg.xml
Initializing HashFunction
HashFunction Initialized
Loading Existing Hash Tables |))))))))))))))))))))))))))))))))))))))))))))))))))| 100%

Loading BloomFilters |))))))))))))))))))))))))))))))))))))))))))))))))))| 100%

Loaded entries 18034408
Initiating Compaction Process
Step 1 of 3 - Running Garbage Collection
Cleared [162324] records during garbage collection
Step 2 of 3 - Initializing Compaction
Closing Hash Tables |))))))))))))))))))))))))))))))))))))))))))))))))))| 100%

Saving BloomFilters |))))))))))))))))))))))))))))))))))))))))))))))))))| 100%

Loading Existing Hash Tables |))))))))))))))))))))))))))))))))))))))))))))))))))| 100%

Loading BloomFilters |))))))))))))))))))))))))))))))))))))))))))))))))))| 100%

Loaded entries 15551979
Running Compaction on DSE, this may take a while
Scanning DSE |]                                                 | 0% Unable to finish compaction becausejava.io.IOException: not implemented
Unable to initialize HashChunkService
java.io.IOException: Unable to finish compaction
    at org.opendedup.sdfs.filestore.DSECompaction.runCheck(DSECompaction.java:64)
    at org.opendedup.sdfs.filestore.DSECompaction.runCheck(DSECompaction.java:87)
    at org.opendedup.sdfs.servers.HashChunkService.init(HashChunkService.java:209)
    at org.opendedup.sdfs.servers.HCServiceProxy.init(HCServiceProxy.java:161)
    at org.opendedup.sdfs.servers.SDFSService.start(SDFSService.java:62)
    at fuse.SDFS.MountSDFS.main(MountSDFS.java:152)
[1]+  Done

[Sam Silverberg]

Hi there! 

You cannot run conpaction on variable block volumes. This will be fixed in the next release so I would sit tight for a few weeks if that is ok.

--
You received this message because you are subscribed to the Google Groups "dedupfilesystem-sdfs-user-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dedupfilesystem-sdfs-u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marcobaldo]

Hello.

Fyi I have the same issue on a fixed block volume (hash-type="murmur3_128").

<locations dedup-db-store="/sdfs/volumes/pool1/ddb" io-log="/sdfs/volumes/pool1/ioperf.log"/>
<io chunk-size="4" claim-hash-schedule="0 59 23 * * ?" dedup-files="true" hash-type="murmur3_128" log-level="2" max-file-inactive="900" max
-file-write-buffers="1" max-open-files="1024" meta-file-cache="1024" safe-close="true" safe-sync="false" write-threads="8"/>
<permissions default-file="0644" default-folder="0755" default-group="0" default-owner="0"/>

Have a nice day

Marco

Hi there! 

To unsubscribe from this group and stop receiving emails from it, send an email to dedupfilesystem-sdfs-user-discuss+unsubscribe@googlegroups.com.

[David Truog]

Sam - Any ETA on the update?  It has been nearly 3 months now with no update and my volume has a lot of dead space now.  I would just drop and re-create but I do not have sufficient space to store the VMs anywhere else without buying more hardware.

[Stan Wijckmans]

I'm also waiting for this, it's pretty unusable for me without compaction on variable blocks.

Op donderdag 16 april 2015 21:12:54 UTC+2 schreef David Truog: