Updating Debian package does not remove /boot/initrd.img #3

sphh · 2020-06-03T08:10:39Z

When updating the Debian package (both 4.19-lts and 5.6), the file initrd.img-xxx from the old package stays behind. I just found 5 of those outdated files.

Is there a chance to include the removal in the Debian packages?

The text was updated successfully, but these errors were encountered:

qzed · 2020-06-14T19:02:19Z

Can you post the entries in the boot directory (i.e. run ls -al /boot)?

sphh · 2020-06-14T19:14:26Z

I already deleted the files by hand to save some space in the /boot partition, but here it is anyway:

$ ls /boot/
config-4.15.0-106-generic
config-4.19.123-surface-lts
config-5.6.15-surface
efi/
grub/
initrd.img-4.15.0-106-generic
initrd.img-4.19.123-surface-lts
initrd.img-5.6.15-surface
lost+found/
memtest86+.bin
memtest86+.elf
memtest86+_multiboot.bin
System.map-4.15.0-106-generic
System.map-4.19.123-surface-lts
System.map-5.6.15-surface
vmlinuz-4.15.0-106-generic
vmlinuz-4.19.123-surface-lts
vmlinuz-5.6.15-surface

I can get a new list after the next round of surface kernel updates.

qzed · 2020-06-14T19:14:32Z

I cannot reproduce this in a LXC container running Ubuntu 19.10. The postrm script of the package calls the hooks in /etc/kernel/postrm.d with, as far as I can tell, the correct version, which should then take care of updating/removing the initrd, at least on Ubuntu and Debian.

Which distribution are you running, specifically?

qzed · 2020-06-14T19:16:21Z

initrd.img-5.6.15-surface is exactly the same name I see in my container so it doesn't seem to be any difference there.

sphh · 2020-06-14T19:23:59Z

I run Linux Mint 19.3 Cinnamon.

The "problem" was, that after an kernel update from - let's say 5.6.14 to 5.6.15 - there were these files in /boot (I hope I reconstructed it correctly):

config-5.6.15-surface
initrd.img-5.6.14-surface
initrd.img-5.6.15-surface
System.map-5.6.15-surface
vmlinuz-5.6.15-surface

qzed · 2020-06-14T19:45:25Z

This seems to be a problem with the /etc/kernel/postrm.d/initramfs-tools script, updating the initramfs after package removal/upgrade. This contains

    if [ -z "$1" ] || [ "$1" != "remove" ]; then
        exit 0
    fi

which returns if the package is not removed, e.g. is upgraded. it seems that Debian/Ubuntu expect all kernel packages to be specifically named with their version in the name. That way the package does not really get upgraded, but removed and a completely new package (with different name) gets installed.

There's nothing we can do to change the /etc/kernel/postrm.d/initramfs-tools script, since that's not part of the kernel package. To replicate the behavior of original Debian/Ubuntu packages, we'd have to switch to meta-packages (#2).

sphh · 2020-06-14T20:05:26Z

Would it be possible to remove the stale initrd.img-xxx file with the help of package maintainer scripts? A lot of time has passed since I was responsible for a Debian package, that I can't remember all the details...

qzed · 2020-06-14T20:18:38Z

Possible yes, although that would bypass the initrd tools and I'm not sure if that is a good idea. I think that a better quick-fix would probably be modifying https://github.com/torvalds/linux/blob/b3a9e3b9622ae10064826dccb4f7a52bd88c7407/scripts/package/builddeb#L193 for postrm by replacing upgrade with remove (first parameter to the script). The best solution would be to switch to meta-packages, but doing that will cost more time.

danielzgtg · 2020-06-15T01:16:41Z

Can you post the entries in the boot directory (i.e. run ls -al /boot)?

I already deleted the files by hand to save some space in the /boot partition

Here is my output, where I didn't delete any files:

