systemd depends so heavily on a files it can not reboot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've hit very unpleasant trouble - my ext4 rootfs gots crazy and I had a thousands of "multiply claimed blocks" files. This revealed to me one systemd weakness - it depends so heavily on a files on a rootfs, it can not, in case they are damaged, do its basic function - allow to login and control and shutdown processes.

This really seems like a problem to me, because in case, there is something wrong with the (remote) system, the least thing you want is to not be able to login because systemd is missing some (non esential) files. OK you may say - you can not login remotely - but you can not login even localy and also an attempt to reboot the machine with years working "ctrl-alt-del" is not working because e.g. @ctrl-alt-del.target is missing.

This really looked like a bug to me
https://bugzilla.redhat.com/show_bug.cgi?id=981877
but it is a feature.

So to avoid the worst - the need to interrupt the power and risk the damage to all other mounted file systems, I'd like to open a discussion on enabling the sysrq in Fedora by default to work around this feature: https://bugzilla.redhat.com/show_bug.cgi?id=982200


Adam Pribyl
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux