You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A typical snapper config will have this kind of snapshot numbering
# | Type | Pre # | Date | User | Cleanup | Description | Userdata
----+--------+-------+---------------------------------+------+----------+-------------+---------
0 | single | | | root | | current |
33 | single | | Sun 23 Jan 2022 03:01:01 PM +06 | root | timeline | timeline |
34 | single | | Sun 23 Jan 2022 04:01:01 PM +06 | root | timeline | timeline |
The fact that a snapshot is the 34th snapshot taken by snapper doesn't seem to useful in any way.
What could be useful is, if it was numbered from 1 to n ordered by date, such as
# | Type | Pre # | Date | User | Cleanup | Description | Userdata
----+--------+-------+---------------------------------+------+----------+-------------+---------
0 | single | | | root | | current |
1 | single | | Sun 23 Jan 2022 03:01:01 PM +06 | root | timeline | timeline |
2 | single | | Sun 23 Jan 2022 04:01:01 PM +06 | root | timeline | timeline |
I have tried just renaming /.snapshot/# and changing /.snapshot/#/info.xml accordingly, while I can delete as usual using the modified number but that snapshot no longer appears on the output of
snapper -c root list
There could be an option such as
snapper -c root update-numbering
and an option to do this automatically after cleanup
The text was updated successfully, but these errors were encountered:
There are even request to not reuse deleted numbers (see github.com//issues/131).
I can see, this simplifies things for folks doing backup to external drive, but for those using local backup only, keeping the number consecutive is much cleaner and its not like anyone's losing anything, because current method will still be the default and those who want to use deleted numbers will run update-numbering command manually or enable the option to do it after cleanup
For all it's worth, it should be possible to change the numbering as needed. I'd like to have my initial snapshot numbered at 1, following an upgrade for instance. High numbers can become unmanageable so the ability to reset the sequence as needed is crucial. At present, it's not possible without messing with snapper's setup by hand.
A typical snapper config will have this kind of snapshot numbering
The fact that a snapshot is the 34th snapshot taken by snapper doesn't seem to useful in any way.
What could be useful is, if it was numbered from 1 to n ordered by date, such as
I have tried just renaming /.snapshot/# and changing /.snapshot/#/info.xml accordingly, while I can delete as usual using the modified number but that snapshot no longer appears on the output of
There could be an option such as
and an option to do this automatically after cleanup
The text was updated successfully, but these errors were encountered: