| Summary: | TTY login no longer works when disk is full | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ell1e <el> |
| Component: | pam | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | dennis, el, gansalmon, itamar, jonathan, kernel-maint, kzak, madhu.chinakonda, marcelo.barbosa, mluscon, tmraz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-12-04 09:23:13 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
ell1e
2013-10-09 20:15:34 UTC
If your disk is full and things need to write to the disk to log in, then I don't think there is much that can be done here. At any rate, it isn't a kernel issue. Moving to the distribution component. I am wondering if there was a way login could be done anyway? (e.g. by storing whatever needs to be written - login logs I suppose - in memory?) Also sorry for the #fedora remark, it doesn't belong here and it might or might not have been a misunderstanding. (it's on irc feedback now) The login & getty programs come from util-linux, although the issue could lie elsewhere. If this is related, sudo and su don't work either. We would need a strace log of the login process to see where it is stuck. Hmm I suppose I could see if I can reproduce it safely inside a virtual machine. I'm a bit reluctant with trying it on my laptop atm where I experienced this, since btrfs. The agetty processes are the one I would need to attach strace to I suppose? Yes, probably strace with -f (agetty asks for username, then exec login(1), the login process asks for password). It's probably journald or audit problem. We need strace log to find out where the login process is stuck. Clearing needinfo since this has been closed for years |