xfs
[Top] [All Lists]

Re: 1.0 Installer

To: Mike Burger <mburger@xxxxxxxxxxxxxx>
Subject: Re: 1.0 Installer
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Thu, 24 May 2001 22:54:49 +0200
Cc: Eric Sandeen <sandeen@xxxxxxx>, <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.33.0105241605410.17475-100000@xxxxxxxxxxxxxxxxx net>
References: <4.3.2.7.2.20010524212751.037873b8@xxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
At 16:06 24-5-2001 -0400, Mike Burger wrote:
On Thu, 24 May 2001, Seth Mos wrote:

> At 14:15 24-5-2001 -0500, Eric Sandeen wrote:
> >Seth Mos wrote:
> > >
> > > The installer seems to barf when trying to Upgrade a installation of a
> > > system where the XFS filesystem is not clean.
> > > I had to boot the machine another time to recover the filesystem to a clean
> > > state before I could try to upgrade it.
> >
> >Hm, we didn't anticipate this scenario.  :)  FWIW, the same thing
> >happens under ext2, if it detects that a filesystem was not cleanly
> >unmounted, the install won't continue.
>
> Uhm, that shouldn't happen with a journaling fs :D

Why not?  The installer doesn't invoke the cleanup routines...it just sees
a filesystem that was not cleanly unmounted.

How can one "see" a fs that is not cleanly unmounted? I mean what does anaconda do to check for that?
With ext2 you get a warning, journaling fs on the other hand know what to do.
It would be great if it could just recover the fs on mount and continue.

Cheers

--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.


<Prev in Thread] Current Thread [Next in Thread>