Stackato 2.10.X Filesystem is not writeable

Posted by jamesf on 2013-08-09 12:55
OS: All / Any | Product: Stackato | tags: filesystem stackato

I have deployed an app with a filesystem service but my filesystem suddenly is no longer writeable. Why is that?


The fs quota has a low default value of 100M. When you hit this quota on your filesystem service, the filesystem will no longer be writeable. You may need another filesystem, or you can globally increase the max filesystem size by running the following:

$ kato config set filesystem_node max_fs_size x

(where x is an integer in MB)

This is also possible through the Settings of the web console. You may need to restart the filesystem service using "kato restart filesystem".

This will not retroactively increase existing filesystem services, it will only affect newly created services after the change.

ActiveState Staff
Mon, 2013-08-12 15:23

Under some situations, a bug may occur where a filesystem will reach its quota before actually being full, at approximately 50M. This is due to a minor bug, a patch is available via the kato patch service, or here for 2.10.4 users:

For more information, contact Stackato support.