USEDDS- can I remove it somehow?

R

ruffpl

Well-Known Member
Jan 11, 2020
37
2
48
40
I have a question about some stuff that are taking space on zfs pool (2x120gb raid 0) where I store my Virtual Machines. I done a little clean up and when I checked content I saw that there was 3 raw vm-100-disks: 10GB+ 20GB+ 50MB ( so total less than 31GB) but when I checked on the graph it showed that 51GB were used. I ussed command to check it " zfs list -t filesystem -o space,mounted" and it shows: 51.3GB USED, 0B USED SNAP, 20.3GB USEDDS, 0B USEDREFRESERV, 31.0GB USEDCHILD, MOUNTED no.
What and how can I (and can I) remove this 20,3GB to get some more free space? I sit some kind of backup of Virtual machine or something that got lost on the disk?
 
Last edited:
can you post the whole zfs list (zfs list -t all) output?
does anything exist in the dataset directly?
 
With added 2 new virtual machines for test today( so it is around 72,1GB, but on the graph it shows 92,56GB used)



root@PROXMOX:~# zfs list -t all
NAME USED AVAIL REFER MOUNTPOINT
STORAGECENTER 16.4T 8.93T 16.4T /STORAGECENTER
VIRTUALCENTER 92.6G 15.0G 20.3G /VIRTUALCENTER
VIRTUALCENTER/vm-100-disk-0 10.3G 24.2G 1.13G -
VIRTUALCENTER/vm-100-disk-1 53.8M 15.0G 28.4M -
VIRTUALCENTER/vm-100-disk-2 20.6G 23.0G 12.6G -
VIRTUALCENTER/vm-101-disk-0 20.6G 27.5G 8.10G -
VIRTUALCENTER/vm-102-disk-0 20.6G 30.2G 5.36G -
rpool 8.24G 5.32G 104K /rpool
rpool/ROOT 8.24G 5.32G 96K /rpool/ROOT
rpool/ROOT/pve-1 8.24G 5.32G 8.24G /
rpool/data 96K 5.32G 96K /rpool/data



Theres are only: dump, images, private, template folders which are empty
 
can you post the output of
Code: 
ls -laR /VIRTUALCENTER
?
 
root@PROXMOX:~# ls -laR /VIRTUALCENTER
/VIRTUALCENTER:
total 11
drwxr-xr-x 6 root root 6 Mar 15 19:29 .
drwxr-xr-x 20 root root 26 Mar 1 11:48 ..
drwxr-xr-x 2 root root 2 Mar 13 07:10 dump
drwxr-xr-x 2 root root 2 Mar 13 07:10 images
drwxr-xr-x 2 root root 2 Mar 13 07:10 private
drwxr-xr-x 4 root root 4 Mar 14 12:04 template

/VIRTUALCENTER/dump:
total 1
drwxr-xr-x 2 root root 2 Mar 13 07:10 .
drwxr-xr-x 6 root root 6 Mar 15 19:29 ..

/VIRTUALCENTER/images:
total 1
drwxr-xr-x 2 root root 2 Mar 13 07:10 .
drwxr-xr-x 6 root root 6 Mar 15 19:29 ..

/VIRTUALCENTER/private:
total 1
drwxr-xr-x 2 root root 2 Mar 13 07:10 .
drwxr-xr-x 6 root root 6 Mar 15 19:29 ..

/VIRTUALCENTER/template:
total 2
drwxr-xr-x 4 root root 4 Mar 14 12:04 .
drwxr-xr-x 6 root root 6 Mar 15 19:29 ..
drwxr-xr-x 2 root root 2 Mar 14 12:04 cache
drwxr-xr-x 2 root root 2 Mar 14 18:12 iso

/VIRTUALCENTER/template/cache:
total 1
drwxr-xr-x 2 root root 2 Mar 14 12:04 .
drwxr-xr-x 4 root root 4 Mar 14 12:04 ..

/VIRTUALCENTER/template/iso:
total 1
drwxr-xr-x 2 root root 2 Mar 14 18:12 .
drwxr-xr-x 4 root root 4 Mar 14 12:04 ..
 
is VIRTUALCENTER mounted?
please post the output of
Code: 
zfs get all VIRTUALCENTER

alternatively, maybe there was a file that got removed but a process still accesses it?
try
Code: 
lsof -n 2>/dev/null | grep VIRTUALCENTER
 
