Reply to post: Re: @jerky_rs read the documentation

Linux greybeards release beta of systemd-free Debian fork


Re: @jerky_rs read the documentation

I cannot recall ever having a sysvinit-based system toss me into single user mode because a filesystem mount took "too long" due to a forced fsck. Sure, I might have had a filesystem be unavailable for a time while a mount-time fsck completed but I never had the "entire system" be unavailable while I was running that fsck by hand. (In a pinch, I've commented out the filesystem entry in /etc/fstab, rebooted the system, and hoped systemd get confused by another big filesystem needing an fsck.) I'm sure there's a means of extending the time-out that systemctl imposes on mounts but I'll undoubtedly get burned again unless I make it ten times longer. (And will even /that/ be long enough? I haven't sat there with a stopwatch timing an fsck of a multi-terabyte filesystem.)

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Biting the hand that feeds IT © 1998–2019