drwxr-xr-x  4 root root     4096 Jun 12 13:38 .
drwxr-xr-x 18 root root     4096 Mar 15 14:43 ..
-rw-r--r--  1 root root   241743 Jun  1 05:39 config-5.6.15-surface
-rw-r--r--  1 root root   243596 Jun 12 11:02 config-5.7.0-daniel1
drwx------  4 root root     4096 Dec 31  1969 efi
drwxr-xr-x  5 root root     4096 Jun 12 13:38 grub
-rw-r--r--  1 root root 82644751 Mar 21 11:57 initrd.img-5.5.10-surface
-rw-r--r--  1 root root 82672122 Apr  1 15:33 initrd.img-5.5.13-surface
-rw-r--r--  1 root root 82116124 Mar 15 14:39 initrd.img-5.5.8-surface
-rw-r--r--  1 root root 83634384 May 25 17:31 initrd.img-5.6.14-surface
-rw-r--r--  1 root root 83767267 Jun 12 13:36 initrd.img-5.6.15-surface
-rw-r--r--  1 root root 83566986 Apr 20 20:25 initrd.img-5.6.5-surface
-rw-r--r--  1 root root 83631541 May 25 17:29 initrd.img-5.6.7-surface
-rw-r--r--  1 root root 84109809 Jun 12 13:38 initrd.img-5.7.0-daniel1
-rw-r--r--  1 root root   182704 Feb 13 18:09 memtest86+.bin
-rw-r--r--  1 root root   184380 Feb 13 18:09 memtest86+.elf
-rw-r--r--  1 root root   184884 Feb 13 18:09 memtest86+_multiboot.bin
-rw-r--r--  1 root root  5346756 Jun  1 05:39 System.map-5.6.15-surface
-rw-r--r--  1 root root  5403608 Jun 12 11:02 System.map-5.7.0-daniel1
-rw-r--r--  1 root root 11888888 Jun  1 05:39 vmlinuz-5.6.15-surface
-rw-r--r--  1 root root 11856032 Jun 12 11:02 vmlinuz-5.7.0-daniel1

danielzgtg · 2020-07-02T18:24:01Z

Over the course of the past few months, the problem has grown to affect me more seriously. I now have 11 of them in /boot and there is not a single byte of disk space left. This caused APT to fail with the following error today:

Processing triggers for initramfs-tools (0.136ubuntu6.2) ...
update-initramfs: Generating /boot/initrd.img-5.7.6-surface
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.7.6-surface with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.31-0ubuntu9) ...
Errors were encountered while processing:
 linux-firmware
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

While I am aware of this bug and that I need to apply the workaround of deleting those files, others might not be. They might be confused and wonder why initramfs-tools suddenly started failing.

qzed · 2020-07-02T21:24:29Z

I'll try to have a go at it this weekend.

qzed · 2020-07-03T01:19:13Z

@danielzgtg Okay, so I'm trying to figure out how Debian/Ubuntu implement the kernel metapackages. Specifically how they remove old kernels (they do that, right?). If they do that, any idea how?

danielzgtg · 2020-07-04T03:12:32Z

Old kernels are removed by being "no longer required." They are removed with apt autoremove. That forms part of the apt update && apt upgrade && apt dist-upgrade && apt autoremove --purge I do.

The latest kernel is always depended upon by the metapackage. The second latest kernel is not depended on, but somehow isn't marked "no longer required." Earlier kernels are always marked as "no longer required." The command that updates the metapackage does not remove the old kernel; that is done manually in a separate command.

qzed · 2020-07-04T12:00:35Z

Thanks! That does clear things up for me. I just wanted to be certain that there isn't any "magic" behavior just for kernel packages that removes old ones on apt upgrade automatically. So it should be enough to just specify a dependency.

qzed · 2020-07-05T11:15:41Z

@danielzgtg Can you test if upgrading to the latest version works without any problems?

Edit: Just noticed I screwed up the LTS release. Can you try updating the non-LTS release? That should work.
Edit 2: The LTS release should now also work.

sphh · 2020-07-05T17:54:41Z

@qzed, thanks for looking into this and making meta-packages!

Today I wanted to install the newly available packages, but I get the following errors. I don't know if this is because of this metapackage thing...

