X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C77ACB.724B9410@onstor-exch02.onstor.net>; Mon, 9 Apr 2007 10:21:01 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Delorean can't do a system config copy to a 2.2 system
Date: Mon, 9 Apr 2007 10:21:01 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02215711@onstor-exch02.onstor.net>
In-Reply-To: <20070409093018.3c6e5487@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Delorean can't do a system config copy to a 2.2 system
Thread-Index: Acd6xFzpbqOZ2oROTqOoYojFxMYX1AABZKwQ
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>

I just checked the fstab on the secondary flash, it has one, but it is
wrong. My primary flash is wd0, the secondary flash's fstab has wd0
where it should be wd1. Hmm, I thought flash install got this right. But
come to think of it, I don't believe I ever checked. It is probably this
way because the system was never booted from that flash after the flash
install. But what I am attempting to do is a common practice, in-house
perhaps, but very much needed in development and QA.

vi /mnt1/etc/fstab
/dev/wd0a / ffs ro,noatime 1 1
/dev/wd0e /tmp ffs rw 1 2
/dev/wd0d /usr ffs ro,noatime 1 2
/dev/wd0g /usr/local/agile ffs ro,noatime 1 2
/dev/wd0f /var ffs rw 1 2
/dev/wd0h /usr/local/agile/conf ffs rw 1 2

I just changed the wd0s to wd1 and ran the system config copy and it
worked. I have a work-around so I can keep going on my tests.

Larry

-----Original Message-----
From: Andy Sharp=20
Sent: Monday, April 09, 2007 9:30 AM
To: Larry Scheer
Cc: Tim Gardner
Subject: Re: Delorean can't do a system config copy to a 2.2 system

Pfft, it's not me.  It's common knowledge the clusterdb and other
config files may not be backwards compatible.

As for the flash-install, it probably doesn't put an fstab file on the
CF card, which would account for the problem there.  That's a bug in
flash-install that can be fixed.




On Sat, 7 Apr 2007 11:37:12 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> This can't be. We can't start saying this is WAD. If so you changed a
> working design and disable a common practice done by engineering and
> QA to rapidly switch systems between revs.
>=20
> It is common to down-rev a system in QA and engineering by doing a
> flash install then doing a system config copy and then copying a
> saved cluster-db of an old release that matches the system to the
> seconday flash and rebooting.
>=20
> We have done this for years. You just can't take away this capability
> and say it is WAD. It can take many hours to reconfigure a system and
> re-build a cluster database with all the volumes, virtual servers,
> mirrors, snapshots and the like.
>=20
> You have taken away a proceedure that took only minutes to one that
> takes several hours. This can't happen.
>=20
> Sorry, but you need to fix this. I won't be the only one to say so.
>=20
> By the way this is still broken in the latest Delorean build.
>=20
> Larry
>=20
> -----Original Message-----
> From: Andy Sharp
> Sent: Fri 4/6/2007 5:57 PM
> To: Larry Scheer
> Cc: Tim Gardner
> Subject: Re: Delorean can't do a system config copy to a 2.2 system
> =20
> WAD
>=20
> Not a supported operation to copy system config backwards to an older
> version.
>=20
> Besides, first you have to boot the one you installed with
> flash_install because I think flash_install doesn't put an fstab file
> on there; that's done during initial config process.
>=20
> Good luck,
>=20
> a
>=20
> On Fri, 6 Apr 2007 17:32:51 -0700 "Larry Scheer"
> <larry.scheer@onstor.com> wrote:
>=20
> > Andy,
> > 	I was setting up Tim's filer (eng45, a cheetah) to do the
> > unit test of the 2.2.X maintenance release that has the new upgrade
> > features. The primary flash has the latest Delorean build (sync'ed
> > today) loaded on it.
> >=20
> > I did a flash install of 2.2.2.1 on the secondary flash and I
> > installed Ken's build of Delorean done on Tuesday (submittal 11)  on
> > the primary flash I could not do a system config copy to place the
> > config info on the secondary flash. I got this error message:
> >=20
> > system config copy
> > mount_secondary: Can't mount /dev/wd0a on /mnt1/: Device busy(16)
> > Unmounting /mnt1/usr/local/agile/conf...failed!
> > Error: No such file or directory(9)
> > Unmounting /mnt1/var...failed!
> > Error: No such file or directory(9)
> > Unmounting /mnt1/usr/local/agile...failed!
> > Error: No such file or directory(9)
> > Unmounting /mnt1/usr...failed!
> > Error: No such file or directory(9)
> > Unmounting /mnt1/tmp...failed!
> > Error: No such file or directory(9)
> > Unmounting /mnt1/...failed!
> > Error: Invalid argument(9)
> >=20
> > I will upgrade to the latest build to see if the problem still is
> > there. (I didn't have a problem with today's build upgrading the
> > config on the secondary flash of a bobcat. But the secondary flash
> > had Delorean installed on it.
> >=20
> > We need this capability to work on flashes that have an older
> > release (i.e 2.2 or 1.3.3) than the primary.=20
> >=20
> > I need to take off so I won't be able to see if the latest build can
> > update a 2.2.2.1 flash with a Delorean config until much later.
> > (Maybe Monday?)=20
> >=20
> > Larry
>=20
