Hello all,
Thanx to all that answered me, It helped me better understand the
point... because
that is the point... understanding merroring and solaris booting :)
My question was:
once the system is up and running, is there a way to knwo what
partition
actually been booted up?
Probably the best anwser would be :
A booted up system has necessarely booted off :
- the first "okay" disk in the eeprom list : boot-device
I ll summarize any further comments i might recieve.
Mohamed LRHAZI
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
ddunham@taos.com:
They both are, that's the point. It does load the kernel of one disk
(set by your boot-device), but reads and writes after that point go to
both devices simultaneously.
If it's not a production box, pull out one of the disks. Then put it
back in and repair your mirror.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
gjenson@spillman.com:
I don't know that the system can really tell you that. We'll see if
anyone
has anything useful to say.
I usually pull the "c0t0d0s0" disk that is the default boot-disk. You
must
have set the boot-device to be both sides of the mirror if you have a
chance
of booting off of the other disk.
Gary
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Mark_Neill@CSX.com:
You didn't boot on a submirror. Or more exactly, you booted on both
submirrors.
Depending on how you set up your mirror, you're either reading the
mirror
round-robin (blocks 1-8 from d01, 9-16 from d02, 17-24 from d01, etc etc
etc), or reading blocks from the drive on which the heads are closest to
the
block you're requesting.
Either way, you're not guaranteed to be getting data from any particular
submirror in any particular order.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
kevin@web.xcdg.xerox.com:
run:
eeprom | grep boot-device
that will tell the device that the system goes to by default.
Hope that helps.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Matthew.Stier@fnc.fujitsu.com:
First, if you haven't run '/usr/sbin/installboot' against the secondary
mirror of the root partition, your question is moot. You won't be able
to
boot on the secondary mirror anyway.
Second, if you have installed the boot block on the secondary mirror,
the
answer to the question become very simple.
"Whatever disk did you specify at boot time."
The OpenBoot Prom (OBP) has several aliases setup various disks. The
aliases 'disk' and 'disk0' refer to the systems default boot disk. If
you
are lucky enough to have selected a pre-aliased drive, you could then
boot
of that disk as "boot <aliasname>". If you are not, you will need to
find
information about setting up aliases, and create your own for the
secondary
mirror you have choosen.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
simon.millard@barclays.co.uk:
look in the file /etc/systems and it will tell you.
You always boot from slice 0
Simon
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Mike.Salehi@usa.xerox.com:
You did not boot off of any one partition, the machine
booted off of d0 and some I/O may have come from one or
the other partition.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
goos@xs4all.nl:
If you have not changed eeprom aliases for default boot-device you have
booted
from the same disk as before it was mirrored.
Oscar Goosens
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Baurjan.Ismagulov@gantek.com:
hi,
while being unaware of the method you ask for, i can suppose that you
can test
your system in other ways. let's assume that you mirrored c0t0d0s0 and
c0t1d0s0.
then, you can explicitly boot from disk0 and disk1 (from the obp). to be
sure, you
can even remove another disk (but you'll have to play with state
database
replicas if you have only two disks).
hope this helps,
baurjan.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:07 CDT