Creates fsck .REC artifacts that can lead to "partition full" errors

[Michael Vogt]

I ran accross this today on my BBB:
"""
$ sudo snappy update
Failed to run command '/bin/cp /writable/cache/assets/dtbs/omap3-overo-storm-gallop43.dtb /boot/uboot/a/dtbs': /bin/cp: error writing ‘/boot/uboot/a/dtbs/omap3-overo-storm-gallop43.dtb’: No space left on device
/bin/cp: failed to extend ‘/boot/uboot/a/dtbs/omap3-overo-storm-gallop43.dtb’: No space left on device
 (exit status 1)
...
# ls -l /boot/uboot/
total 19583
-rwxr-xr-x 1 root root 38400 Jan 1 1980 FSCK0000.REC
-rwxr-xr-x 1 root root 6484992 Jan 1 1980 FSCK0001.REC
-rwxr-xr-x 1 root root 13492736 Jan 1 1980 FSCK0002.REC
-rwxr-xr-x 1 root root 512 Jan 1 1980 FSCK0003.REC
-rwxr-xr-x 1 root root 30208 Jan 1 1980 FSCK0004.REC
-rwxr-xr-x 1 root root 2048 Jan 1 1980 FSCK0005.REC
# df -h /boot/uboot/
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p1 63M 63M 1.0K 100% /boot/uboot
"""

which indicates that we need to not create .REC files or remove them as the partition is too small.

[Michael Vogt (mvo)]

Another potential robustness issue. It seems like we need a job that removes the "FSCK*.REC" files (maybe even in initramfs after fsck.vfat was run). Adding ogra to get his opinion.

[Leo Arias (elopio)]

ogra, is this still a valid bug? Are we still leaving .rec files around?

[Launchpad Janitor (janitor)]

[Expired for Snappy because there has been no activity for 60 days.]