E: /tmp/apt-dpkg-install-DbU0wE/0-linux-headers-4.19.131-surface-lts_4.19.131-surface-lts-3_amd64.deb: trying to overwrite '/usr/src/linux-headers-4.19.131-surface-lts/.config', which is also in package linux-headers-surface-lts 4.19.131-1
E: /tmp/apt-dpkg-install-DbU0wE/1-linux-headers-5.7.7-surface_5.7.7-surface-2_amd64.deb: trying to overwrite '/lib/modules/5.7.7-surface/build', which is also in package linux-headers-surface 5.7.7-1
E: /tmp/apt-dpkg-install-DbU0wE/4-linux-image-4.19.131-surface-lts_4.19.131-surface-lts-3_amd64.deb: trying to overwrite '/boot/System.map-4.19.131-surface-lts', which is also in package linux-image-surface-lts 4.19.131-1
E: /tmp/apt-dpkg-install-DbU0wE/5-linux-image-5.7.7-surface_5.7.7-surface-2_amd64.deb: trying to overwrite '/boot/System.map-5.7.7-surface', which is also in package linux-image-surface 5.7.7-1

I have both the linux-surface and linux-surface-lts installed...

qzed · 2020-07-05T18:50:37Z

Yeah, that's caused by the change, thanks for the feedback! This means that to upgrade the packages, you'll have to manually uninstall linux-surface and linux-surace-lts and then re-install them.

Basically, what happens is (as far as I can see it): The linux-surface-lts package gets marked for an update. With the change, it now depends on linux-image-<...>, so it wants to install that first. Installing that fails however, because the old linux-surface-lts package has files that are in the newer version part of the linux-image-<...> package, which that package would then overwrite. The files are still there, because the package gets upgraded only after the dependencies are installed.

sphh · 2020-07-05T21:06:27Z

I managed to recover from this error with:

sudo apt-get --fix-broken install

ghost · 2020-07-06T02:59:47Z

Old kernels are removed by being "no longer required." They are removed with apt autoremove. That forms part of the apt update && apt upgrade && apt dist-upgrade && apt autoremove --purge I do.

In Ubuntu, running autoremove or purging is not necessary as of the last four or more months. When the software updater window appears it prompts to remove old kernels. I haven't had to run either of those commands, for the purpose of removing old Ubuntu kernels, for months.

Going forward, does this mean you have to uninstall the current linux-surface kernel before you can install the latest version or it'll error? Or it's a one-off as a result of the changes listed in #96?

Edited - Added images

Am I pointing out something relevant here or am I pointing out the obvious! Do say!

qzed · 2020-07-06T08:51:01Z

In Ubuntu, running autoremove or purging is not necessary as of the last four or more months.

Intersting, thanks for sharing! Do you have any idea how the kernel packages are identified and marked for removal? Can you have an eye on this over the next couple of linux-surface kernel releases to check if that's working correctly/how that behaves?

Going forward, does this mean you have to uninstall the current linux-surface kernel before you can install the latest version or it'll error? Or it's a one-off as a result of the changes listed in #96?

This should be a one-off for this upgrade only, although I haven't been able to test that, so would be neat to have some feedback on that over the next couple of releases. I've also updated the announcement to make this a bit clearer.

danielzgtg · 2020-07-06T10:08:35Z

Can you test if upgrading to the latest version works without any problems?

The update went well

root@daniel-tablet1:~# apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-5.7.7-surface linux-image-5.7.7-surface
The following packages will be upgraded:
  linux-headers-surface linux-image-surface surface-control
