Invisible files?

[Kieeps]

so i noticed today that my array named zsas couldnt' create a new VM doe to "not enough space", the array shows as 408GB under node->disks->ZFS and 372GB free...
but when i do:
df -h
i get
zsas 128G 128K 128G 1% /zsas

and that's just not true....

when i run:
zfs list zsas
i get this:
NAME USED AVAIL REFER MOUNTPOINT
zsas 268G 127G 96K /zsas

and thats... wierd...'cus when i go to /zsas the folder is empty.

What am i missing? is this mess intended?

zfs list -r zsas
NAME USED AVAIL REFER MOUNTPOINT
zsas 268G 127G 96K /zsas
zsas/vm-100-disk-0 103G 230G 3.23M -
zsas/vm-106-disk-1 33.0G 160G 2.59M -
zsas/vm-107-disk-0 33.0G 160G 56K -
zsas/vm-107-disk-1 33.0G 143G 16.9G -
zsas/vm-108-disk-0 33.0G 160G 56K -
zsas/vm-108-disk-1 33.0G 142G 18.3G -
(i currently dont even have a VM with id 100, so it would be great to get that removed....if i can find it)

zpool list zsas
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
zsas 408G 35.2G 373G - - 11% 8% 1.00x ONLINE -

 

[aaron]

and thats... wierd...'cus when i go to /zsas the folder is empty.

This is because the subvolumes for VMs are not filesystems (as when used for containers) but ZVOLs, block devices. They show up at /dev/zvol/<pool>/vm-XXX.....

If you really do not have anything on the disk for the not present VM 100 you can destroy it with
zfs destroy zsas/vm-100-disk-0

Do you have any snapshots present? zfs list -t all

Please use the CODE tags for the output of the commands. This makes it much easier to read. You can also format it as code (three dots next to the emoticon button in the editor).

 

[Kieeps]

Sorry for the late response, had some stuff to deal with.

Here is the Output of zfs list -t all

zfs list -t all
NAME                           USED  AVAIL     REFER  MOUNTPOINT
rpool                         41.3G   180G      104K  /rpool
rpool/ROOT                    2.02G   180G       96K  /rpool/ROOT
rpool/ROOT/pve-1              2.02G   180G     2.02G  /
rpool/data                    39.3G   180G       96K  /rpool/data
rpool/data/subvol-169-disk-0  10.1G   140G     10.1G  /rpool/data/subvol-169-disk-0
rpool/data/vm-100-disk-0      12.7G   180G     12.7G  -
rpool/data/vm-100-disk-1      11.6G   180G     11.6G  -
rpool/data/vm-106-disk-0      4.83G   180G     4.83G  -
zsas                           268G   127G       96K  /zsas
zsas/vm-100-disk-0             103G   230G     3.23M  -
zsas/vm-106-disk-1            33.0G   160G     2.59M  -
zsas/vm-107-disk-0            33.0G   160G       56K  -
zsas/vm-107-disk-1            33.0G   143G     16.9G  -
zsas/vm-108-disk-0            33.0G   160G       56K  -
zsas/vm-108-disk-1            33.0G   142G     18.3G  -

sorry for not useing the CODE tag i guess i was in a hurry as always

anway, obviously they are zvol's, i dont know why i didnt think of it. i think i need to read up more on zfs itself, i'm always surprised of how versatile the fs is and most of my questions are related to this it seems, so im sorry if this is very trivial problems

 

[aaron]

Okay, well if all your questions are answered please edit the first post and mark it as solved

If you really have no VM with ID 100 you can destroy the zsas/vm-100-disk-0 zvol.