{"action":"created","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/4486","repository_url":"https://api.github.com/repos/systemd/systemd","labels_url":"https://api.github.com/repos/systemd/systemd/issues/4486/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/4486/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/4486/events","html_url":"https://github.com/systemd/systemd/issues/4486","id":185161540,"number":4486,"title":"System boots only once every 3-4 attempts unless quota.service is masked","user":{"login":"sergiocallegari","id":2779431,"avatar_url":"https://avatars.githubusercontent.com/u/2779431?v=3","gravatar_id":"","url":"https://api.github.com/users/sergiocallegari","html_url":"https://github.com/sergiocallegari","followers_url":"https://api.github.com/users/sergiocallegari/followers","following_url":"https://api.github.com/users/sergiocallegari/following{/other_user}","gists_url":"https://api.github.com/users/sergiocallegari/gists{/gist_id}","starred_url":"https://api.github.com/users/sergiocallegari/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sergiocallegari/subscriptions","organizations_url":"https://api.github.com/users/sergiocallegari/orgs","repos_url":"https://api.github.com/users/sergiocallegari/repos","events_url":"https://api.github.com/users/sergiocallegari/events{/privacy}","received_events_url":"https://api.github.com/users/sergiocallegari/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-10-25T16:03:10Z","updated_at":"2016-10-29T11:44:48Z","closed_at":null,"body":"### Submission type\r\n\r\n  - [x] Bug report\r\n  - [ ] Request for enhancement (RFE)\r\n\r\n*NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!*\r\n\r\n### systemd version the issue has been seen with\r\n\r\n> 231\r\n\r\n*NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!*\r\n\r\n### Used distribution\r\n\r\n> Ubuntu 16.10 (yakkety)\r\n\r\n### In case of bug report: Expected behaviour you didn't see\r\n\r\n> System boots reliably\r\n\r\n### In case of bug report: Unexpected behaviour you saw\r\n\r\n> Only 1 boot every ~4 attempts succeeds. In all the other cases the units corresponding to the fstab devices timeout and fail. The system is then dropped in an emergency prompt.\r\n\r\n### In case of bug report: Steps to reproduce the problem\r\n\r\n> Boot the system.\r\n\r\nThe architecture of the machine where the issue occurs may be relevant. This is a system with\r\n\r\n- 2 rotating disks managed via an intel fake raid in raid1. Intel fake raid is managed by mdadm that now supports the intel metadata.\r\n- 1 ssd\r\n\r\n- one partition of the ssd is /boot. Another partition of the ssd is swap. The rest of the ssd is a physical volume for lvm2. Root is in here as a logical volume. Opt is also here as another logical volume.\r\n\r\n- One partition of the raid is another lvm2 physical volume in another volume group. Homes are here.\r\n\r\nThis looks very much like a race somewhere, because when the machine succeeds in booting everything is fine, but most of the time the boot fails.\r\n\r\nIt is also a regression. Ubuntu 16.04 with systemd 229 used to boot reliably. The issue appeared on an upgrade from 16.04 to 16.10."},"comment":{"url":"https://api.github.com/repos/systemd/systemd/issues/comments/257087061","html_url":"https://github.com/systemd/systemd/issues/4486#issuecomment-257087061","issue_url":"https://api.github.com/repos/systemd/systemd/issues/4486","id":257087061,"user":{"login":"sergiocallegari","id":2779431,"avatar_url":"https://avatars.githubusercontent.com/u/2779431?v=3","gravatar_id":"","url":"https://api.github.com/users/sergiocallegari","html_url":"https://github.com/sergiocallegari","followers_url":"https://api.github.com/users/sergiocallegari/followers","following_url":"https://api.github.com/users/sergiocallegari/following{/other_user}","gists_url":"https://api.github.com/users/sergiocallegari/gists{/gist_id}","starred_url":"https://api.github.com/users/sergiocallegari/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sergiocallegari/subscriptions","organizations_url":"https://api.github.com/users/sergiocallegari/orgs","repos_url":"https://api.github.com/users/sergiocallegari/repos","events_url":"https://api.github.com/users/sergiocallegari/events{/privacy}","received_events_url":"https://api.github.com/users/sergiocallegari/received_events","type":"User","site_admin":false},"created_at":"2016-10-29T11:44:48Z","updated_at":"2016-10-29T11:44:48Z","body":"Thanks for providing a hint pointing to the distro. That will make it easier to assure that they do not wait the upstream on this. I'll report it in the distro bug asap, so you do not get further spurious reports on it.\r\n\r\nI take the occasion for a favor.  I'm quite inexpert in trying to debug the boot with systemd, and particularly baffled right now, with an issue that does not systematically repeat every time. Is there some pointer at what I can do to try to understand what is going on? I tend to suspect that something that should start /after/ all the fstab stuff is mounted starts too early and makes it impossible for the systemd mount to work with the entries in the fstab. What I do not understand is why /all/ the entries (including swap) start having issues and not the only one that should be interested by the quotas.\r\n\r\nIs there any way to add verbosity to the fstab generator and the dev-disk-by & co processes? \r\n\r\n"}}
{"actor":{"display_login":"sergiocallegari"}}