ZFS pool question

I created a pool the other day. I created a 10 gig files just for a test, then deleted it.

I proceeded to create a few files systems. But for some reason the pool shows 10% full, but the files systems are both at 1%? Both files systems share the same pool.

When I ls -al the pool I just see the file systems.

How can I remove the file I created from the other day?

Thanks

What does

zfs list -t all

say?

zfs list -t all
invalid type 'all'
usage:
        list [-rH] [-o property[,...]] [-t type[,...]] [-s property] ...
            [-S property] ... [filesystem|volume|snapshot] ...
The following properties are supported:
        PROPERTY       EDIT  INHERIT   VALUES
        available        NO       NO   <size>
        compressratio    NO       NO   <1.00x or higher if compressed>
        creation         NO       NO   <date>
        mounted          NO       NO   yes | no
        origin           NO       NO   <snapshot>
        referenced       NO       NO   <size>
        type             NO       NO   filesystem | volume | snapshot
        used             NO       NO   <size>
        aclinherit      YES      YES   discard | noallow | restricted | passthrough | passthrough-x
        aclmode         YES      YES   discard | groupmask | passthrough
        atime           YES      YES   on | off
        canmount        YES       NO   on | off | noauto
        casesensitivity NO      YES   sensitive | insensitive | mixed
        checksum        YES      YES   on | off | fletcher2 | fletcher4 | sha256
        compression     YES      YES   on | off | lzjb | gzip | gzip-[1-9]
        copies          YES      YES   1 | 2 | 3
        devices         YES      YES   on | off
        exec            YES      YES   on | off
        mountpoint      YES      YES   <path> | legacy | none
        nbmand          YES      YES   on | off
        normalization    NO      YES   none | formC | formD | formKC | formKD
        quota           YES       NO   <size> | none
        readonly        YES      YES   on | off
        recordsize      YES      YES   512 to 128k, power of 2
        refquota        YES       NO   <size> | none
        refreservation  YES       NO   <size> | none
        reservation     YES       NO   <size> | none
        setuid          YES      YES   on | off
        shareiscsi      YES      YES   on | off | type=<type>
        sharenfs        YES      YES   on | off | share(1M) options
        sharesmb        YES      YES   on | off | sharemgr(1M) options
        snapdir         YES      YES   hidden | visible
        utf8only         NO      YES   on | off
        version         YES       NO   1 | 2 | 3 | current
        volblocksize     NO      YES   512 to 128k, power of 2
        volsize         YES       NO   <size>
        vscan           YES      YES   on | off
        xattr           YES      YES   on | off
        zoned           YES      YES   on | off
Sizes are specified in bytes with standard units such as K, M, G, etc.
 
User-defined properties can be specified by using a name containing a colon (:).

If I just use zfs list all

NAME               USED  AVAIL  REFER  MOUNTPOINT
glowpool          29.7G   238G  26.6G  /glowpool
glowpool/glows     234M   238G   234M  /glowpool/glows
glowpool/gorking  2.90G   238G  2.90G  /glowpool/gorking

If my previous command didn't work, try this:

zfs list -t filesystem,snapshot,volume

The thing is you probably have snapshot of that deleted file somewhere and that is what consumes space.

What says:

df -k /glowpool /glowpool/glows /glowpool/gorking
ls -al /glowpool /glowpool/glows /glowpool/gorking

No snapshoots at all.

df -k /glowpool /glowpool/glows /glowpool/gorking
 
glowpool 280756224 27845021 241270760 11% /glowpool
glowpool/glows 280756224 6304776 241270760 3% /glowpool/glows
glowpool/gorking 280756224 5335415 241270760 3% /glowpool/gorking
 
ls -al /glowpool
 
/glowpool:
total 69
drwxrwxrwx 4 root sys 4 Nov 3 13:32 .
drwxr-xr-x 40 root root 1024 Nov 5 08:45 ..
drwxrwxrwx 18 webservd webservd 18 Nov 4 09:22 glows
drwxrwxrwx 4 webservd staff 245 Nov 6 09:13 gorking

/glowpool/glows /glowpool/gorking too much to post.

It might be possible that the files you deleted are still open by some process. Alternatively, you might have the glows or gorking mounts being at the same time directories where files are hidden (overlay mount).