Unalloacating space on a dedupliacted disk V6

[fazekast]

As I correctly understand this is a known issue with deduplicated volumes (in version 6.0), namely that the erased space on the deduped vol could`t be reclaimed.

We are still playing with this ancient version of the sofware in our non-productive environment. I only found a workaround suggesting remigration spdata to a new/temporary file on an "external" physical drive , which allows you to get rid of the trash in the spdata file. The dedupe disk was configured for 5TB - appearing currently as 6,45TB file in the windows filesystem - and unfortunately there is no physical space to expand the affacted volume.

My question Is, if is there any update on this issue yet (a new tool and/or an other better workaround ...)? This time we cant upgrade to V8.

thanks,
tomas.

[Jhon_Smith]

People are using LSFS with in-line dedup now. I don't think that anyone will work on a bug of outdated version these days

[anton (staff)]

V6 is EOL-ed many years ago. Please update to V8 to get the most up-to-date in-line dedupe code being part of LSFS so far.