SOLVED Missing half my space? Just got out of space warning

[Dirk]

This latest install has given me no end of heartburn.

Older machine was re-tasked for different media. The 5 2TB drives are in Z2 and a sixth as hot spare. I come up with about 5.2 usable and according to the ZFS calculators that's about right.

The out of space warning was a surprise and not sure where the space went. I've checked datasets and the one media dataset is where it should be at about 2.7TB. Where did the rest go? Jails and other datasets are tiny in comparison. I checked snapshots but nothing amiss. So something is tying up about 2.5TB

I would appreciate any help asapas I certainly don't want to crash the system with 1.3GB of free space.

zfs list -o space

Code:

Welcome to TrueNAS

Warning: settings changed through the CLI are not written to
the configuration database and will be reset on reboot.

root@Brutus[~]# zfs list -o space
NAME                                                        AVAIL   USED  USEDSNAP  USEDDS  USEDREFRESERV  USEDCHILD
boot-pool                                                   26.3G  2.32G0B     24K             0B      2.32G
boot-pool/.system                                           26.3G  2.23M0B     26K             0B      2.21M
boot-pool/.system/configs-5b73e8a039ec468ca0e6b8af17a87983  26.3G    24K0B     24K             0B         0B
boot-pool/.system/cores                                     1024M   501K0B    501K             0B         0B
boot-pool/.system/rrd-5b73e8a039ec468ca0e6b8af17a87983      26.3G  1.54M0B   1.54M             0B         0B
boot-pool/.system/samba4                                    26.3G    45K0B     45K             0B         0B
boot-pool/.system/services                                  26.3G    24K0B     24K             0B         0B
boot-pool/.system/syslog-5b73e8a039ec468ca0e6b8af17a87983   26.3G  67.5K0B   67.5K             0B         0B
boot-pool/.system/webui                                     26.3G    24K0B     24K             0B         0B
boot-pool/ROOT                                              26.3G  2.31G0B     24K             0B      2.31G
boot-pool/ROOT/12.0-U2.1                                    26.3G  2.31G     1.16G   1.15G             0B         0B
boot-pool/ROOT/Initial-Install                              26.3G  1.74M0B   1.74M             0B         0B
boot-pool/ROOT/default                                      26.3G   285K0B    285K             0B         0B
mainpool                                                    1.35G  5.20T0B   2.45T             0B      2.75T
mainpool/.system                                            1.35G  34.7M0B    213K             0B      34.5M
mainpool/.system/configs-5b73e8a039ec468ca0e6b8af17a87983   1.35G  1.73M0B   1.73M             0B         0B
mainpool/.system/cores                                      1024M   170K0B    170K             0B         0B
mainpool/.system/rrd-5b73e8a039ec468ca0e6b8af17a87983       1.35G  30.9M0B   30.9M             0B         0B
mainpool/.system/samba4                                     1.35G   440K      128K    312K             0B         0B
mainpool/.system/services                                   1.35G   170K0B    170K             0B         0B
mainpool/.system/syslog-5b73e8a039ec468ca0e6b8af17a87983    1.35G   902K0B    902K             0B         0B
mainpool/.system/webui                                      1.35G   170K0B    170K             0B         0B
mainpool/iocage                                             1.35G  6.91G0B   8.79M             0B      6.90G
mainpool/iocage/download                                    1.35G   402M0B    170K             0B       402M
mainpool/iocage/download/12.2-RELEASE                       1.35G   402M0B    402M             0B         0B
mainpool/iocage/images                                      1.35G  1.21G0B   1.21G             0B         0B
mainpool/iocage/jails                                       1.35G  3.49G0B    185K             0B      3.49G
mainpool/iocage/jails/Emby                                  1.35G  1.37G0B    199K             0B      1.37G
mainpool/iocage/jails/Emby/root                             1.35G  1.37G0B   1.37G             0B         0B
mainpool/iocage/jails/sabnzbd                               1.35G  1.16G0B    199K             0B      1.16G
mainpool/iocage/jails/sabnzbd/root                          1.35G  1.16G0B   1.16G             0B         0B
mainpool/iocage/jails/sonarr                                1.35G   985M0B    199K             0B       985M
mainpool/iocage/jails/sonarr/root                           1.35G   985M0B    985M             0B         0B
mainpool/iocage/log                                         1.35G   206K0B    206K             0B         0B
mainpool/iocage/releases                                    1.35G  1.81G0B    170K             0B      1.81G
mainpool/iocage/releases/12.2-RELEASE                       1.35G  1.81G0B    170K             0B      1.81G
mainpool/iocage/releases/12.2-RELEASE/root                  1.35G  1.81G     22.0M   1.79G             0B         0B
mainpool/iocage/templates                                   1.35G   170K0B    170K             0B         0B
mainpool/media                                              1.35G  2.74T0B   2.74T             0B         0B
root@Brutus[~]#

 

