Bug#756103: systemd should be more forgiving of fstab errors

2014-08-12 Thread Andrei POPESCU
On Lu, 11 aug 14, 23:53:54, Michael Biebl wrote:
 Am 11.08.2014 23:35, schrieb Andrei POPESCU:
  I have been thinking about this incident since then and watching all the 
  system doesn't boot due to fstab errors reports (I'm subscribed to 
  both -user and -pkg-systemd-maintainers).
  
  I'm not sure it's a good idea to just fail the boot completely whenever 
  there are errors like mine in fstab, but instead it would be much 
  friendlier if systemd would try to bring up as much of the system as 
  possible and start the emergency console only if e.g. / and /usr are 
  missing.
 
 
 I already commented on that. I think it's wrong to just continue booting
 and starting potentially critical services.
 How is systemd supposed to know which file systems are vital?
 
It can't, of course (nor should it), unless receiving enough information 
from the admin, but see below.

 You might have database on separate partitions and you might risk losing
 data if the services are started but the partitions aren't available.

I understand these concerns, however:

1. it seems very brittle to me that a wrong fstab entry is capable of 
blocking the entire boot. This will be mitigated once emergency mode is 
fixed, but still won't be much comfort for headless systems.

2. sysv-rc would not stop either, so this would not be a regression

Another possibility would be if admins could designate specific 
filesystems as critical for booting with a fstab parameter like 
'bootwait', where systemd stops if that particular filesystem couldn't 
be mounted.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Bug#756103: systemd should be more forgiving of fstab errors

2014-08-11 Thread Andrei POPESCU
Control: reopen -1
Control: severity -1 wishlist
Control: retitle -1 systemd should be more forgiving of fstab errors

On Sb, 26 iul 14, 18:54:01, Andrei POPESCU wrote:
 On Sb, 26 iul 14, 17:29:21, Michael Biebl wrote:
  
  You simply have a typo here :-P
  
  udf,iso9660,user,noauto should be
  udf,iso9660 user,noauto
  
  note the space vs ','
  
  Closing the bug as a misconfiguration issue.
 
 Oh, this is embarrassing, I just fixed that yesterday, because I 
 didn't realise those don't belong together.
 
 Now I replaced the ',' with a tab so that I don't make this mistake 
 again next time I look at my fstab before my first green tea cup. Sorry 
 to have wasted your time :(

Hi again,

I have been thinking about this incident since then and watching all the 
system doesn't boot due to fstab errors reports (I'm subscribed to 
both -user and -pkg-systemd-maintainers).

I'm not sure it's a good idea to just fail the boot completely whenever 
there are errors like mine in fstab, but instead it would be much 
friendlier if systemd would try to bring up as much of the system as 
possible and start the emergency console only if e.g. / and /usr are 
missing.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Bug#756103: systemd should be more forgiving of fstab errors

2014-08-11 Thread Michael Biebl
Am 11.08.2014 23:35, schrieb Andrei POPESCU:
 I have been thinking about this incident since then and watching all the 
 system doesn't boot due to fstab errors reports (I'm subscribed to 
 both -user and -pkg-systemd-maintainers).
 
 I'm not sure it's a good idea to just fail the boot completely whenever 
 there are errors like mine in fstab, but instead it would be much 
 friendlier if systemd would try to bring up as much of the system as 
 possible and start the emergency console only if e.g. / and /usr are 
 missing.


I already commented on that. I think it's wrong to just continue booting
and starting potentially critical services.
How is systemd supposed to know which file systems are vital?

You might have database on separate partitions and you might risk losing
data if the services are started but the partitions aren't available.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature