3. Sia Blocks Space after Failure

Sia Blocks Space after Failure

  • D

    I tried to add a 400gb storage folder on my 1TB SSD, after a few seconds, I got a message,
    2017/06/21 08:39:53.818762 storagefolderadd.go:372: Call to AddStorageFolder has failed: could not allocate storage folder: truncate /Users/username/SIA/siahostdata.dat: no space left on device

    After this, my disk utilities shows me that a huge part of my space is blocked (before ~200gb were used). I already deleted the folder I created with sia-ui. There is no selected folder shown anymore within sia-ui.

    df -h
Filesystem                                              Size   Used  Avail Capacity   iused      ifree %iused  Mounted on
/dev/disk1                                             931Gi  717Gi  214Gi    78%   2956232 4292011047    0%   /

    EDIT:
    I'm currently trying to erase deleted files with diskutil secureErase freespace 1 "/dev/disk1" because it shows the space as deletable in OS X disk utilities. Still I read that this space is backed up, so it's not good to keep 400gb of garbage. I will replay later on the status.

    The space which was prior shown as deletable is now blocked, which slows my mac down.

    EDIT 2:
    I switched off the time machine (which deletes mobile backups) and on again. This or the above erase with a reboot seemed to freed the space again. Can't tell it 100% because I tried several other things also.

    0
  • M

    Did you try just restarting Sia after deleting the file but before erasing and rebooting?

    On Unix systems, space used by deleted files only gets released once the process working on the file releases it, usually when it's shut down, even though the file explorer will not show the file anymore immediately after the delete command.

    0
  • D

    Yes, I deleted the folder, then quit Sia and rebooted. I ran several disk utilities programs and disk cleaners and rebooted again. I disabled the time machine local backups and rebooted. The space switched in-between sometimes from deletable to fully occupied, resulting in a slow system etc. Finally after doing the secureErase and disabling the time machine completely + rebooting the space was free.

    0
Log in to reply