Reported space discrepency

Joined
Apr 27, 2020
Messages
8
After a little but of help as to what to do here please!

Ended up replicating my 2-day old proof of concept NAS to a new machine after a drive failure on the machine everything was being copied from, so I decided to dump 3x10tb discs in the original server and set up FreeNAS again.

Now, exactly what happened in the restore is honestly a little hazy because I was running on very little sleep. I somehow ended up with 2 copies of my restored data, one of which was removed (an appeared not to be as a result of the snapshot - but who knows)

Anyway!

I've removed the snapshot since the replication is complete and the data is in place, all working as I'd hope and expect. However, right now, the Pools page shows 8.47TB usage.

Code:
Storage                                                   8.49T  9.10T  2.51T  /mnt/Storage
Storage/.system                                           20.3M  9.10T   128K  legacy
Storage/CCTV                                               179M  1024G   179M  /mnt/Storage/CCTV
Storage/Data                                              5.52T  9.10T  5.52T  /mnt/Storage/Data
Storage/TimeMachine                                        451G  1.50T   117K  /mnt/Storage/TimeMachine
Storage/iocage                                            15.4G   500G  6.18M  /mnt/Storage/iocage
Storage/iocage/download                                    289M  9.10T   117K  /mnt/Storage/iocage/download


Adding up what's in use comes to ~6TB
My replication was ~2.54TB

It feels as though with some compression, that difference is the remainder of some replication data somewhere? I removed the snapshot after import, but is there anywhere else this is likely to be? I obviously don't want to lose out on my 2.5TB! Ran a scrub task on the drive too - thinking a scrub task probably does what it sounds like to no avail.

Any ideas? I really have no desire to start again and figure this must be pretty simple for someone who knows what they're doing
 

Attachments

  • Screenshot 2020-04-27 13.37.43.png
    Screenshot 2020-04-27 13.37.43.png
    1.1 MB · Views: 217
  • Screenshot 2020-04-27 13.38.17.png
    Screenshot 2020-04-27 13.38.17.png
    1.1 MB · Views: 204
Joined
Apr 27, 2020
Messages
8
Okay, so far I've learnt that it's referenced data, but I don't know how to remove it.

I think what's happened is that I restored the data as a clone, and copied this to an existing dataset structure I had in place.

I'm guessing I then maybe deleted stuff in the wrong order, so am now left with a 2.5TB reference of data that effectively doesn't now exist.

Is there any way to clear that?
 
Joined
Jan 4, 2014
Messages
1,644
zfs list -o space may reveal the culprit.
 
Joined
Jan 4, 2014
Messages
1,644
To report the space used by individual snapshots zfs list -t snapshot
 
Joined
Apr 27, 2020
Messages
8
As mentioned in the first post, there are no snapshots - it's not quite that easy this time haha.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
That only makes things easier. You surely have files around 2 TB stored directly in the top-level dataset.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
I don't mean to be rude, but have you checked? Something like du -d 3 -t 1G -h /mnt/Poolname | sort -h, either mentally removing the datasets from the output or using the mask option of du.
 
Joined
Apr 27, 2020
Messages
8
I don't mean to be rude, but have you checked? Something like du -d 3 -t 1G -h /mnt/Poolname | sort -h, either mentally removing the datasets from the output or using the mask option of du.

Yes. I did this yesterday. There's nothing on the root of my Storage pool.
 
Joined
Apr 27, 2020
Messages
8
I've created a new snapshot. This new snapshot contains a directory that I deleted - which is the sum of the extra space in use. I'm guessing I must have cleared the snapshot/cloned dataset in the wrong order last time?

If I just destroy the snapshot, it doesn't clear that space, though
 
Joined
Apr 27, 2020
Messages
8
Right - I've solved it. Not entirely sure how it happened.

I had pre-created my Pool and Dataset structure. I then imported from a hard disk whilst replicating from my other FreeNAS box.

After that, as far as I remember, when the dataset from the other NAS was imported.

SOMEHOW, the data from my hard drive import, '3t' ended up in the FOLDER Storage/Data/3t
But, there's a Dataset mounted at Storage/Data. Hence, any attempt to find it through a systemwide du wasn't showing this directory.

I unmounted the Data Dataset, and mv'd the 3t folder, re-mounted Data and am now able to delete it, freeing the space.
 
Top