root@PROXMOX:~# zfs get all VIRTUALCENTER
NAME PROPERTY VALUE SOURCE
VIRTUALCENTER type filesystem -
VIRTUALCENTER creation Sun Mar 1 11:46 2020 -
VIRTUALCENTER used 92.6G -
VIRTUALCENTER available 15.0G -
VIRTUALCENTER referenced 20.3G -
VIRTUALCENTER compressratio 1.20x -
VIRTUALCENTER mounted no -
VIRTUALCENTER quota none default
VIRTUALCENTER reservation none default
VIRTUALCENTER recordsize 128K default
VIRTUALCENTER mountpoint /VIRTUALCENTER default
VIRTUALCENTER sharenfs off default
VIRTUALCENTER checksum on default
VIRTUALCENTER compression on local
VIRTUALCENTER atime on default
VIRTUALCENTER devices on default
VIRTUALCENTER exec on default
VIRTUALCENTER setuid on default
VIRTUALCENTER readonly off default
VIRTUALCENTER zoned off default
VIRTUALCENTER snapdir hidden default
VIRTUALCENTER aclinherit restricted default
VIRTUALCENTER createtxg 1 -
VIRTUALCENTER canmount on default
VIRTUALCENTER xattr on default
VIRTUALCENTER copies 1 default
VIRTUALCENTER version 5 -
VIRTUALCENTER utf8only off -
VIRTUALCENTER normalization none -
VIRTUALCENTER casesensitivity sensitive -
VIRTUALCENTER vscan off default
VIRTUALCENTER nbmand off default
VIRTUALCENTER sharesmb off default
VIRTUALCENTER refquota none default
VIRTUALCENTER refreservation none default
VIRTUALCENTER guid 3348856757066965362 -
VIRTUALCENTER primarycache all default
VIRTUALCENTER secondarycache all default
VIRTUALCENTER usedbysnapshots 0B -
VIRTUALCENTER usedbydataset 20.3G -
VIRTUALCENTER usedbychildren 72.3G -
VIRTUALCENTER usedbyrefreservation 0B -
VIRTUALCENTER logbias latency default
VIRTUALCENTER objsetid 54 -
VIRTUALCENTER dedup off default
VIRTUALCENTER mlslabel none default
VIRTUALCENTER sync standard default
VIRTUALCENTER dnodesize legacy default
VIRTUALCENTER refcompressratio 1.18x -
VIRTUALCENTER written 20.3G -
VIRTUALCENTER logicalused 57.2G -
VIRTUALCENTER logicalreferenced 24.0G -
VIRTUALCENTER volmode default default
VIRTUALCENTER filesystem_limit none default
VIRTUALCENTER snapshot_limit none default
VIRTUALCENTER filesystem_count none default
VIRTUALCENTER snapshot_count none default
VIRTUALCENTER snapdev hidden default
VIRTUALCENTER acltype off default
VIRTUALCENTER context none default
VIRTUALCENTER fscontext none default
VIRTUALCENTER defcontext none default
VIRTUALCENTER rootcontext none default
VIRTUALCENTER relatime off default
VIRTUALCENTER redundant_metadata all default
VIRTUALCENTER overlay off default
VIRTUALCENTER encryption off default
VIRTUALCENTER keylocation none default
VIRTUALCENTER keyformat none default
VIRTUALCENTER pbkdf2iters 0 default
VIRTUALCENTER special_small_blocks 0 default
 
ruffpl said:
VIRTUALCENTER mounted no -
Click to expand...
it is not mounted, so the 'ls' from above is not showing the content of the zpool

try mounting it and then check whats inside
 
Thanks for help. Can I mount it to folder or some other way? I am using this whole pool right now with virtual machines/ will this cause any problem?
 
ruffpl said:
Thanks for help. Can I mount it to folder or some other way? I am using this whole pool right now with virtual machines/ will this cause any problem?
Click to expand...

no mounting should not make any problems, check 'man zfs' for details about mounting a dataset
 
I got:

root@PROXMOX:~# zfs mount VIRTUALCENTER
cannot mount '/VIRTUALCENTER': directory is not empty
 
yes you cannot mount it if the directory is not empty -> remove the directories inside (its ok since they are empty anyway)
 
Thanks. It helped. After removing old empty folders, mount pool and reebot I got new folders with backup and couple iso files that was on old directory that I removed by proxmox menu, but did not removed files.
 
You must log in or register to reply here.
Top Bottom