Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Jan 1999 12:47:44 GMT
From:      mfer@leirianet.pt (M Ferreira)
To:        freebsd-questions@FreeBSD.ORG
Cc:        grog@lemis.com
Subject:   Fatal trap while reading vinum config from drive
Message-ID:  <36b85b8f.93466878@mail2.leirianet.pt>

next in thread | raw e-mail | index | archive | help

I have 4 disks labeled:

da0s1
  a:   204800        0    4.2BSD        0     0     0   # (Cyl.    0 -
143*)
  c:  4226725        0    unused        0     0         # (Cyl.    0 -
2955*)
  e:  1972224   204800    4.2BSD        0     0     0   # (Cyl.  143*-
1522*)
  f:  2049701  2177024    unused        0     0         # (Cyl. 1522*-
2955*)

da1s1
  b:   538624        0      swap                        # (Cyl.    0 -
376*)
  c:  4226725        0    unused        0     0         # (Cyl.    0 -
2955*)
  e:  3688101   538624    unused        0     0         # (Cyl.  376*-
2955*)

da2s1
  c:  8888924        0    unused        0     0         # (Cyl.    0 -
553*)
  e:  8888924        0    unused        0     0         # (Cyl.    0 -
553*)

da3s1
  c:  8888924        0    unused        0     0         # (Cyl.    0 -
553*)
  e:  8888924        0    unused        0     0         # (Cyl.    0 -
553*)

My intention is to have 

/dev/da1s1b             none            swap    sw              0
0
/dev/da0s1a             /               ufs     rw              1
1
/dev/da0s1e             /usr            ufs     rw              2
2
/dev/vinum/small        /arch           ufs     rw              2
3
/dev/vinum/big          /data           ufs     rw              2
4

so, i've created the following config:

drive a device /dev/da0s1f
drive b device /dev/da1s1e
drive c device /dev/da2s1e
drive d device /dev/da3s1e

volume small
        plex org concat
                sd len 2047735b drive a
                sd len 3686135b drive b

volume big
        plex org striped 128b
                sd len 8888055b drive c
                sd len 8888055b drive d

disk length values are shortened 265b in order to hold vinum config.

vinum create 'config' gives me:

Configuration summary

Drives:         4 (4 configured)
Volumes:        2 (4 configured)
Plexes:         2 (8 configured)
Subdisks:       4 (16 configured)

D a                     State: up       Device /dev/da0s1f
D b                     State: up       Device /dev/da1s1e
D c                     State: up       Device /dev/da2s1e
D d                     State: up       Device /dev/da3s1e

V small                 State: up       Plexes:       1 Size:
2799 MB
V big                   State: up       Plexes:       1 Size:
8679 MB

P small.p0            C State: up       Subdisks:     2 Size:
2799 MB
P big.p0              S State: up       Subdisks:     2 Size:
8679 MB

S small.p0.s0           State: up       PO:        0  B Size:
999 MB
S small.p0.s1           State: up       PO:      999 MB Size:
1799 MB
S big.p0.s0             State: up       PO:        0  B Size:
4339 MB
S big.p0.s1             State: up       PO:       64 kB Size:
4339 MB

Just to confirm everything is fine, init small.p0 and init big.p0
finish successfully.

newfs -v /dev/vinum/rbig finishes successfully with one minor quirk
wich is:

Warning: 530 sector(s) in last cylinder unallocated
/dev/vinum/rbig:        17776110 sectors in 4340 cylinders of 1
tracks, 4096 sectors
        8679.7MB in 272 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
super-block backups (for fsck -b #) at:
 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320,
589856,

Same thing with newfs -v /dev/vinum/rbig:

Warning: 530 sector(s) in last cylinder unallocated
/dev/vinum/rsmall:      5733870 sectors in 1400 cylinders of 1 tracks,
4096 sectors
        2799.7MB in 88 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
super-block backups (for fsck -b #) at:
 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320,
589856,

mounting /dev/vinum/small and /dev/vinum/big under /arch and /data
goes ok:

Filesystem       1K-blocks     Used    Avail Capacity  Mounted on
/dev/da0s1a          99183    37265    53984    41%    /
/dev/da0s1e         955591   763377   115767    87%    /usr
procfs                   4        4        0   100%    /proc
/dev/vinum/small   2778213        1  2555955     0%    /arch
/dev/vinum/big     8613858        1  7924749     0%    /data

Now the bad news. Without touching $vinum_slices in rc.conf, i tried
to reboot and manually do a vinum read /dev/da0 /dev/da1 /dev/da2
/dev/da3 (compatibility slice naming should be ok, i guess) and i get:

Fatal trap 18: integer divide fault while in kernel mode

How can I diagnose and correct this?

I'm running 3.0-stable cvsuped this weekend.

tia

M Ferreira


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36b85b8f.93466878>