[SweetAndLow]

All your data is in your main pool. Probably in the folder where you mounted your media dataset over it

 

[HoneyBadger]

Your mainpool/media dataset has a usedsnap value of 2.74T - did you take one very early on in the pool's lifetime and never delete it?

Drop a zfs list -t snapshot output in CODE blocks please.

 

[Dirk]

Sweetnlow. I'm looking for duplicates, but can't find any. I have some mount points but don't see a duplicate media or tv-shows data

HoneyBadger (is that from the famous YouTube video?) Snapshots was about the first place I looked and deleted all but the small one for the jails. But I see it's not released.

Going down for another reboot.

Code:

root@Brutus[~]# zfs list -t snapshot
NAME                                                        USED  AVAIL     REFER  MOUNTPOINT
boot-pool/ROOT/12.0-U2.1@2021-02-16-05:30:15               1.73M      -     1.16G  -
boot-pool/ROOT/12.0-U2.1@2021-02-23-15:04:08               1.82M      -     1.16G  -
mainpool/.system/samba4@update--2021-02-23-23-05--12.0-U2   128K      -      312K  -
mainpool/iocage/releases/12.2-RELEASE/root@sabnzbd          241K      -     1.79G  -
mainpool/iocage/releases/12.2-RELEASE/root@Emby             241K      -     1.79G  -
mainpool/iocage/releases/12.2-RELEASE/root@sonarr           227K      -     1.79G  -

 

[Dirk]

Solved"
There was indeed another directory created by rsysnc module setup. I created it to keep things fresh while I got the server set up. However, instead of syncing the data to /media/tv-shows it went to /backup (the name of the module). Was using module due to everything being on the local lan. Will have to read further.
Where I got double bit was I use Winscp to motor around and from my Win 10 client and it does not refresh the directory structure even if you go in and out of the directory. You have to click a refresh and that revealed the directory. Then to be trippli bit, you can see the zfs list showed no backup directory (that part I find odd).

Thank you for the help in tracking it down. I'm not sure of the mechanics of this forum does it provide a "SOLVED" option?

 

[HoneyBadger]

I believe you can edit your first post and select the [SOLVED] tag as a flair.

The /backup directory was considered a sub-directory on the mainpool root, so it wasn't being identified as a separate dataset. Strange about the WinSCP refresh behavior, you'd think it would want to pull an fresh ls each time.

(And yes, the name is a reference to the infamous YouTube video. This honey badger do care though, especially about the safety of people's data.)

 

[Tigersharke]

Actually a prefix, and done but I think it may be 'edit thread' as thats what it is for me to make the adjustment. Although yes, you'd need to scroll up to show the option to edit in the menu the way things work on these forums it scrolls off the top.

 

[Dirk]

I believe you can edit your first post and select the [SOLVED] tag as a flair.

The /backup directory was considered a sub-directory on the mainpool root, so it wasn't being identified as a separate dataset. Strange about the WinSCP refresh behavior, you'd think it would want to pull an fresh ls each time.

(And yes, the name is a reference to the infamous YouTube video. This honey badger do care though, especially about the safety of people's data.)

Thanks badger. Yes it is odd about the Winscp not doing a represh. When you think about it the directory had been there fore days, yet not visible to me bouncing all over the file structure trying to find where the space went.

Makes sense that the zfs list did not show the directory if it's purpose was to show datasets.
Long live the honeybadger!

 

[Dirk]

Actually a prefix, and done but I think it may be 'edit thread' as thats what it is for me to make the adjustment. Although yes, you'd need to scroll up to show the option to edit in the menu the way things work on these forums it scrolls off the top.

Thanks Tiger. Truenas, Sonarr, and Emby forums have always been good to me and I try to give back. And thanks for updating the title.