snapshots created without task defined

gork1337

Cadet
Joined
Jan 29, 2022
Messages
3
Heya

I tried search for it, but couldn't come up with any solution :(
Maybe I searched for the wrong terms, so excuse me if this has already been solved somewhere

I'm running TrueNAS for many years on the same machine and did regular updates, now I'm at 12.0-U7
My problem is, that snapshots are being created frequently and never deleted which will fill up my disks.
There are no Tasks defined (or none that I could find) that do those snaphshots.
I wasn't able to find out where in the system files such a task may be created and now I don't really know what to do, apart from deleting those snapshot every now and then, as I do not have a use for them and don't want them to be created:

My problem is whit the timemachine-dataset@aapltm snapshots
Code:
root@freenas[/etc]# zfs list -t snapshot
NAME                                                     USED  AVAIL     REFER  MOUNTPOINT
boot-pool/ROOT/12.0-U7@2021-02-16-11:53:21              1.65M      -     1.16G  -
boot-pool/ROOT/12.0-U7@2021-03-28-12:11:55              1.75M      -     1.16G  -
boot-pool/ROOT/12.0-U7@2021-08-01-22:01:01              1.15G      -     1.15G  -
boot-pool/ROOT/12.0-U7@2021-11-15-16:37:49              1.18G      -     1.18G  -
boot-pool/ROOT/12.0-U7@2021-12-21-10:09:54              1.18G      -     1.18G  -
zfs/.system/samba4@update--2020-11-21-14-11--11.3-U4.1   320K      -      355K  -
zfs/.system/samba4@update--2021-03-28-10-46--12.0-U2     296K      -      575K  -
zfs/.system/samba4@update--2021-08-01-20-47--12.0-U2.1   296K      -      575K  -
zfs/.system/samba4@update--2021-11-15-16-02--12.0-U4.1   151K      -      599K  -
zfs/.system/samba4@wbc-1636992806                        174K      -      587K  -
zfs/.system/samba4@wbc-1639146538                        285K      -      587K  -
zfs/.system/samba4@update--2021-12-21-09-37--12.0-U6.1   169K      -      599K  -
zfs/.system/samba4@wbc-1640080051                        145K      -      575K  -
zfs/.system/samba4@wbc-1642887519                        267K      -      599K  -
zfs/timemachine-dataset@aapltm-1643404211               2.41G      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643407541               43.1M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643408277               9.80M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643408826                593K      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643410160                187M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643415351               22.0M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643417787               1.40M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643418204               74.9M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643439899                354M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643443500                323M      -     1.89T  -
zfs/timemachine-dataset@aapltm-1643451523                  0B      -     1.89T  -


Any hint as to where I can find the task / job that creates those snapshots?
interestingly the snapshots are only created for my TimeMachine dataset, the other datasets are not being snapshot

Sorry for attaching so many files, I'm not sure which ones are needed :)

Any help is appreciated!
 

Attachments

  • Untitled.jpg
    Untitled.jpg
    143.5 KB · Views: 142
  • Untitled 2.jpg
    Untitled 2.jpg
    41.8 KB · Views: 148
  • Untitled 3.jpg
    Untitled 3.jpg
    33.8 KB · Views: 138
  • Untitled 4.jpg
    Untitled 4.jpg
    35.5 KB · Views: 126
  • Untitled21.jpg
    Untitled21.jpg
    67.4 KB · Views: 156
  • Untitled 22.jpg
    Untitled 22.jpg
    87.7 KB · Views: 158

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Any hint as to where I can find the task / job that creates those snapshots?
The biggest/only hint is appltm... that's apple TimeMachine.

If you set the share as the type Multi-User Time Machine and/or started using it as a Time Machine target from a Mac, you will get snapshots. It's by design (and automatic in the background, there's no option to turn it off).
 

gork1337

