Mark Schouten wrote:
>>> [root@storage ~]# zfs list -o name,used,referenced,usedbychildren,usedbydataset,usedbysnapshots,available,mountpoint,quota,reserv,refquota,refreserv "$@" | sed -r "s/none/ -/g"
>>> NAME USED REFER USEDCHILD USEDDS USEDSNAP AVAIL MOUNTPOINT QUOTA RESERV REFQUOTA REFRESERV
>>> storage 1.60T 431G 1.18T 431G 0 138G /storage - - - -
>>> storage/av.https-ict.nl..OS 20G 16K 0 16K 0 158G - - - - 20G
>>> storage/bestandonline.https-ict.nl.OS 20G 16K 0 16K 0 158G - - - - 20G
>>
>> Let's take this one for example. It's not mounted! It shouldn't be
>> listed in next command output.
>
> They are zvols, they shouldn't be mounted. They're exported by iscsitgt as devices.
As they are zvols they do exists at /dev/zvol/storage/ and not
/storage/. Where did all that files came from?
Can you post your iscsitgt setup?
>
>> This is not a zfs dataset. This is a file. It has no relevance to named
>> dataset. And it drains space from /storage.
>
> That's absolutely true. There are indeed three files that could be removed.
> bestandonline.https-ict.nl.DATA
> documentatievm.https-ict.nl
> testvm1.https-ict.nl
>
> But still, there is only 16K referenced by the zvols...
>
--
Sphinx of black quartz judge my vow.