Deleting iSCSI LUN did not free my disk space

This issue is fixed in the next release 6.2.0. Once that release is available please let us know if you run into the issue again.

I had a large (3TB) iSCSI LUN on one of my RN314s (equipped with 4 2 TB drives) that I deleted, and ReadyNAS is not showing the space as available. I have scrubbed and defragged. The iSCSI lun was called Javelin_Migration. I noticed the following while searching the filesystem (note the bold, underlined text):

root@lestatnas2:/data/.purge# ls -tlr
total 0
drwxr-xr-x 1 root root 32 Jun 14 2014 1432681732_Javelin_Migration
root@lestatnas2:/data/.purge# du -k -s * | sort -n
3221225480 1432681732_Javelin_Migration
root@lestatnas2:/data/.purge# cd 1432681732_Javelin_Migration/
root@lestatnas2:/data/.purge/1432681732_Javelin_Migration# ls
root@lestatnas2:/data/.purge/1432681732_Javelin_Migration# ls -tlr
total 0
root@lestatnas2:/data/.purge/1432681732_Javelin_Migration# ls -la
total 0
drwxr-xr-x 1 root root 32 Jun 14 2014 .
drwxr-xr-x 1 root root 56 May 26 18:08 ..
drwxr-xr-x 1 root root 74 Jun 14 2014 .iscsi
root@lestatnas2:/data/.purge/1432681732_Javelin_Migration# cd .iscsi/
root@lestatnas2:/data/.purge/1432681732_Javelin_Migration/.iscsi# ls
iscsi_lun_backing_store
root@lestatnas2:/data/.purge/1432681732_Javelin_Migration/.iscsi# ls -tlr
total 3221225476
-rw-r--r-- 1 root root 3298534883840 May 25 22:32 iscsi_lun_backing_store
root@lestatnas2:/data/.purge/1432681732_Javelin_Migration/.iscsi#


Why is this data lingering, and can I just delete it? I'd rather not format the drives if I can avoid it. I absolutely intend for this LUN and all backups, data, etc to be deleted.

Thanks for your help!

Which firmware are you running?

The latest: version 6.2.4

mdgm wrote:
Which firmware are you running?

The latest: Version 6.2.4

Can you send me your logs (see the Sending Logs link in my sig).

Please also check your PM inbox.

mdgm wrote:
Can you send me your logs (see the Sending Logs link in my sig). Please also check your PM inbox.

Logs emailed

Looks like there was quite a bit going on here.

A downgrade to 6.1.6 from 6.2.3 when doing a migration from an ARM box to a OS6 box which left the snapshots unable to be deleted from the web interface.

Deleting the LUN from the backend that failed to finish being deleted worked. Deleting the snapshots from the backend worked as well.

Started a volume balance. The system should be fine now, but as I mentioned on the remote session, considering all that's happened and that the system was setup on 6.0.0 I think there would be some benefit to

1. Backing up your data
2. Verifying backup is successful
3. Doing a factory default (wipes all data, settings, everything)
4. Restore data from backup

mdgm wrote:
Can you send me your logs (see the Sending Logs link in my sig). Please also check your PM inbox.

Thanks for your help!