Cadet
Joined
Jan 29, 2022
Messages
3
thanks for the quick reply!
Ok, if it is by design, then I am wondering why they 'overflow' and fill up the hole system?
Or is it my mistake, as the quota is larger than free space?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Have a look at this thread...

 

gork1337

Cadet
Joined
Jan 29, 2022
Messages
3
thanks for the link!
Neat trick to enable snapshots in case the sparsebundle ever gets corrupted (or at least when mac os is complaining)
but the lack of documentation made me make this thread ;)

thanks again for your help!
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
In next SCALE release and TrueNAS 13 release we'll have improved heuristics for determining whether time machine backup was completed during an SMB session.
https://github.com/truenas/samba/commit/a7c4ed89c87a96bd2c180914c2c8f51fff6333b5 in practice this reduced number of snapshots to once per day per time machine client.
 

bearattack11

Dabbler
Joined
Jan 1, 2021
Messages
11
Is there anyway to control the retention on these snapshots? I’ve tried to add the parameter “tmprotect:retention = 5” but it seems the snapshots are persisting longer…
 

stillka

Explorer
Joined
Nov 15, 2014
Messages
55
In next SCALE release and TrueNAS 13 release we'll have improved heuristics for determining whether time machine backup was completed during an SMB session.
https://github.com/truenas/samba/commit/a7c4ed89c87a96bd2c180914c2c8f51fff6333b5 in practice this reduced number of snapshots to once per day per time machine client.
I am not using time machine, only standards SMB shares ("no preset", no "time machine" enabled) and I see it also, not in gui but in cli:

