Quote: Originally Posted by springer.music Originally Posted by Do you mean that there's even less space than on 6.0?

Titanium Backup reports that there 15.6 MB free. Shouldn't this be enough for a very small mod such as an edit to build. prop?

This post is likely an important one going forward, it could be the answer to various issues people have on 6.0 related to /system.The conversation below pertains specifically to Nexus 6 @ 6.0.1, which has an almost full /system, but I'll bet the issue exists on all Nexus devices.So after some further investigation, something pretty odd is going on.ext4 (the filesystem) has various types of reserved blocks.I suspect the tools on booted Android do not count one type of reserved block. Indeed, when you use "df" utility (both toolbox and toybox), it shows 15mb or so free. Using the same "df" utility in recovery (busybox) shows 0b free. It does show that not all blocks are in use, but the remainder is likely reserved.If you use a root shell on either booted Android or in recovery, trying to write contents to a new file in /system will fail. To make matters worse, file creation succeeds, but writing content does not, so you end up with a 0 byte file. You need to delete a few extra megabytes of files, before you are able to write even 1 byte to a new file!Many editing tools remove the old file and write a new file at the same spot rather than truly editing a file. I'm not sure if the latter has any chance of succeeding, but the former would definitely fail in this scenario.While the issue is understandable technically, it is likely to trip up a lot of tools, as the error is generated at the least expected moment.This issue is a magnet for file corruption and bootloops. Beware this issue when modifying anything on /system!Immediate hunch is that the difference is explained by usage of struct statfs's bfree vs bavail member.Yes, even though TiBu and whatever other tool are showing you megabytes free, adding/modifying files is likely to give unexpected results on a (near-)full /system partition, and an unlucky edit can definitely prevent the device from booting! Can't give you exact numbers right now, but beforefiles orfiles to /system, I would recommendfiles until you have at least 30-ish mb free.