View Single Post
Old 05-26-2020, 11:55 PM   #109
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@DNSB: That's... not actually clear to me.

That there'd be a free space check during the update's *download* OTA, sure, why not.
But I'm concerned with storage issues in the rootfs, not the USB partition .

And there, the actual installation is basically an unchecked tar call. There's an integrity check *before* the unpack, but that would have no bearing on a storage space issue arising *during* the unpack.

The only thing that would flag such a failure is the lack of an updated revinfo entry in the install log (/usr/local/Kobo/install.log).

It'll happily keep on trucking and try to install the kernel, bootloader & co, even if the unpack screwed up first. (Which, granted, would probably not be *that* problematic, because those don't live in the rootfs).

----

That said, we currently have quite a bit of leeway in terms of free space there, so I wouldn't worry too much about it, especially given the fact that the only people actually putting stuff in the rootfs ought to know what they're doing in the first place .

Last edited by NiLuJe; 05-27-2020 at 12:00 AM.
NiLuJe is offline   Reply With Quote