On Tue, Aug 28, 2018 at 1:14 PM, Menion wrote:
> You are correct, indeed in order to cleanup you need
>
> 1) someone realize that snapshots have been created
> 2) apt-brtfs-snapshot is manually installed on the system
>
> Assuming also that the snapshots created during do-release-upgrade are
>
On Tue, Aug 28, 2018 at 8:56 AM, Menion wrote:
> [sudo] password for menion:
> ID gen top level path
> -- --- -
> 257 600627 5 /@
> 258 600626 5 /@home
> 296 599489 5
>
On 2018-08-28 15:14, Menion wrote:
You are correct, indeed in order to cleanup you need
1) someone realize that snapshots have been created
2) apt-brtfs-snapshot is manually installed on the system
Your second requirement is only needed if you want the nice automated
cleanup. There's
On Tue, Aug 28, 2018 at 1:25 PM Menion wrote:
>
> Ok, I have removed the snapshot and the free expected space is here, thank
> you!
> As a side note: apt-btrfs-snapshot was not installed, but it is
> present in Ubuntu repository and I have used it (and I like the idea
> of automatic snapshot
Ok, I have removed the snapshot and the free expected space is here, thank you!
As a side note: apt-btrfs-snapshot was not installed, but it is
present in Ubuntu repository and I have used it (and I like the idea
of automatic snapshot during upgrade)
This means that the do-release-upgrade does
On 2018-08-28 12:05, Noah Massey wrote:
On Tue, Aug 28, 2018 at 11:47 AM Austin S. Hemmelgarn
wrote:
On 2018-08-28 11:27, Noah Massey wrote:
On Tue, Aug 28, 2018 at 10:59 AM Menion wrote:
[sudo] password for menion:
ID gen top level path
-- --- -
On Tue, Aug 28, 2018 at 11:47 AM Austin S. Hemmelgarn
wrote:
>
> On 2018-08-28 11:27, Noah Massey wrote:
> > On Tue, Aug 28, 2018 at 10:59 AM Menion wrote:
> >>
> >> [sudo] password for menion:
> >> ID gen top level path
> >> -- --- -
> >> 257
On 2018-08-28 11:27, Noah Massey wrote:
On Tue, Aug 28, 2018 at 10:59 AM Menion wrote:
[sudo] password for menion:
ID gen top level path
-- --- -
257 600627 5 /@
258 600626 5 /@home
296 599489 5
On Tue, Aug 28, 2018 at 10:59 AM Menion wrote:
>
> [sudo] password for menion:
> ID gen top level path
> -- --- -
> 257 600627 5 /@
> 258 600626 5 /@home
> 296 599489 5
>
[sudo] password for menion:
ID gen top level path
-- --- -
257 600627 5 /@
258 600626 5 /@home
296 599489 5
/@apt-snapshot-release-upgrade-bionic-2018-08-27_15:29:55
297 599489 5
On Tue, Aug 28, 2018 at 3:34 AM, Menion wrote:
> Hi all
> I have run a distro upgrade on my Ubuntu 16.04 that runs ppa kernel
> 4.17.2 with btrfsprogs 4.17.0
> The root filesystem is BTRFS single created by the Ubuntu Xenial
> installer (so on kernel 4.4.0) on an internal mmc, located in
>
On 2018/8/28 下午9:07, Menion wrote:
> Ok, thanks for your replay
> This is a root FS, how can I defragment it?
If it's a rootfs, then it's a little strange.
Normally package manager should overwrite the whole file during package
update transaction, thus the extent booking doesn't happen as
Ok, thanks for your replay
This is a root FS, how can I defragment it?
If I try to launch it I get this output:
menion@Menionubuntu:~$ sudo btrfs filesystem defragment -r /
ERROR: defrag failed on /bin/bash: Text file busy
ERROR: defrag failed on /bin/dash: Text file busy
ERROR: defrag failed on
On 2018/8/28 下午5:34, Menion wrote:
> Hi all
> I have run a distro upgrade on my Ubuntu 16.04 that runs ppa kernel
> 4.17.2 with btrfsprogs 4.17.0
> The root filesystem is BTRFS single created by the Ubuntu Xenial
> installer (so on kernel 4.4.0) on an internal mmc, located in
> /dev/mmcblk0p3
>
Hi all
I have run a distro upgrade on my Ubuntu 16.04 that runs ppa kernel
4.17.2 with btrfsprogs 4.17.0
The root filesystem is BTRFS single created by the Ubuntu Xenial
installer (so on kernel 4.4.0) on an internal mmc, located in
/dev/mmcblk0p3
After the upgrade I have cleaned apt cache and
15 matches
Mail list logo