3 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 70.7 MB of archives.
After this operation, 28.8 MB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 https://pkg.surfacelinux.com/debian release/main amd64 linux-headers-5.7.7-surface amd64 5.7.7-surface-2 [7,788 kB]
Get:2 https://pkg.surfacelinux.com/debian release/main amd64 linux-headers-surface amd64 5.7.7-surface-2 [2,458 B]
Get:3 https://pkg.surfacelinux.com/debian release/main amd64 linux-image-5.7.7-surface amd64 5.7.7-surface-2 [62.6 MB]
Get:4 https://pkg.surfacelinux.com/debian release/main amd64 linux-image-surface amd64 5.7.7-surface-2 [2,454 B]                                                                        
Get:5 https://pkg.surfacelinux.com/debian release/main amd64 surface-control amd64 0.2.6-1 [259 kB]                                                                                     
Fetched 70.7 MB in 13s (5,266 kB/s)                                                                                                                                                     
Selecting previously unselected package linux-headers-5.7.7-surface.
(Reading database ... 313679 files and directories currently installed.)
Preparing to unpack .../linux-headers-5.7.7-surface_5.7.7-surface-2_amd64.deb ...
Unpacking linux-headers-5.7.7-surface (5.7.7-surface-2) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-5.7.7-surface_5.7.7-surface-2_amd64.deb (--unpack):
 trying to overwrite '/lib/modules/5.7.7-surface/build', which is also in package linux-headers-surface 5.7.7-1
Preparing to unpack .../linux-headers-surface_5.7.7-surface-2_amd64.deb ...
Unpacking linux-headers-surface (5.7.7-surface-2) over (5.7.7-1) ...
Selecting previously unselected package linux-image-5.7.7-surface.
Preparing to unpack .../linux-image-5.7.7-surface_5.7.7-surface-2_amd64.deb ...
Unpacking linux-image-5.7.7-surface (5.7.7-surface-2) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-5.7.7-surface_5.7.7-surface-2_amd64.deb (--unpack):
 trying to overwrite '/boot/System.map-5.7.7-surface', which is also in package linux-image-surface 5.7.7-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../linux-image-surface_5.7.7-surface-2_amd64.deb ...
Unpacking linux-image-surface (5.7.7-surface-2) over (5.7.7-1) ...
Preparing to unpack .../surface-control_0.2.6-1_amd64.deb ...
Unpacking surface-control (0.2.6-1) over (0.2.5-3) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-headers-5.7.7-surface_5.7.7-surface-2_amd64.deb
 /var/cache/apt/archives/linux-image-5.7.7-surface_5.7.7-surface-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@daniel-tablet1:~# apt install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  linux-headers-5.7.7-surface linux-image-5.7.7-surface
The following NEW packages will be installed:
  linux-headers-5.7.7-surface linux-image-5.7.7-surface
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 70.4 MB of archives.
After this operation, 330 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://pkg.surfacelinux.com/debian release/main amd64 linux-headers-5.7.7-surface amd64 5.7.7-surface-2 [7,788 kB]
Get:2 https://pkg.surfacelinux.com/debian release/main amd64 linux-image-5.7.7-surface amd64 5.7.7-surface-2 [62.6 MB]
Fetched 70.4 MB in 20s (3,526 kB/s)                                                                                                                                                     
(Reading database ... 277865 files and directories currently installed.)
Preparing to unpack .../linux-headers-5.7.7-surface_5.7.7-surface-2_amd64.deb ...
Unpacking linux-headers-5.7.7-surface (5.7.7-surface-2) ...
Preparing to unpack .../linux-image-5.7.7-surface_5.7.7-surface-2_amd64.deb ...
Unpacking linux-image-5.7.7-surface (5.7.7-surface-2) ...
Setting up surface-control (0.2.6-1) ...
Setting up linux-headers-5.7.7-surface (5.7.7-surface-2) ...
Setting up linux-image-5.7.7-surface (5.7.7-surface-2) ...
 * dkms: running auto installation service for kernel 5.7.7-surface                                                                                                               [ OK ] 
update-initramfs: Generating /boot/initrd.img-5.7.7-surface
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.7.7-surface
Found initrd image: /boot/initrd.img-5.7.7-surface
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings
done
Setting up linux-headers-surface (5.7.7-surface-2) ...
Setting up linux-image-surface (5.7.7-surface-2) ...
root@daniel-tablet1:~#

