Re: disk busy on startup

[Marcus Brinkmann]

On Tue, Aug 13, 2002 at 04:39:33PM -0700, James Morrison wrote:
> --- Wolfgang_J?hrling <wolfgang@pro-linux.de> wrote:
> > James Morrison <rocketmail_com@rocketmail.com> wrote:
> > > What would happen if the module line in grub were to have --readonly, eg
> > > module /hurd/ext2fs.static --readonly ... ?
> > 
> > I can tell you what actually happens: Everything works perfect!
> > Thanks, this has fixed my system.  But as "fsysopts /" gives me
> > 
> > /hurd/ext2fs.static --writable --store-type=typed device:hd1s2
> > 
> > I wonder, should --readonly be used in any case for the root file
> > system?
> 
>  Given this and that Debian GNU/Linux boots the linux kernel with readonly,
> should we always use --readonly?

Probably.  It makes sense to me, although I would like to where the system
becomes busy.  Can someone of you who see the bug try the following:

Reproduce the bug in a neighborhurd.  Find out where the fs finds it is
busy.  Then find where the fs makes itself busy (sets a bit, or adds some
element to a list).  Set a break point there and see what happened :)

>  I'm going to do the hard upgrade now.

Thanks, more testing is better.  As this problem didn't occur before, we
should add a note about the work around to the UPDATE doc, change the
install manual, and upload the packages.

Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    marcus@gnu.org
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/