Assigned to random sheriff. Sheriff, this is high priority because it's broken the release.

Could this be same as https://bugs.chromium.org/p/chromium/issues/detail?id=888744?

The one you linked is about the problem generally, and will require a large effort response.

This bug is about the Nautilius specific issue that needs to be addressed today. It can probably be addressed by allocating a little more space to the rootfs.

Look for someone with experience with "build_image" and disk layouts.

I can possibly fix that (I increased rootfs on another device recently). Gimme some time. 

Alex, can you confirm what is the MMC size on the cheapest/lowest Nautilus SKU? Any concerns in increasing it from 2GB->4GB?

The rootfs partition size can't change, only the file system itself.

Or have we started FSI'ing new devices with a larger rootfs partition? That might be an option, but is a really big deal that should be communicated widely and somehow enforced for future devices.

Actually wait, it looks like the rootfs size was already 4GB, only the FS size needs to be increased, that should be easy..

Oh... it looks like someone has already done this and NOT communicated widely.

What machines have larger rootfs partitions? 

Eve + Soraka and Poppy atleast. 

Also Nautilus and Fizz based devices. So looks like all Kabylakes.

I'm not sure, but one more consideration may be this: I'm wondering if all the USB sticks in the lab need to be replaced if we increase the rootfs (I once heard Gwendal mention *I think* that if we change rootfs size, then we can't install the new image over rootfs).

That's a good question, but I believe we are okay.

Changing the rootfs partition size can change the USB stick size, but changing the rootfs file system size shouldn't affect the recovery image size.

Well, unless you explicitly modified the partition size on recovery images.

https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1241358

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/2b62fbb0b3d777fab7f86af096c3466ecf62f238

commit 2b62fbb0b3d777fab7f86af096c3466ecf62f238
Author: Rajat Jain <rajatja@google.com>
Date: Wed Sep 26 03:41:03 2018

nautilus: Increase the filesystem size to 2.3 GB

BUG= chromium:888691 
TEST=Check the free available space in nautilus.

Change-Id: Ic98860d429af8e4b3275b22d2f217887a4bd7544
Reviewed-on: https://chromium-review.googlesource.com/1241358
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Rajat Jain <rajatja@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>

[modify] https://crrev.com/2b62fbb0b3d777fab7f86af096c3466ecf62f238/overlay-nautilus/scripts/disk_layout.json

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/7fe86001c6bf65471aa34744ea2f44e4c4d13b92

commit 7fe86001c6bf65471aa34744ea2f44e4c4d13b92
Author: Rajat Jain <rajatja@google.com>
Date: Sat Sep 29 03:37:11 2018

baseboard-poppy/nami/rammus: Increase rootfs filesystem to 2.3GB

All these baseboards allocate 4GB for rootfs but create filesystem
on only 2 GB. Since the builds have started to fail, lets increase
their filesystem to 2.3GB. These are all Kabylake boards, and thus
it is reasonable to make them at par with other kabylakes (Eve,
Nautilus etc).

BUG=chromium:889849,chromium:888744, chromium:888691 
TEST=Check rootfs space increased on soraka

Change-Id: I0ed4b17dfe89a8fc3461587ab74b524ecef12896
Reviewed-on: https://chromium-review.googlesource.com/1249951
Commit-Ready: Rajat Jain <rajatja@chromium.org>
Tested-by: Rajat Jain <rajatja@chromium.org>
Reviewed-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>

[modify] https://crrev.com/7fe86001c6bf65471aa34744ea2f44e4c4d13b92/baseboard-poppy/scripts/disk_layout.json
[modify] https://crrev.com/7fe86001c6bf65471aa34744ea2f44e4c4d13b92/baseboard-rammus/scripts/disk_layout.json
[modify] https://crrev.com/7fe86001c6bf65471aa34744ea2f44e4c4d13b92/baseboard-nami/scripts/disk_layout.json