Boots fine. initrd.img-5.7.6-surface is still left in /boot/, but it should be the last one that needs to be removed manually. Once 5.7.8/5.8 comes out, the removal of initrd.img-5.7.7-surface can be tested.

I also encountered the thing with:

I managed to recover from this error with [...]

When the software updater window appears it prompts to remove old kernels

I don't use the GUI :)

one-off for this upgrade only

This could be avoided even for the first time with a Conflicts line.

ghost · 2020-07-06T14:22:38Z

Do you have any idea how the kernel packages are identified and marked for removal?

I'm not sure how I would find that out, I spent some time googling related terms but couldn't find anything useful. Here is the [1]dpkg log when the kernels were being removed, here is the journalctl [2]log when the preceding update was in progress, installing new kernels via the Software Updater and here is a [3]log of the Software Updater removing kernels. If you see any other files mentioned in these links, you think might help tell me and I'll have a look at posting.

[1]https://github.com/condemnedmeat/dot/blob/master/dpkg.txt
[2]https://github.com/condemnedmeat/dot/blob/master/loga.txt
[3]https://github.com/condemnedmeat/dot/blob/master/logb.txt

ghost · 2020-07-06T14:45:57Z

Or perhaps the answer is somewhere here...

/etc/kernel/postinst.d:
apt-auto-removal
initramfs-tools
unattended-upgrades
update-notifier
zz-update-grub

/etc/kernel/postrm.d:
initramfs-tools
zz-update-grub

qzed · 2020-07-06T16:19:56Z

The update went well

Neat!

This could be avoided even for the first time with a Conflicts line.

Ah thanks! I'll keep that in mind for the next time. On the other hand, the failure gets users to (hopefully) look at the announcements and makes them aware of the outdated initrd files, so I think it might not be that bad of a thing.

I also encountered the thing with:

I managed to recover from this error with [...]

Thanks! I've updated the announcement and added the apt-get --fix-broken install command.

qzed · 2020-07-06T16:23:37Z

Or perhaps the answer is somewhere here...

/etc/kernel/postinst.d:
apt-auto-removal

I think that could be it. In that case it should already work (since the initramfs-tools stuff works). Guess the only way to know for sure is to check the behavior over the next couple of releases.

ghost · 2020-07-10T02:28:10Z

I got these errors on the very next update.

It's recreated the initrd files that had been deleted.

qzed · 2020-07-10T12:25:41Z

It somewhat looks like there are still remnants of old kernels around. As I don't use Ubuntu, I have no clue where, or what would cause the initrds to be rebuilt.

ghost · 2020-07-10T14:23:20Z

The solution may be to sudo rm the equivalent files in /var/lib/initramfs-tools as apparently that is where initramfs refers to. I'll see what happens when I next update.

I'm not sure if you only need to remove those files or if you must remove the files in the boot partition too.

The source of my information was:
http://www.bigsoft.co.uk/blog/2018/05/13/ubuntu-boot-partition-full
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1773476/comments/6

ghost · 2020-07-16T02:46:43Z

No depmod issues and the previous kernel is automatically removed during the update so all works on 18.04 & 20.04.

qzed · 2020-07-16T15:49:53Z

Neat! Closing this as it seems to be resolved. Feel free to comment/re-open if there are still issues remaining.

danielzgtg · 2020-07-22T02:40:48Z

It worked today and automatically removed the third last kernel. It also magically preserved the second last kernel.

ghost · 2020-08-18T19:03:29Z

Currently the old kernels are not being removed at the time the new kernel is being installed when using Software Updater. It is listed to be removed next time the Updater is used. Perhaps I reported it as working incorrectly in July, or this is intended behaviour. This has been the case since debian_lts-4.19.134 or so.

qzed · 2020-08-18T19:21:01Z

I guess as long as apt autoremove removes them (except for maybe the latest N versions), it works as intended. Let me know if apt autoremove doesn't work.

ghost · 2020-08-18T19:22:46Z

I should think that works as it is meant to.

qzed mentioned this issue Jul 5, 2020

Announcements and updates linux-surface/linux-surface#96

