Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!hellgate.utah.edu!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Can V1.2 file systems be mounted under 3.0
Message-ID: <7805@cbmvax.UUCP>
Date: 1 Sep 89 17:16:12 GMT
References: <1444@esat.kuleuven.ac.be> <7802@cbmvax.UUCP> <1989Sep1.125332.9286@acd4.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 26

In article <1989Sep1.125332.9286@acd4.UUCP> mjb@acd4.UUCP ( Mike Bryan          ) writes:
> In article <7802@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
> >In article <1444@esat.kuleuven.ac.be> ELSEN@esat.kuleuven.ac.be (Marc Elsen) writes:
> >>     I will soon be upgrading from Ultrix 1.2 to 3.1 and I was wondering
> >> whether V1.2 file systems can still be mounted under Ultrix 3.1.
> >
> >The clean flag is basically advisory - if there have been no changes to the
> >filesystem since it was mounted/unmouted, fsck -p can skip checking it and
> >mount doesn't complain when you try to mount it.  You can still mount an
> >old (1.2) or "dirty" filesystem by using the "-o force" option to mount.
> 
> You don't need to use the "-o force" option to mount.  Assuming you
> have the 1.2 filesystems in /etc/fstab, an fsck will automatically be
> run on that filesystem when the system is booted.  The fsck will
> properly setup the "clean byte", and those filesystems will then be
> 3.0 filesystems.  No problem!

Of course, assuming it's a one time cutover.  If you're stepping gingerly,
you may not want to have 3.x fsck "improve" the filesystem right off and
if you're switching back and forth in a test mode, you'd have to fsck
the filesystem again every time 1.2 gets its claws into it...

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)