Getting this errors regularly. Need to restart every time when this error shows..

Deleted: Screenshot 2018-10-05 at 3.11.33 AM.png 49.4 KB

	Screenshot 2018-10-05 at 3.11.33 AM.png 49.4 KB View Download

heloooo........ issue no solved yet after the update...

Can you file feedback by hitting alt-shift-i after this error occurs? Put a description of the issue and send it. Then notify this bug so we can dig into it. Thanks!

Since no comment was made from your team, i need to clear all Linux files and need to install Linux (beta) again. Now this error is not occurring. But the Chromebook os now hanging sometimes even if I have not opened any Linux apps.

@joelhockey what are errors 4 & 8?

These codes are the CrostiniResult codes from starting up the vm/container.

 
https://cs.chromium.org/chromium/src/chrome/browser/chromeos/crostini/crostini_manager.h?l=32&rcl=8ee18d310d3f388750eb3e4b74fcfcebe1b74a2e

Enums start at 0.

4 = VM_START_FAILED
concierge reported failure starting vm.  /var/log/messages should show error

8 = CLIENT_ERROR
quite a number of different possibilities.  ~/log/chrome should show error

I have used the linux apps morning.. But today evening i can't see any linux apps neither the files

Deleted: Screenshot 2018-10-27 at 12.33.17 AM.png 49.4 KB

	Screenshot 2018-10-27 at 12.33.17 AM.png 49.4 KB View Download

I have also raised issue by hitting alt-shift-i.

Turned off the Chrombook and tried now after 8 hrs. Till now same issue not solved.

Releasing ownership to allow triage again.

Please check why the container is failing to start.

There's a size check in CrostiniManager that's being hit: https://cs.chromium.org/chromium/src/chrome/browser/chromeos/crostini/crostini_manager.cc?type=cs&q=%22Insufficient+disk+available%22&sq=package:chromium&g=0&l=697

I don't think Chrome should do the disk size check, since it doesn't know if the disk already exists or not. If the disk already exists, we don't need to have enough free space to create another disk. We can let concierge fail to create the disk if there isn't enough space.

What do you think, Nick?

Sounds like a good plan. This problem might happen if someone set up Linux using crosh, then was asked to set up again via the installer because the former didn't set the Crostini Enabled pref.

We could definitely eliminate the size check if the disk exists. This will be a change to the whole flow, though.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/67f715ec592aa3d5c28da1acb8439216304eaec9

commit 67f715ec592aa3d5c28da1acb8439216304eaec9
Author: Nicholas Verne <nverne@chromium.org>
Date: Tue Nov 13 04:50:27 2018

Crostini no longer fails to start when disk space is low.

The previous container restart flow would return an error if there was
insufficient disk. Free disk size is not relevant if there's an existing disk
image.

Bug:  891165 
Change-Id: I34ed750263182e920ab96befc8b00f1f2b2db89e
Reviewed-on: https://chromium-review.googlesource.com/c/1328482
Reviewed-by: Ben Wells <benwells@chromium.org>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607490}
[modify] https://crrev.com/67f715ec592aa3d5c28da1acb8439216304eaec9/chrome/browser/chromeos/crostini/crostini_manager.cc
[modify] https://crrev.com/67f715ec592aa3d5c28da1acb8439216304eaec9/chrome/browser/chromeos/crostini/crostini_manager.h
[modify] https://crrev.com/67f715ec592aa3d5c28da1acb8439216304eaec9/chrome/browser/chromeos/crostini/crostini_manager_unittest.cc