[systemd-devel] [Help] Can't log in to homed user account: "No space left on device"
Andrii Zymohliad
azymohliad at protonmail.com
Sun Aug 23 06:34:48 UTC 2020
Hello! I've lost the ability to log in to my systemd-homed user account. I would be very grateful for any help!
If I log in as root and try to authenticate:
# homectl authenticate azymohliad
Then after typing my password I get the following output:
Operation on home azymohliad failed: Not enough disk space for home azymohliad
It also produces the following system logs:
сер 22 09:11:08 az-wolf-pc systemd-homed[425]: azymohliad: changing state inactive → authenticating
сер 22 09:11:08 az-wolf-pc systemd-homework[1215]: None of the supplied plaintext passwords unlocks the user record's hashed passwords.
сер 22 09:11:08 az-wolf-pc systemd-homed[425]: Authentication failed: Required key not available
сер 22 09:11:08 az-wolf-pc systemd-homed[425]: azymohliad: changing state authenticating → inactive
сер 22 09:11:23 az-wolf-pc systemd-homed[425]: azymohliad: changing state inactive → authenticating
сер 22 09:11:23 az-wolf-pc systemd-homework[1216]: Provided password unlocks user record.
сер 22 09:11:23 az-wolf-pc systemd-homed[425]: Authentication failed: No space left on device
сер 22 09:11:23 az-wolf-pc systemd-homed[425]: azymohliad: changing state authenticating → inactive
And here [https://pastebin.com/BwkkvbZr](https://pastebin.com/BwkkvbZr]here[/url) is the full log since the last boot.
My root filesystem is BTRFS, home is LUKS-encrypted BTRFS on a loopback file. Here's the details:
# homectl inspect azymohliad
User name: azymohliad
State: inactive
Disposition: regular
Last Change: Thu 2020-06-25 17:41:52 EEST
Last Passw.: Thu 2020-06-04 19:04:43 EEST
Login OK: yes
Password OK: yes
UID: 60265
GID: 60265 (azymohliad)
Aux. Groups: audio
docker
wheel
Real Name: Andrii Zymohliad
Directory: /home/azymohliad
Storage: luks (strong encryption)
Image Path: /home/azymohliad.home
Removable: no
Shell: /usr/bin/fish
LUKS Discard: online=no offline=yes
LUKS UUID: 4ed4c05040e4429ca0163bb40587ec2d
Part UUID: 3ed283c030ab42778c1fb75aeeccc88e
FS UUID: 4ffae38b42c94e5389a13d21cd862938
File System: btrfs
LUKS Cipher: aes
Cipher Mode: xts-plain64
Volume Key: 256bit
Mount Flags: nosuid nodev exec
Disk Size: 402.7G
Disk Floor: 256.0M
Disk Ceiling: 429.3G
Good Auth.: 362
Last Good: Fri 2020-08-21 19:23:27 EEST
Bad Auth.: 128
Last Bad: Sat 2020-08-22 09:45:32 EEST
Next Try: anytime
Auth. Limit: 30 attempts per 1min
Passwords: 1
Local Sig.: yes
Service: io.systemd.Home
My root partition is 475G, and as you can see, home file size is ~400G (I guess it was stupid to leave only 75G for root in the first place). But for some reason `btrfs fi usage /` shows that only 352G are allocated on the device before I try to authenticate (every time after boot), and full 475G after authentication attempt.
I've posted some more btrfs info outputs on Arch forum (https://bbs.archlinux.org/viewtopic.php?id=258382). I'm not sure how to properly format snippets on mail list and how convenient it is to read them here, first time on tech mail list.
I can unlock and mount my /home/azymohliad.home file manually, so that confirms that it's not corrupted. I haven't tried to resize it manually (outside of homectl), I'm afraid to do anything wrong.
Thanks for taking time to read this far! Is there anything obvious here that I can do to fix it? Or any hints where to look?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20200823/a844bd3d/attachment.htm>
More information about the systemd-devel
mailing list