> I suspect that the workaround until > this is figured out why the fallocate fails (I suspect shared extents, > there's evidence this home file has been snapshot and I don't know > what effect that has on fallocating the file) is to use > --luks-discard=true ? That should avoid the need to fallocate when > opening.
Just to confirm, "homectl update --luks-discard=on azymohliad" fixed the issue for me. I can log in again. Thanks a lot to Chris and Andrei! > And the user will have to be vigilant about the space usage > of user home because it's now possible to overcommit. I guess it's better to reduce home size (to something like 300-350G in my case) to decrease the probability of overcommit? _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
