linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Noah Massey <noah.massey@gmail.com>, menion@gmail.com
Cc: Chris Murphy <lists@colorremedies.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 14Gb of space lost after distro upgrade on BTFS root partition (long thread with logs)
Date: Tue, 28 Aug 2018 11:47:05 -0400	[thread overview]
Message-ID: <d46b344f-6d03-5425-188d-88e823caa074@gmail.com> (raw)
In-Reply-To: <CADfjVrhcZT1u5uTC4x9XOf2ke+3H+gNH6s-4hufOT1VSkpTGaw@mail.gmail.com>

On 2018-08-28 11:27, Noah Massey wrote:
> On Tue, Aug 28, 2018 at 10:59 AM Menion <menion@gmail.com> wrote:
>>
>> [sudo] password for menion:
>> ID      gen     top level       path
>> --      ---     ---------       ----
>> 257     600627  5               <FS_TREE>/@
>> 258     600626  5               <FS_TREE>/@home
>> 296     599489  5
>> <FS_TREE>/@apt-snapshot-release-upgrade-bionic-2018-08-27_15:29:55
>> 297     599489  5
>> <FS_TREE>/@apt-snapshot-release-upgrade-bionic-2018-08-27_15:30:08
>> 298     599489  5
>> <FS_TREE>/@apt-snapshot-release-upgrade-bionic-2018-08-27_15:33:30
>>
>> So, there are snapshots, right? The time stamp is when I have launched
>> do-release-upgrade, but it didn't ask anything about snapshot, neither
>> I asked for it.
> 
> This is an Ubuntu thing
> `apt show apt-btrfs-snapshot`
> which "will create a btrfs snapshot of the root filesystem each time
> that apt installs/removes/upgrades a software package."
Not Ubuntu, Debian.  It's just that Ubuntu installs and configures the 
package by default, while Debian does not.

This behavior in general is not specific to Debian either, a lot of 
distributions are either working on or already have this type of 
functionality, because it's the only sane and correct way to handle 
updates short of rebuilding the entire system from scratch.
> 
>> During the do-release-upgrade I got some issues due to the (very) bad
>> behaviour of the script in remote terminal, then I have fixed
>> everything manually and now the filesystem is operational in bionic
>> version
>> If it is confirmed, how can I remove the unwanted snapshot, keeping
>> the current "visible" filesystem contents
> 
> By default, the package runs a weekly cron job to cleanup old
> snapshots. (Defaults to 90d, but you can configure that in
> APT::Snapshots::MaxAge) Alternatively, you can cleanup with the
> command yourself. Run `sudo apt-btrfs-snapshot list`, and then `sudo
> apt-btrfs-snapshot delete <snapshot to delete>`

  reply	other threads:[~2018-08-28 19:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  9:34 14Gb of space lost after distro upgrade on BTFS root partition (long thread with logs) Menion
2018-08-28 11:54 ` Qu Wenruo
2018-08-28 13:07   ` Menion
2018-08-28 13:22     ` Qu Wenruo
2018-08-28 13:47 ` Chris Murphy
2018-08-28 14:56   ` Menion
2018-08-28 15:27     ` Noah Massey
2018-08-28 15:47       ` Austin S. Hemmelgarn [this message]
2018-08-28 16:05         ` Noah Massey
2018-08-28 17:07           ` Austin S. Hemmelgarn
2018-08-28 17:25             ` Menion
2018-08-28 18:06               ` Noah Massey
     [not found]                 ` <CAJVZm6dpfQghX+cCo=LkqZMAtFfCMKtq+XHpNGb6wH8z8eMcQA@mail.gmail.com>
2018-08-28 19:47                   ` Austin S. Hemmelgarn
2018-08-29  0:16                   ` Chris Murphy
2018-08-29  0:10     ` Chris Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d46b344f-6d03-5425-188d-88e823caa074@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=menion@gmail.com \
    --cc=noah.massey@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).