{"action":"created","issue":{"url":"https://api.github.com/repos/QubesOS/qubes-issues/issues/1191","labels_url":"https://api.github.com/repos/QubesOS/qubes-issues/issues/1191/labels{/name}","comments_url":"https://api.github.com/repos/QubesOS/qubes-issues/issues/1191/comments","events_url":"https://api.github.com/repos/QubesOS/qubes-issues/issues/1191/events","html_url":"https://github.com/QubesOS/qubes-issues/issues/1191","id":106540809,"number":1191,"title":"Disk space errors & issues with a Standalone VM","user":{"login":"bnvk","id":48677,"avatar_url":"https://avatars.githubusercontent.com/u/48677?v=3","gravatar_id":"","url":"https://api.github.com/users/bnvk","html_url":"https://github.com/bnvk","followers_url":"https://api.github.com/users/bnvk/followers","following_url":"https://api.github.com/users/bnvk/following{/other_user}","gists_url":"https://api.github.com/users/bnvk/gists{/gist_id}","starred_url":"https://api.github.com/users/bnvk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bnvk/subscriptions","organizations_url":"https://api.github.com/users/bnvk/orgs","repos_url":"https://api.github.com/users/bnvk/repos","events_url":"https://api.github.com/users/bnvk/events{/privacy}","received_events_url":"https://api.github.com/users/bnvk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-09-15T12:00:07Z","updated_at":"2015-09-15T13:34:49Z","closed_at":null,"body":"I am encountering a strange situation with doing some software development work (running a node.js build script to generate packages) whereby the build task fails with a node.js error\r\n`[ { [Error: ENOSPC, write] errno: 54, code: 'ENOSPC' } ] undefined` which is a no disk space error. \r\n\r\nEach time after running this build script and it errors out, thereafter doing a normal tab-to-complete bash command also errors out with:\r\n\r\n```\r\n[user@dev ~]$ cd sou-bash: cannot create temp file for here-document: No space left on device`\r\n```\r\n\r\nAt first I thought this was just that my StandaloneVM needed more allowed disk space. I increased it to 24 GB, but the error keeps persisting. Here is the print out from looking at disk space usage:\r\n\r\n```\r\n[user@dev ~]$ df -h\r\nFilesystem          Size  Used Avail Use% Mounted on\r\n/dev/mapper/dmroot  9.8G  7.7G  1.6G  84% /\r\n/dev/xvdd           380M  147M  213M  41% /usr/lib/modules\r\ndevtmpfs            152M     0  152M   0% /dev\r\ntmpfs               157M   21M  137M  13% /dev/shm\r\ntmpfs               157M  504K  156M   1% /run\r\ntmpfs               157M     0  157M   0% /sys/fs/cgroup\r\ntmpfs               157M  157M     0 100% /tmp\r\n/dev/xvdb            24G  5.1G   19G  22% /rw\r\ntmpfs                32M   12K   32M   1% /run/user/1000\r\n```\r\n\r\nAnother strange issue I notice that co-occurs with this \"disk space issue\" are that upon stopping & restarting the StandaloneVM, the Qubes VM manager crashes. This StandaloneVM is based on a Fedora 21 template.\r\n\r\nAny thoughts or additional info I can provide @marmarek ?"},"comment":{"url":"https://api.github.com/repos/QubesOS/qubes-issues/issues/comments/140395059","html_url":"https://github.com/QubesOS/qubes-issues/issues/1191#issuecomment-140395059","issue_url":"https://api.github.com/repos/QubesOS/qubes-issues/issues/1191","id":140395059,"user":{"login":"marmarek","id":726704,"avatar_url":"https://avatars.githubusercontent.com/u/726704?v=3","gravatar_id":"","url":"https://api.github.com/users/marmarek","html_url":"https://github.com/marmarek","followers_url":"https://api.github.com/users/marmarek/followers","following_url":"https://api.github.com/users/marmarek/following{/other_user}","gists_url":"https://api.github.com/users/marmarek/gists{/gist_id}","starred_url":"https://api.github.com/users/marmarek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marmarek/subscriptions","organizations_url":"https://api.github.com/users/marmarek/orgs","repos_url":"https://api.github.com/users/marmarek/repos","events_url":"https://api.github.com/users/marmarek/events{/privacy}","received_events_url":"https://api.github.com/users/marmarek/received_events","type":"User","site_admin":false},"created_at":"2015-09-15T13:34:49Z","updated_at":"2015-09-15T13:34:49Z","body":"On Tue, Sep 15, 2015 at 06:02:46AM -0700, qubesuser wrote:\n> Is it really a good idea to mount a tmpfs on /tmp at all?\n\nAsk Fedora people ;)\nhttps://fedoraproject.org/wiki/Features/tmp-on-tmpfs\n\n> Ubuntu 15.04 HVM (which is what most software is tested on) doesn't seem to mount anything on /tmp by default for instance.\n> \n> Qubes could put /tmp on volatile.img and make it huge (since it's sparse).\n\nYes, it may be good idea to not use tmpfs for /tmp, especially when user\nhas not so much RAM.\nThe side effect would be that /tmp from TmplateVM may leak into child\nVMs. Not sure if that's an issue.\n\n-- \nBest Regards,\nMarek Marczykowski-Górecki\nInvisible Things Lab\nA: Because it messes up the order in which people normally read text.\nQ: Why is top-posting such a bad thing?\n"}}