Replies: 3 comments 1 reply
-
|
You can always list all snapshots of the dataset by From the perspective of "hidden" files, one possibility for pool/eds to have space used but not visible, is that you first copied there data and then created datasets with names matching original directories. In such case data below the children dataset mount points will still be there, but inaccessible. To check that you should be able to unmount the datasets on top manually with umount command and check if there is anything under them. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you amotin. I see below that "pool/eds/video" has a mount point showing the correct USED=24.4T. eds is shorthand for "encrypted data set." Thank you again for your invaluable help. |
Beta Was this translation helpful? Give feedback.
-
|
So if it says 23.9T You could, one imagines, use I would strongly bet, as amotin suggested above, that you have data in folders on |
Beta Was this translation helpful? Give feedback.
-
|
Hello All I unmounted all of the datasets below /mnt/pool/eds to find the following: The above are all folders, not datasets. On day-one, two years ago, I must have created folders in the /mnt/pool/eds dataset only to later discover that folders cannot be replicated. I understand that the [clone-snap, move-data, delete-empty-clone] method I employed did not work but now, I wonder why. Should I have not done [clone-snap, move-data, delete-empty-clone] or was the problem caused by the underlying, same-named folder? I am curious, if the underlying "video" folder did not exist, would the [clone-snap, move-data, delete-empty-clone] method have worked? Originally, I simply deleted the last snapshot, which was auto-created after all of the files in the "video" dataset were deleted, then rebooted. I can now report that the rm was successful. Thank You |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm new to ZFS and really need some help.
My machine:
TrueNAS Core 13.0-U5, 32GB Memory, Xeon E3-1200 4-core, 128K SSD - boot, 12 8TB spinners - pool - RAIDZ2.
There are no user files stored in the "pool" dataset.
Notice that the "pool" dataset has USEDDS=238K which I assume belongs to invisible stuff like snapshots, metadata and I don't know what else.
I assume that USEDDS=238K for the "pool" dataset is probably a normal situation.
There are also no user files stored in the "pool/eds" dataset either.
Notice that "pool/eds" has USEDDS=23.9T which is nowhere near correct.
The USEDCHILD=39.0T is correct. The "pool/eds" child datasets do add up to 39.0T.
I need to find and delete the non-visible USEDDS=23.9T data from the "pool/eds" dataset.
Here is the complete "pool/eds" dataset storage space.
I have searched Google and this forum and have found no answer.
I believe that it is saying that there is 23.9TB of data stored in the "pool/eds" dataset but, ls does not show it.
"ls -a" is supposed to list dot-hidden files and none show up.
"ls -d .*/" also shows no dot-hidden directories in the "pool/eds" dataset.
Although, I do know that "/mnt/pool/eds/.zfs" exists yet, "ls -d .*/" does not show the ".zfs" folder either.
So at this point, I must assume that there is a folder in the "pool/eds" dataset that is also not visible, like ".zfs" is not visible but, consumes 23.9TB of storage space.
I don't know what I'm missing and need a little help.
Here is a description of what I did:
All of the files in /mnt/pool/eds/video had somehow been deleted and an automatic snapshot had already been created after the deletion.
I deleted that current snapshot of the empty /mnt/pool/eds/video dataset.
I cloned a one-day-old snapshot of /mnt/pool/eds/video to /mnt/pool/eds/video-clone.
I ssh'd in, then su - then I mv'd each folder from /mnt/pool/eds/video-clone/folder-name to /mnt/pool/eds/video one folder at a time.
Storage Used rose from 58% to 94% during the move. It took about 28 hours to move the full 23.9TB.
It's surprising to me that it took 28 hours to manipulate the snapshots concerned since, the move created no new actual data.
/mnt/pool/eds/video-clone was emptied and all of the data was correctly moved to /mnt/pool/eds/video.
I then went to the GUI and deleted the empty /mnt/pool/eds/video-clone.
I never made a snapshot of /mnt/pool/eds/video-clone so I expected the Storage Used to return to 58% but, it remained at 94%.
But, obviously, creating the /mnt/pool/eds/video-clone dataset must have created a system default (invisible?) snapshot.
One could create a detailed ZFS dataset structure in TrueNAS and never, ever, create a single snapshot yet the system will still work correctly.
Hence the system must create system default snapshots, even if the admin never purposefully makes any manual or automatic snapshots.
I can find absolutely no information about this, other than "deleting a dataset will also delete all snapshots for the dataset".
I assume that also means that deleting a dataset will also delete the system default snapshot including any other snapshots that were ever created.
It appears that in my case, the system default snapshot of /mnt/pool/eds/video-clone may not have been deleted when the dataset was deleted or the default snapshot was applied to the /mnt/pool/eds dataset when the /mnt/pool/eds/video-clone dataset was deleted.
I automatically make and retain snapshots for one week.
It has now been 10 days since the data move and all snapshots made before the data move have been automatically removed from the system.
I am still stuck at 94% Storage Used.
You can see above that the /mnt/pool/eds dataset shows USEDDS= 23.9T.
23.9TB is the amount of data that was cloned from the /mnt/pool/eds/video snapshot to the temporary /mnt/pool/eds/video-clone dataset.
There is no data in the /mnt/pool/eds dataset, only more datasets that are currently, correctly detailed by the USEDCHILD=39.0T value.
Actually, there never was any data in the /mnt/pool/eds dataset.
Cloning the /mnt/pool/eds/video snapshot to the /mnt/pool/eds/video-clone dataset created a new dataset in /mnt/pool/eds not USEDDS data.
The cloning to a new dataset should have increased USEDCHILD from 39TB to 63TB because the /mnt/pool/eds/video-clone dataset was simply a new dataset added to /mnt/pool/eds.
It was not 23.9TB of raw data added to /mnt/pool/eds, which would increase USEDDS to 23.9TB.
It was 23.9TB added to /mnt/pool/eds in the form of a new dataset /mnt/pool/eds/video-clone, which should have increased USEDCHILD.
I'm stuck here and don't know where to look next.
Thank You
Beta Was this translation helpful? Give feedback.
All reactions