diff options
| author | Dr. Tilmann Bubeck <t.bubeck@reinform.de> | 2012-05-04 10:32:47 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2013-04-01 23:43:48 -0400 |
| commit | 80cfe9e163b1c92f917e0a5e053b148fca790677 (patch) | |
| tree | 357b1daff0c40858c6f850e60f110093bf1538a6 /src/test/test-loopback.c | |
| parent | 9607d9470eec07df817e58f64d312ccb5ac4cfcc (diff) | |
Do no isolate in case of emergency or severe problems
This patch changes local-fs.target and systemd-fsck to not use
"isolate" when going into emergency.
This fixes https://bugzilla.redhat.com/show_bug.cgi?id=810722
The motivation is, that when something wents wrong, we should
keep everything as it is, to let the user fix the problem. When
isolating we stop a lot of services and therefore change the
system heavily so that it gets harder for the user to fix.
An example is a crypted partition. When the fsck in a crypted
partition fails, it previously used "emergency/start/isolate"
which stops cryptsetup. Therefore if the user tries to fsck
e.g. /dev/mapper/luks-356c20ae-c7a2-4f1c-ae1d-1d290a91b691
as printed by the failing fsck, then it will not find this
device (because it got closed).
So please apply this patch to let the user see the failing
situation.
Thanks!
[zj: removed dead isolate param from start_target().]
https://bugs.freedesktop.org/show_bug.cgi?id=49463
https://bugzilla.redhat.com/show_bug.cgi?id=810722
Diffstat (limited to 'src/test/test-loopback.c')
0 files changed, 0 insertions, 0 deletions