This might be influenced by those numbers at the end of the fstab entry.. The last one indicates whether fsck should be run against it. If yours is 0, then that should prevent Linux from requiring it there.
I'm not sure how badly you mucked up the syntax though... As others have said - use 'mount -a' to check each time you update fstab. And -- error recovery is there.. you are put into a shell so you can try and correct it :-) Scott Rohling On Thu, Jun 9, 2011 at 10:21 AM, Bauer, Bobby (NIH/CIT) [E] < baue...@mail.nih.gov> wrote: > I recently had a typo in fstab for a new file system I tried to add and my > system would not come back up. Thanks to everybody for helping me out and > getting my system back without a major recovery effort. > > Any reason why zLinux dies when it finds a bad entry in fstab even though > the filesystem is not needed to bring the system up? Do other linux/unix > system do this? Seems a little short on error recovery but then I'm speaking > as an old MVS dinosaur. > > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
