From: Eric.Chacron@alcatel.fr
Date: Mon Jul 22 2002 - 09:10:27 EDT
Thanks to Dr. Thomas P. Blinn and Lucien HERCAUD for their answers.
Tru64 V5 provides backward compatibility with Tru54 V4 for ADVFS (versions
3 and 4) and LSM.
For that V5 maintains supports of both new and old metadata, but
it seems better to migrate to the new format in order to get benefit
from the new release.
In my case the correlation with the quotacheck error is not so evident.
I'll close this report for the moment.
Eric Chacron
ALcatel CNG/CTO
---------------------- Forwarded by Eric CHACRON/FR/ALCATEL on 22/07/2002
14:55 ---------------------------
"Dr Thomas.Blinn@HP.com" <tpb on 22/07/2002 14:40:07
To: Eric CHACRON/FR/ALCATEL@ALCATEL
cc:
Subject: Re: V5.1 / 4.0F ADVFS and LSM metadata compatibles ?
>
> Thnaks for your answer.
> We tried and got a "quotacheck" error on one file system ( i have join
the
> console output).
>
>
> My purpose is also to understand the "internals" as i know that ADVFS
> internal structures
> are very different in Tru64 V5 than the prior release i would like to
knwo
> how this
> backward compatibility is managed : implicit conversion on first mount /
> open of
> the file metadata or old ADVFS branches of code maintained just for this
> case ?
>
> Eric
If quotacheck complains, try running it again. Disk quota support in
Tru64 UNIX is flaky at best, and AdvFS doesn't make it better.
Being that as it may, the old AdvFS code co-exists in the kernel with
the new code. There no automatic or implicit conversion of any of
your domains; I believe there are tools to help convert a domain in
place, but I'd have to go read the documentation (carefully) to be
sure; the obvious way to convert a domain is one fileset at a time,
using vdump and vrestore. Since the eventual demise of Tru64 UNIX
and Alpha is a known quantity, you can be reasonably confident that
other than bug fixes, there will be no significant change in what is
AdvFS in the Tru64 UNIX product. So converting to the Tru64 UNIX V5
on disk formats (which are called the version 4 formats in the AdvFS
code, since there was no AdvFS in the old DEC OSF/1 V1.x products) is
a reasonably safe proposition, as long as you never intend to go back
to accessing the file systems with a Digital UNIX V4.x system. There
is no support in V4.x for the new formats, and there never will be.
Similar things happen for LSM -- the new version is capable of dealing
with the old metadata (and logging and so forth), but you get better
support if you migrate to the new formats and the new code base.
Tom
Dr. Thomas P. Blinn + Tru64 UNIX Software + Hewlett-Packard Company
Internet: tpb@zk3.dec.com, thomas.blinn@compaq.com, thomas.blinn@hp.com
110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
Technology Partnership Engineering Phone: (603) 884-0646
ACM Member: tpblinn@acm.org PC@Home: tom@felines.mv.net
Worry kills more people than work because more people worry than work.
Keep your stick on the ice. -- Steve Smith ("Red Green")
My favorite palindrome is: Satan, oscillate my metallic sonatas.
-- Phil Agre, pagre@alpha.oac.ucla.edu
Yesterday it worked / Today it is not working / UNIX is like that
-- apologies to Margaret Segall
Opinions expressed herein are my own, and do not necessarily represent
those of my employer or anyone else, living or dead, real or imagined.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:46 EDT