Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Nov 2000 21:05:50 -0800
From:      "Rod Taylor" <rbt@zort.on.ca>
To:        <freebsd-stable@freebsd.org>
Subject:   Fstab issues...
Message-ID:  <007e01c05766$8b5b48b0$6500000a@jester>

next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C05723.7D164FE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

While playing around I managed to fully erase /etc/fstab (on purpose =
actually :).

Anyhow, on a reboot something rather mistifying happened.  It was =
obvious that it wouldn't be able to find any devices to mount, and =
mounted the / partition read only.  Now, the strange thing is that I was =
unable to mount / for write (mount /dev/ad0s1a /) without first creating =
an fstab file with a fixit disk.

I certainly don't believe this is expected as in 2.2.x I seem to =
remember having the ability to create fstab if it was killed.


As to why I deleted it, I was going to CVS /etc on some production boxes =
and wanted to know what the worst case scenario would be if there was a =
crash before the initial checkout.  The results were using a fixit =
floppy.

Can this be rectified to not make mount depend on /etc/fstab existing?

------=_NextPart_000_007B_01C05723.7D164FE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>While playing around I managed to fully =
erase=20
/etc/fstab (on purpose actually :).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Anyhow, on a reboot something rather =
mistifying=20
happened.&nbsp; It was obvious that it wouldn't be able to find any =
devices to=20
mount, and mounted the / partition read only.&nbsp; Now, the strange =
thing is=20
that I was unable to mount / for write (mount /dev/ad0s1a /) without =
first=20
creating an fstab file with a fixit disk.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I certainly don't believe this is =
expected as in=20
2.2.x I seem to remember having the ability to create fstab if it was=20
killed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>As to why I deleted it, I was going to =
CVS /etc on=20
some production boxes and wanted to know what the worst case scenario =
would be=20
if there was a crash before the initial checkout.&nbsp; The results were =
using a=20
fixit floppy.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Can this be rectified to not make mount =
depend on=20
/etc/fstab existing?</FONT></DIV></BODY></HTML>

------=_NextPart_000_007B_01C05723.7D164FE0--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?007e01c05766$8b5b48b0$6500000a>