root@truenas[~]# zfs list -t snapshot | grep samba
vg_data/.system/samba4@wbc-1633554652 196K - 2.33M -
vg_data/.system/samba4@wbc-1633555227 196K - 2.33M -
vg_data/.system/samba4@wbc-1634301643 192K - 2.33M -
vg_data/.system/samba4@wbc-1634306930 192K - 2.33M -
vg_data/.system/samba4@wbc-1634316532 200K - 2.33M -
vg_data/.system/samba4@wbc-1634376583 200K - 2.33M -
vg_data/.system/samba4@wbc-1634392496 200K - 2.33M -
vg_data/.system/samba4@wbc-1634444660 208K - 2.33M -
vg_data/.system/samba4@wbc-1634933792 224K - 2.33M -
vg_data/.system/samba4@wbc-1636264437 200K - 2.33M -
vg_data/.system/samba4@wbc-1636280244 200K - 2.33M -
vg_data/.system/samba4@wbc-1636286192 200K - 2.33M -
vg_data/.system/samba4@wbc-1636356395 200K - 2.33M -
vg_data/.system/samba4@wbc-1636363190 200K - 2.33M -
vg_data/.system/samba4@wbc-1636831096 184K - 2.33M -
vg_data/.system/samba4@wbc-1636832062 184K - 2.33M -
vg_data/.system/samba4@wbc-1636965532 192K - 2.33M -
vg_data/.system/samba4@wbc-1636966819 192K - 2.33M -
vg_data/.system/samba4@wbc-1637059530 192K - 2.33M -
vg_data/.system/samba4@wbc-1637060207 192K - 2.33M -
vg_data/.system/samba4@wbc-1637060932 184K - 2.33M -
vg_data/.system/samba4@wbc-1637065851 192K - 2.33M -
vg_data/.system/samba4@wbc-1637078099 184K - 2.33M -
vg_data/.system/samba4@wbc-1637078750 192K - 2.33M -
vg_data/.system/samba4@wbc-1637079618 192K - 2.33M -
vg_data/.system/samba4@wbc-1637080535 192K - 2.33M -
vg_data/.system/samba4@wbc-1637084749 200K - 2.33M -
vg_data/.system/samba4@wbc-1637091853 200K - 2.33M -
vg_data/.system/samba4@wbc-1637141713 208K - 2.33M -
vg_data/.system/samba4@wbc-1639009650 184K - 2.33M -
vg_data/.system/samba4@wbc-1639010114 184K - 2.33M -
vg_data/.system/samba4@wbc-1639869187 232K - 2.33M -
vg_data/.system/samba4@wbc-1640502225 200K - 2.33M -
vg_data/.system/samba4@wbc-1640519465 192K - 2.33M -
vg_data/.system/samba4@wbc-1640522694 192K - 2.33M -
vg_data/.system/samba4@wbc-1640532092 176K - 2.33M -
vg_data/.system/samba4@wbc-1640533233 176K - 2.33M -
vg_data/.system/samba4@wbc-1641228312 232K - 2.33M -
vg_data/.system/samba4@wbc-1643873853 208K - 2.29M -
vg_data/.system/samba4@wbc-1644011450 208K - 2.29M -
vg_data/.system/samba4@wbc-1644107246 184K - 2.29M -
vg_data/.system/samba4@wbc-1644107951 184K - 2.29M -
vg_data/.system/samba4@wbc-1648966917 224K - 2.35M -
vg_data/.system/samba4@wbc-1649173912 152K - 2.35M -
vg_data/.system/samba4@wbc-1649177471 152K - 2.35M -
vg_data/.system/samba4@wbc-1650034930 152K - 2.35M -
vg_data/.system/samba4@wbc-1650035571 152K - 2.35M -
vg_data/.system/samba4@wbc-1650035845 192K - 2.35M -
vg_data/.system/samba4@wbc-1652300212 136K - 2.35M -
vg_data/.system/samba4@wbc-1652301124 128K - 2.35M -
vg_data/.system/samba4@wbc-1652302049 152K - 2.35M -
vg_data/.system/samba4@wbc-1657137223 256K - 2.33M -
vg_data/.system/samba4@wbc-1660288066 224K - 2.32M -
vg_data/.system/samba4@wbc-1661418759 232K - 2.41M -
vg_data/.system/samba4@update--2022-09-01-08-33--13.0-U1.1 128K - 2.42M -
vg_data/.system/samba4@wbc-1662021444 112K - 2.41M -
vg_data/.system/samba4@wbc-1662022020 128K - 2.41M -
vg_data/.system/samba4@wbc-1662023061 144K - 2.41M -
vg_data/.system/samba4@wbc-1663102758 152K - 2.40M -
vg_data/.system/samba4@wbc-1663103876 152K - 2.40M -
vg_data/.system/samba4@wbc-1664617302 152K - 2.39M -
vg_data/.system/samba4@wbc-1664618535 152K - 2.39M -
vg_data/.system/samba4@update--2022-10-01-10-27--13.0-U2 136K - 2.39M -
vg_data/.system/samba4@wbc-1664620430 112K - 2.39M -
vg_data/.system/samba4@update--2022-10-01-12-30--SCALE-22.02.4 132K - 2.40M -
vg_data/.system/samba4@update--2022-10-01-12-45--SCALE-22.02.4 132K - 2.40M -
vg_data/.system/samba4@wbc-1664660480 152K - 2.40M -
vg_data/.system/samba4@wbc-1664661695 164K - 2.40M -
vg_data/.system/samba4@wbc-1664698288 168K - 2.40M -
vg_data/.system/samba4@wbc-1664951702 144K - 2.41M -
vg_data/.system/samba4@wbc-1664952981 156K - 2.41M -
vg_data/.system/samba4@wbc-1665234126 172K - 2.41M -
vg_data/.system/samba4@wbc-1665250091 164K - 2.41M -
vg_data/.system/samba4@wbc-1665251574 164K - 2.41M -
vg_data/.system/samba4@wbc-1667036335 140K - 2.41M -
vg_data/.system/samba4@update--2022-10-29-19-56--SCALE-22.02.4 156K - 2.42M -

Any way how to get rid of this "feature"?

Thanks.
 
Top