raw device for solaris(sparc)

tfhkc...@taifuji.com

unread,

Oct 31, 2000, 11:02:14 AM10/31/00

to

Hello,

I am now testing Informix-dynamic server 9.2 for
Sun Solaris 8, I have something can not understand
for Solaris 8.

(1) I used raw device /dev/rdsk/c0t1d0s0 (2GB, for rootdb)
/dev/rdsk/c0t1d0s1 (2GB, for
additioanl chunk)

(2) after I initialized the rootdb using onmonitor, the
partition of /dev/rdsk/c0t1d0s0 disappeared. (partition crupt,
partition crash)

(3) I used the format utility of solaris 8 to partition the
disk.

Can anybody tell me how to use raw device in Sun Solaris 8 (Sparc)?

Thanks for your help.

Kelly Loyd

unread,

Oct 31, 2000, 2:46:54 PM10/31/00

to

G'day

On our Solaris machines, we must use an offset of approximately 50 K -
Solaris stores the Volume Table of Contents ( VTOC ) in the first blocks
on the partition and when Informix initialises with no offset, it wipes
this information rendering the disk 'corrupt'

Put a value in the chunk OFFSET field in onmonitor or use the -o option
in onspaces.

Regards
Kelly

Doug McAllister

unread,

Nov 2, 2000, 5:24:03 PM11/2/00

to

First: NEVER,NEVER,NEVER refer to the direct device name, make a link
and refer to that. If the device names change, you only need to change
the link name.

Second: Solaris comes with a volume manager which is a "lite" version of
Veritas. Create logical volumes and use these. They end up in
/dev/vx/rdsk. I create logical volumes named infchunk1, infchunk2, etc.
Never need an offset.

B-T-W, have you run into the Solaris 8,Informix,TCP/IP bug yet?

doug.mcallister.vcf

smooth1

unread,

Nov 6, 2000, 3:00:00 AM11/6/00

to

Add an offset of at least 8K

tfhkc...@taifuji.com wrote in message
<8tmr0b$2g...@imsp212.netvigator.com>...

philippe

unread,

Nov 7, 2000, 3:00:00 AM11/7/00

to

- Sorry for bad english -
I've no Sun servers, but I imagine you can translate What I say in your OS

1 - When the partition is mounted, Unix writes datas into the first pages of
the
partition.
2 - When you initialize you raw device, if offset is 0, informix overwrites
these datas. -> crash

So :
1 - Create a link (such as /dev/rootraw, /dev/dataraw1, ...) with your
partitions /dev/rdsk....
If you have to change the physical partition (hardware failure), you
can create a new raw device
in another partition and you have just to change the link to match the
/dev/raw before restauring.
When you create your chunks, use the link name.
This link MUST be in the (?) rc.d directory (or similar in Sun system)
2 - NEVER (auto) mount your partition (in UnixWare and System5, it is in
/dev/vfstab)
Here is an example (anonymised)
#
# Table of filesystem defaults.
#
# special fsckdev
mountp fstype fsckpass automnt mntopts
/dev/dsk/f1 /dev/dsk/f1
/install s5 - no -
/dev/dsk/1s1 /dev/rdsk/1s1
/mnt1 vxfs 1 yes -
#/dev/dsks/XXX151/s1 /dev/rdsks/XXX151/s1 RAW DEVICE RAW1
#/dev/dsks/XXX151/s2 /dev/rdsks/XXX151/s2 RAW DEVICE RAW2
/dev/dsks/XXX151/s3 /dev/rdsks/XXX151/s3 /oss11
vxfs 1 yes -
etc...
I 've links /dev/.../151/s1 with "RAW1" etc..
The "#" is only to show the patition in the vfstab but it is not mounted

3 - Keep 8 k (I prefer 96 K) for offset of any chunks that are at the
begenning of the partition
That prevents from accidental mount ( the first pages of rootdbs will
never be overwriten
by Unix)

"smooth1" <smo...@iclway.co.uk> a écrit dans le message news:
3a06e...@news2.vip.uk.com...

> Add an offset of at least 8K
>
> tfhkc...@taifuji.com wrote in message
> <8tmr0b$2g...@imsp212.netvigator.com>...