Results 1 to 3 of 3

Thread: snapper cleanup number

  1. #1
    Join Date
    Jun 2016
    Posts
    26

    Question snapper cleanup number

    Hi,
    I recently had a my / run out of space due to snapper snapshots. I then manually deleted a bunch to make space, but I know there is the
    Code:
    snapper cleanup
    command. I tried running it with the <number> cleanup algorithm and got the following output:
    Code:
    Venus:~ # snapper -v cleanup number
    Deleting snapshot from root:
    1
    Deleting snapshot failed.
    Here is my snapper config for root:
    Code:
    Venus:~ # snapper get-config
    Key                    | Value
    -----------------------+------
    ALLOW_GROUPS           |      
    ALLOW_USERS            |      
    BACKGROUND_COMPARISON  | yes  
    EMPTY_PRE_POST_CLEANUP | yes  
    EMPTY_PRE_POST_MIN_AGE | 1800 
    FSTYPE                 | btrfs
    NUMBER_CLEANUP         | yes  
    NUMBER_LIMIT           | 2-10 
    NUMBER_LIMIT_IMPORTANT | 4-10 
    NUMBER_MIN_AGE         | 1800 
    QGROUP                 | 1/0  
    SPACE_LIMIT            | 0.5  
    SUBVOLUME              | /    
    SYNC_ACL               | no   
    TIMELINE_CLEANUP       | yes  
    TIMELINE_CREATE        | no   
    TIMELINE_LIMIT_DAILY   | 10   
    TIMELINE_LIMIT_HOURLY  | 10   
    TIMELINE_LIMIT_MONTHLY | 10   
    TIMELINE_LIMIT_WEEKLY  | 0    
    TIMELINE_LIMIT_YEARLY  | 10   
    TIMELINE_MIN_AGE       | 1800
    More information:
    Code:
    Venus:~ # snapper --version
    snapper 0.5.1
    flags btrfs,lvm,no-ext4,xattrs,rollback,btrfs-quota,no-selinux
    As far as I understand it, snapshots 0 and 1 can't be removed and that is why it fails. But why does it try to delete snapshot number 1? Shouldn't that be excluded from the cleanup? I did use "snapper rollback" before on this installation, maybe that has something to do with it?

    merk

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,832
    Blog Entries
    15

    Default Re: snapper cleanup number

    Quote Originally Posted by merk View Post
    As far as I understand it, snapshots 0 and 1 can't be removed and that is why it fails. But why does it try to delete snapshot number 1? Shouldn't that be excluded from the cleanup? I did use "snapper rollback" before on this installation, maybe that has something to do with it?
    Hi
    Yes, AFAIK the rollback is the new starting point. Consider modifying you /etc/snapper/configs/root to reduce snapshots (I only keep max 4) then use the cron job manually to clean up snapshots and then run the btrfs balance cron job as well to clean up space.
    Code:
    /etc/cron.daily/suse.de-snapper
    /etc/cron.weekly/btrfs-balance
    Also check the status of the btrfs-balance service;
    Code:
    systemctl status btrfsmaintenance-refresh.service
    Last edited by malcolmlewis; 29-Aug-2017 at 06:59.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3
    Join Date
    Jun 2016
    Posts
    26

    Default Re: snapper cleanup number

    Thank you, I will try that as soon as I am back home.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •