Page 1 of 1
BTFRS Volume reporting large size of 'Other' as used space
Posted: 13 Nov 2022, 17:11
by Overlawd
Recently purchased a T6-423 (TOS 5.0.176) and created a volume with 6 1TB SSDs - Usable space reported as 4.5 TB. I have created a few shared folders which take a couple hundred GBs, but when checking 'Usage details' for Volume, I see a large section of used space, almost 3TB, being used by 'Others'. What does this 'Other's refer to and any way to recover that some of that used space?
Re: BTFRS Volume reporting large size of 'Other' as used space
Posted: 13 Nov 2022, 18:27
by TMnorah
In addition to shared folders and user directories, the space occupied by applications, file system snapshots, etc. is 'other'.
Re: BTFRS Volume reporting large size of 'Other' as used space
Posted: 13 Nov 2022, 19:00
by Overlawd
Thanks for the reply, but it still seems excessive. I have not enabled system snapshots, only have 3 applications installed and 2 users. I have moved large media files that I had on the system to external storage. Is there a way to view if there are system snapshots stored somewhere?

Re: BTFRS Volume reporting large size of 'Other' as used space
Posted: 14 Nov 2022, 17:00
by TMSupport
Log in to SSH terminal to check the usage details of the volume.
Re: BTFRS Volume reporting large size of 'Other' as used space
Posted: 15 Nov 2022, 14:25
by Overlawd
Hi!
I run the command and it output: 13T .
Does that mean anything?
Re: BTFRS Volume reporting large size of 'Other' as used space
Posted: 15 Nov 2022, 14:39
by Overlawd
Sorry. I had one part of the command missing. On the output from running the full command, I see a folder which seems to be rather large:
6.1T @sysSnapShoot
Re: BTFRS Volume reporting large size of 'Other' as used space
Posted: 15 Nov 2022, 17:19
by TMSupport
The size of the snapshot file is incorrectly calculated.
You can delete snapshot files in TOS Desktop - Backup - File System Snapshot - Snapshot List.
Re: BTFRS Volume reporting large size of 'Other' as used space
Posted: 15 Nov 2022, 22:54
by Overlawd
That solved the problem. Thank you very much!