Open

danielzgtg mentioned this issue Jul 6, 2020

Use metapackages for Debian/Ubuntu #2

Closed

qzed closed this as completed Jul 16, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Updating Debian package does not remove /boot/initrd.img #3

Updating Debian package does not remove /boot/initrd.img #3

sphh commented Jun 3, 2020

qzed commented Jun 14, 2020

sphh commented Jun 14, 2020

qzed commented Jun 14, 2020

qzed commented Jun 14, 2020 •

edited

Loading

sphh commented Jun 14, 2020 •

edited

Loading

qzed commented Jun 14, 2020 •

edited

Loading

sphh commented Jun 14, 2020

qzed commented Jun 14, 2020

danielzgtg commented Jun 15, 2020

danielzgtg commented Jul 2, 2020

qzed commented Jul 2, 2020

qzed commented Jul 3, 2020

danielzgtg commented Jul 4, 2020

qzed commented Jul 4, 2020

qzed commented Jul 5, 2020 •

edited

Loading

sphh commented Jul 5, 2020

qzed commented Jul 5, 2020

sphh commented Jul 5, 2020

ghost commented Jul 6, 2020 •

edited by ghost

Loading

qzed commented Jul 6, 2020

danielzgtg commented Jul 6, 2020 •

edited

Loading

ghost commented Jul 6, 2020

ghost commented Jul 6, 2020

qzed commented Jul 6, 2020 •

edited

Loading

qzed commented Jul 6, 2020

ghost commented Jul 10, 2020

qzed commented Jul 10, 2020

ghost commented Jul 10, 2020 •

edited by ghost

Loading

ghost commented Jul 16, 2020

qzed commented Jul 16, 2020

danielzgtg commented Jul 22, 2020

ghost commented Aug 18, 2020

qzed commented Aug 18, 2020

ghost commented Aug 18, 2020

Updating Debian package does not remove /boot/initrd.img #3

Updating Debian package does not remove /boot/initrd.img #3

Comments

sphh commented Jun 3, 2020

qzed commented Jun 14, 2020

sphh commented Jun 14, 2020

qzed commented Jun 14, 2020

qzed commented Jun 14, 2020 • edited Loading

sphh commented Jun 14, 2020 • edited Loading

qzed commented Jun 14, 2020 • edited Loading

sphh commented Jun 14, 2020

qzed commented Jun 14, 2020

danielzgtg commented Jun 15, 2020

danielzgtg commented Jul 2, 2020

qzed commented Jul 2, 2020

qzed commented Jul 3, 2020

danielzgtg commented Jul 4, 2020

qzed commented Jul 4, 2020

qzed commented Jul 5, 2020 • edited Loading

sphh commented Jul 5, 2020

qzed commented Jul 5, 2020

sphh commented Jul 5, 2020

ghost commented Jul 6, 2020 • edited by ghost Loading

qzed commented Jul 6, 2020

danielzgtg commented Jul 6, 2020 • edited Loading

ghost commented Jul 6, 2020

ghost commented Jul 6, 2020

qzed commented Jul 6, 2020 • edited Loading

qzed commented Jul 6, 2020

ghost commented Jul 10, 2020

qzed commented Jul 10, 2020

ghost commented Jul 10, 2020 • edited by ghost Loading

ghost commented Jul 16, 2020

qzed commented Jul 16, 2020

danielzgtg commented Jul 22, 2020

ghost commented Aug 18, 2020

qzed commented Aug 18, 2020

ghost commented Aug 18, 2020

qzed commented Jun 14, 2020 •

edited

Loading

sphh commented Jun 14, 2020 •

edited

Loading

qzed commented Jun 14, 2020 •

edited

Loading

qzed commented Jul 5, 2020 •

edited

Loading

ghost commented Jul 6, 2020 •

edited by ghost

Loading

danielzgtg commented Jul 6, 2020 •

edited

Loading

qzed commented Jul 6, 2020 •

edited

Loading

ghost commented Jul 10, 2020 •

edited by ghost

Loading