1 .\" Hey, Emacs, edit this file in -*- nroff-fill -*- mode
3 .\" Copyright (c) 1997, 1998
4 .\" Nan Yang Computer Services Limited. All rights reserved.
6 .\" This software is distributed under the so-called ``Berkeley
9 .\" Redistribution and use in source and binary forms, with or without
10 .\" modification, are permitted provided that the following conditions
12 .\" 1. Redistributions of source code must retain the above copyright
13 .\" notice, this list of conditions and the following disclaimer.
14 .\" 2. Redistributions in binary form must reproduce the above copyright
15 .\" notice, this list of conditions and the following disclaimer in the
16 .\" documentation and/or other materials provided with the distribution.
17 .\" 3. All advertising materials mentioning features or use of this software
18 .\" must display the following acknowledgement:
19 .\" This product includes software developed by Nan Yang Computer
21 .\" 4. Neither the name of the Company nor the names of its contributors
22 .\" may be used to endorse or promote products derived from this software
23 .\" without specific prior written permission.
25 .\" This software is provided ``as is'', and any express or implied
26 .\" warranties, including, but not limited to, the implied warranties of
27 .\" merchantability and fitness for a particular purpose are disclaimed.
28 .\" In no event shall the company or contributors be liable for any
29 .\" direct, indirect, incidental, special, exemplary, or consequential
30 .\" damages (including, but not limited to, procurement of substitute
31 .\" goods or services; loss of use, data, or profits; or business
32 .\" interruption) however caused and on any theory of liability, whether
33 .\" in contract, strict liability, or tort (including negligence or
34 .\" otherwise) arising in any way out of the use of this software, even if
35 .\" advised of the possibility of such damage.
37 .\" $FreeBSD: src/share/man/man4/vinum.4,v 1.22.2.9 2002/04/22 08:19:35 kuriyama Exp $
44 .Nd Logical Volume Manager
50 is a logical volume manager inspired by, but not derived from, the Veritas
51 Volume Manager. It provides the following features:
54 It provides device-independent logical disks, called \fIvolumes\fP. Volumes are
55 not restricted to the size of any disk on the system.
57 The volumes consist of one or more \fIplexes\fP, each of which contain the
58 entire address space of a volume. This represents an implementation of RAID-1
59 (mirroring). Multiple plexes can also be used for
60 .\" XXX What about sparse plexes? Do we want them?
64 Increased read throughput.
66 will read data from the least active disk, so if a volume has plexes on multiple
67 disks, more data can be read in parallel.
69 reads data from only one plex, but it writes data to all plexes.
71 Increased reliability. By storing plexes on different disks, data will remain
72 available even if one of the plexes becomes unavailable. In comparison with a
73 RAID-5 plex (see below), using multiple plexes requires more storage space, but
74 gives better performance, particularly in the case of a drive failure.
76 Additional plexes can be used for on-line data reorganization. By attaching an
77 additional plex and subsequently detaching one of the older plexes, data can be
78 moved on-line without compromising access.
80 An additional plex can be used to obtain a consistent dump of a file system. By
81 attaching an additional plex and detaching at a specific time, the detached plex
82 becomes an accurate snapshot of the file system at the time of detachment.
83 .\" Make sure to flush!
86 Each plex consists of one or more logical disk slices, called \fIsubdisks\fP.
87 Subdisks are defined as a contiguous block of physical disk storage. A plex may
88 consist of any reasonable number of subdisks (in other words, the real limit is
89 not the number, but other factors, such as memory and performance, associated
90 with maintaining a large number of subdisks).
92 A number of mappings between subdisks and plexes are available:
95 \fIConcatenated plexes\fP\| consist of one or more subdisks, each of which
96 is mapped to a contiguous part of the plex address space.
98 \fIStriped plexes\fP\| consist of two or more subdisks of equal size. The file
99 address space is mapped in \fIstripes\fP, integral fractions of the subdisk
100 size. Consecutive plex address space is mapped to stripes in each subdisk in
115 "plex 0" at SD0.n+(0,.2)
116 "subdisk 0" rjust at SD0.w-(.2,0)
117 "subdisk 1" rjust at SD1.w-(.2,0)
118 "subdisk 2" rjust at SD2.w-(.2,0)
122 The subdisks of a striped plex must all be the same size.
124 \fIRAID-5 plexes\fP\| require at least three equal-sized subdisks. They
125 resemble striped plexes, except that in each stripe, one subdisk stores parity
126 information. This subdisk changes in each stripe: in the first stripe, it is the
127 first subdisk, in the second it is the second subdisk, etc. In the event of a
130 will recover the data based on the information stored on the remaining subdisks.
131 This mapping is particularly suited to read-intensive access. The subdisks of a
132 RAID-5 plex must all be the same size.
133 .\" Make sure to flush!
137 are the lowest level of the storage hierarchy. They represent disk special
141 offers automatic startup. Unlike UNIX file systems,
143 volumes contain all the configuration information needed to ensure that they are
144 started correctly when the subsystem is enabled. This is also a significant
145 advantage over the Veritas\(tm File System. This feature regards the presence
146 of the volumes. It does not mean that the volumes will be mounted
147 automatically, since the standard startup procedures with
149 perform this function.
151 .Sh KERNEL CONFIGURATION
153 is currently supplied as a kernel loadable module (kld), and does not require
154 configuration. As with other klds, it is absolutely necessary to match the kld
155 to the version of the operating system. Failure to do so will cause
157 to issue an error message and terminate.
159 It is possible to configure
161 in the kernel, but this is not recommended. To do so, add this line to the
162 kernel configuration file:
163 .Bd -literal -offset indent
168 The current version of
170 both the kernel module and the user program
172 include significant debugging support. It is not recommended to remove
173 this support at the moment, but if you do you must remove it from both the
174 kernel and the user components. To do this, edit the files
175 .Pa /usr/src/sbin/vinum/Makefile
177 .Pa /usr/src/sys/modules/vinum/Makefile
178 and edit the CFLAGS variable to remove the -DVINUMDEBUG option. If you have
181 into the kernel, either specify the line
182 .Bd -literal -offset indent
186 in the kernel configuration file or remove the -DVINUMDEBUG option from
187 .Pa /usr/src/sbin/vinum/Makefile
190 If the VINUMDEBUG variables do not match,
192 will fail with a message
193 explaining the problem and what to do to correct it.
196 was previously available in two versions: a freely available version which did
197 not contain RAID-5 functionality, and a full version including RAID-5
198 functionality, which was available only from Cybernet Systems Inc. The present
201 includes the RAID-5 functionality.
206 system. It does not require installation.
207 To start it, start the
209 program, which will load the kld if it is not already present.
212 it must be configured. See
214 for information on how to create a
218 Normally, you start a configured version of
220 at boot time. Set the variable
232 is loaded as a kld (the recommended way), the
235 command will unload it. You can also do this with the
239 The kld can only be unloaded when idle, in other words when no volumes are
240 mounted and no other instances of the
242 program are active. Unloading the kld does not harm the data in the volumes.
243 .Ss CONFIGURING AND STARTING OBJECTS
246 utility to configure and start
251 calls are intended for the use of the
253 configuration program only. They are described in the header file
254 .Pa /sys/sys/vinumio.h
256 Conventional disk special devices have a
258 in the second sector of the device. See
260 for more details. This disk label describes the layout of the partitions within
263 does not subdivide volumes, so volumes do not contain a physical disk label.
266 implements the ioctl calls DIOCGDINFO (get disk label), DIOCGPART (get partition
267 information), DIOCWDINFO (write partition information) and DIOCSDINFO (set
268 partition information). DIOCGDINFO and DIOCGPART refer to an internal
269 representation of the disk label which is not present on the volume. As a
281 serves no useful purpose on a vinum volume. If you run it, it will show you
282 three partitions, a, b and c, all the same except for the fstype, for example:
287 # size offset fstype [fsize bsize bps/cpg]
288 a: 2048 0 4.2BSD 1024 8192 0 # (Cyl. 0 - 0)
289 b: 2048 0 swap # (Cyl. 0 - 0)
290 c: 2048 0 unused 0 0 # (Cyl. 0 - 0)
294 ignores the DIOCWDINFO and DIOCSDINFO ioctls, since there is nothing to change.
295 As a result, any attempt to modify the disk label will be silently ignored.
296 .Sh MAKING FILE SYSTEMS
299 volumes do not contain partitions, the names do not need to conform to the
300 standard rules for naming disk partitions. For a physical disk partition, the
301 last letter of the device name specifies the partition identifier (a to h).
303 volumes need not conform to this convention, but if they do not,
305 will complain that it cannot determine the partition. To solve this problem,
310 For example, if you have a volume
312 use the following command to create a ufs file system on it:
315 # newfs -v /dev/vinum/concat
320 assigns default names to plexes and subdisks, although they may be overridden.
321 We do not recommend overriding the default names. Experience with the
324 volume manager, which allows arbitary naming of objects, has shown that this
325 flexibility does not bring a significant advantage, and it can cause confusion.
327 Names may contain any non-blank character, but it is recommended to restrict
328 them to letters, digits and the underscore characters. The names of volumes,
329 plexes and subdisks may be up to 64 characters long, and the names of drives may
330 up to 32 characters long. When choosing volume and plex names, bear in mind
331 that automatically generated plex and subdisk names are longer than the name
332 from which they are derived.
337 creates or deletes objects, it creates a directory
339 in which it makes device entries for each volume. It also creates the
344 in which it stores device entries for the plexes and subdisks. In addition, it
345 creates two more directories,
348 .Pa /dev/vinum/drive ,
349 in which it stores hierarchical information for volumes and drives.
353 creates three super-devices,
354 .Pa /dev/vinum/control ,
355 .Pa /dev/vinum/Control
357 .Pa /dev/vinum/controld .
358 .Pa /dev/vinum/control
361 when it has been compiled without the VINUMDEBUG option,
362 .Pa /dev/vinum/Control
365 when it has been compiled with the VINUMDEBUG option,
367 .Pa /dev/vinum/controld
370 daemon. The two control devices for
372 are used to synchronize the debug status of kernel and user modules.
378 volumes are not subdivided into partitions, and thus do not contain a disk
379 label. Unfortunately, this confuses a number of utilities, notably
381 which normally tries to interpret the last letter of a
383 volume name as a partition identifier. If you use a volume name which does not
392 in order to tell it to ignore this convention.
395 Plexes do not need to be assigned explicit names. By default, a plex name is
396 the name of the volume followed by the letters \f(CW.p\fR and the number of the
397 plex. For example, the plexes of volume
402 and so on. These names can be overridden, but it is not recommended.
405 Like plexes, subdisks are assigned names automatically, and explicit naming is
406 discouraged. A subdisk name is the name of the plex followed by the letters
407 \f(CW\&.s\fR and a number identifying the subdisk. For example, the subdisks of
418 must be named. This makes it possible to move a drive to a different location
419 and still recognize it automatically. Drive names may be up to 32 characters
427 objects described in the section CONFIGURATION FILE in
432 .Bd -literal -offset indent
435 crwxr-xr-- 1 root wheel 91, 2 Mar 30 16:08 concat
436 crwx------ 1 root wheel 91, 0x40000000 Mar 30 16:08 control
437 crwx------ 1 root wheel 91, 0x40000001 Mar 30 16:08 controld
438 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 drive
439 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 plex
440 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 rvol
441 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 sd
442 crwxr-xr-- 1 root wheel 91, 3 Mar 30 16:08 strcon
443 crwxr-xr-- 1 root wheel 91, 1 Mar 30 16:08 stripe
444 crwxr-xr-- 1 root wheel 91, 0 Mar 30 16:08 tinyvol
445 drwxrwxrwx 7 root wheel 512 Mar 30 16:08 vol
446 crwxr-xr-- 1 root wheel 91, 4 Mar 30 16:08 vol5
450 crw-r----- 1 root operator 4, 15 Oct 21 16:51 drive2
451 crw-r----- 1 root operator 4, 31 Oct 21 16:51 drive4
455 crwxr-xr-- 1 root wheel 91, 0x10000002 Mar 30 16:08 concat.p0
456 crwxr-xr-- 1 root wheel 91, 0x10010002 Mar 30 16:08 concat.p1
457 crwxr-xr-- 1 root wheel 91, 0x10000003 Mar 30 16:08 strcon.p0
458 crwxr-xr-- 1 root wheel 91, 0x10010003 Mar 30 16:08 strcon.p1
459 crwxr-xr-- 1 root wheel 91, 0x10000001 Mar 30 16:08 stripe.p0
460 crwxr-xr-- 1 root wheel 91, 0x10000000 Mar 30 16:08 tinyvol.p0
461 crwxr-xr-- 1 root wheel 91, 0x10000004 Mar 30 16:08 vol5.p0
462 crwxr-xr-- 1 root wheel 91, 0x10010004 Mar 30 16:08 vol5.p1
466 crwxr-xr-- 1 root wheel 91, 0x20000002 Mar 30 16:08 concat.p0.s0
467 crwxr-xr-- 1 root wheel 91, 0x20100002 Mar 30 16:08 concat.p0.s1
468 crwxr-xr-- 1 root wheel 91, 0x20010002 Mar 30 16:08 concat.p1.s0
469 crwxr-xr-- 1 root wheel 91, 0x20000003 Mar 30 16:08 strcon.p0.s0
470 crwxr-xr-- 1 root wheel 91, 0x20100003 Mar 30 16:08 strcon.p0.s1
471 crwxr-xr-- 1 root wheel 91, 0x20010003 Mar 30 16:08 strcon.p1.s0
472 crwxr-xr-- 1 root wheel 91, 0x20110003 Mar 30 16:08 strcon.p1.s1
473 crwxr-xr-- 1 root wheel 91, 0x20000001 Mar 30 16:08 stripe.p0.s0
474 crwxr-xr-- 1 root wheel 91, 0x20100001 Mar 30 16:08 stripe.p0.s1
475 crwxr-xr-- 1 root wheel 91, 0x20000000 Mar 30 16:08 tinyvol.p0.s0
476 crwxr-xr-- 1 root wheel 91, 0x20100000 Mar 30 16:08 tinyvol.p0.s1
477 crwxr-xr-- 1 root wheel 91, 0x20000004 Mar 30 16:08 vol5.p0.s0
478 crwxr-xr-- 1 root wheel 91, 0x20100004 Mar 30 16:08 vol5.p0.s1
479 crwxr-xr-- 1 root wheel 91, 0x20010004 Mar 30 16:08 vol5.p1.s0
480 crwxr-xr-- 1 root wheel 91, 0x20110004 Mar 30 16:08 vol5.p1.s1
484 crwxr-xr-- 1 root wheel 91, 2 Mar 30 16:08 concat
485 drwxr-xr-x 4 root wheel 512 Mar 30 16:08 concat.plex
486 crwxr-xr-- 1 root wheel 91, 3 Mar 30 16:08 strcon
487 drwxr-xr-x 4 root wheel 512 Mar 30 16:08 strcon.plex
488 crwxr-xr-- 1 root wheel 91, 1 Mar 30 16:08 stripe
489 drwxr-xr-x 3 root wheel 512 Mar 30 16:08 stripe.plex
490 crwxr-xr-- 1 root wheel 91, 0 Mar 30 16:08 tinyvol
491 drwxr-xr-x 3 root wheel 512 Mar 30 16:08 tinyvol.plex
492 crwxr-xr-- 1 root wheel 91, 4 Mar 30 16:08 vol5
493 drwxr-xr-x 4 root wheel 512 Mar 30 16:08 vol5.plex
495 /dev/vinum/vol/concat.plex:
497 crwxr-xr-- 1 root wheel 91, 0x10000002 Mar 30 16:08 concat.p0
498 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 concat.p0.sd
499 crwxr-xr-- 1 root wheel 91, 0x10010002 Mar 30 16:08 concat.p1
500 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 concat.p1.sd
502 /dev/vinum/vol/concat.plex/concat.p0.sd:
504 crwxr-xr-- 1 root wheel 91, 0x20000002 Mar 30 16:08 concat.p0.s0
505 crwxr-xr-- 1 root wheel 91, 0x20100002 Mar 30 16:08 concat.p0.s1
507 /dev/vinum/vol/concat.plex/concat.p1.sd:
509 crwxr-xr-- 1 root wheel 91, 0x20010002 Mar 30 16:08 concat.p1.s0
511 /dev/vinum/vol/strcon.plex:
513 crwxr-xr-- 1 root wheel 91, 0x10000003 Mar 30 16:08 strcon.p0
514 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 strcon.p0.sd
515 crwxr-xr-- 1 root wheel 91, 0x10010003 Mar 30 16:08 strcon.p1
516 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 strcon.p1.sd
518 /dev/vinum/vol/strcon.plex/strcon.p0.sd:
520 crwxr-xr-- 1 root wheel 91, 0x20000003 Mar 30 16:08 strcon.p0.s0
521 crwxr-xr-- 1 root wheel 91, 0x20100003 Mar 30 16:08 strcon.p0.s1
523 /dev/vinum/vol/strcon.plex/strcon.p1.sd:
525 crwxr-xr-- 1 root wheel 91, 0x20010003 Mar 30 16:08 strcon.p1.s0
526 crwxr-xr-- 1 root wheel 91, 0x20110003 Mar 30 16:08 strcon.p1.s1
528 /dev/vinum/vol/stripe.plex:
530 crwxr-xr-- 1 root wheel 91, 0x10000001 Mar 30 16:08 stripe.p0
531 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 stripe.p0.sd
533 /dev/vinum/vol/stripe.plex/stripe.p0.sd:
535 crwxr-xr-- 1 root wheel 91, 0x20000001 Mar 30 16:08 stripe.p0.s0
536 crwxr-xr-- 1 root wheel 91, 0x20100001 Mar 30 16:08 stripe.p0.s1
538 /dev/vinum/vol/tinyvol.plex:
540 crwxr-xr-- 1 root wheel 91, 0x10000000 Mar 30 16:08 tinyvol.p0
541 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 tinyvol.p0.sd
543 /dev/vinum/vol/tinyvol.plex/tinyvol.p0.sd:
545 crwxr-xr-- 1 root wheel 91, 0x20000000 Mar 30 16:08 tinyvol.p0.s0
546 crwxr-xr-- 1 root wheel 91, 0x20100000 Mar 30 16:08 tinyvol.p0.s1
548 /dev/vinum/vol/vol5.plex:
550 crwxr-xr-- 1 root wheel 91, 0x10000004 Mar 30 16:08 vol5.p0
551 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 vol5.p0.sd
552 crwxr-xr-- 1 root wheel 91, 0x10010004 Mar 30 16:08 vol5.p1
553 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 vol5.p1.sd
555 /dev/vinum/vol/vol5.plex/vol5.p0.sd:
557 crwxr-xr-- 1 root wheel 91, 0x20000004 Mar 30 16:08 vol5.p0.s0
558 crwxr-xr-- 1 root wheel 91, 0x20100004 Mar 30 16:08 vol5.p0.s1
560 /dev/vinum/vol/vol5.plex/vol5.p1.sd:
562 crwxr-xr-- 1 root wheel 91, 0x20010004 Mar 30 16:08 vol5.p1.s0
563 crwxr-xr-- 1 root wheel 91, 0x20110004 Mar 30 16:08 vol5.p1.s1
566 In the case of unattached plexes and subdisks, the naming is reversed. Subdisks
567 are named after the disk on which they are located, and plexes are named after
570 .Nm This mapping is still to be determined.
575 object has a \fIstate\fR associated with it.
577 uses this state to determine the handling of the object.
580 Volumes may have the following states:
584 The volume is completely inaccessible.
586 The volume is up and at least partially functional. Not all plexes may be
590 Plexes may have the following states:
595 A plex entry which has been referenced as part of a volume, but which is
598 A plex which has gone completely down because of I/O errors.
600 A plex which has been taken down by the administrator.
602 A plex which is being initialized.
604 The remaining states represent plexes which are at least partially up.
606 A plex entry which is at least partially up. Not all subdisks are available,
607 and an inconsistency has occurred. If no other plex is uncorrupted, the volume
608 is no longer consistent.
610 A RAID-5 plex entry which is accessible, but one subdisk is down, requiring
611 recovery for many I/O requests.
613 A plex which is really up, but which has a reborn subdisk which we don't
614 completely trust, and which we don't want to read if we can avoid it.
616 A plex entry which is completely up. All subdisks are up.
620 Subdisks can have the following states:
625 A subdisk entry which has been created completely. All fields are correct, and
626 the disk has been updated, but the on the disk is not valid.
628 A subdisk entry which has been referenced as part of a plex, but which is
631 A subdisk entry which has been created completely and which is currently being
634 The following states represent invalid data.
636 A subdisk entry which has been created completely. All fields are correct, the
637 config on disk has been updated, and the data was valid, but since then the
638 drive has been taken down, and as a result updates have been missed.
640 A subdisk entry which has been created completely. All fields are correct, the
641 disk has been updated, and the data was valid, but since then the drive has been
642 crashed and updates have been lost.
644 The following states represent valid, inaccessible data.
646 A subdisk entry which has been created completely. All fields are correct, the
647 disk has been updated, and the data was valid, but since then the drive has gone
648 down. No attempt has been made to write to the subdisk since the crash, so the
651 A subdisk entry which was up, which contained valid data, and which was taken
652 down by the administrator. The data is valid.
654 The subdisk is currently in the process of being revived. We can write but not
657 The following states represent accessible subdisks with valid data.
659 A subdisk entry which has been created completely. All fields are correct, the
660 disk has been updated, and the data was valid, but since then the drive has gone
661 down and up again. No updates were lost, but it is possible that the subdisk
662 has been damaged. We won't read from this subdisk if we have a choice. If this
663 is the only subdisk which covers this address space in the plex, we set its
664 state to up under these circumstances, so this status implies that there is
665 another subdisk to fulfil the request.
667 A subdisk entry which has been created completely. All fields are correct, the
668 disk has been updated, and the data is valid.
672 Drives can have the following states:
677 At least one subdisk refers to the drive, but it is not currently accessible to
678 the system. No device name is known.
680 The drive is not accessible.
682 The drive is up and running.
689 is a new product. Bugs can be expected. The configuration mechanism is not yet
690 fully functional. If you have difficulties, please look at the section
691 DEBUGGING PROBLEMS WITH VINUM before reporting problems.
695 pseudo-device appear to work, but are not supported. If you have trouble with
696 this configuration, please first replace the kernel with a non-Vinum
697 kernel and test with the kld module.
699 Detection of differences between the version of the kernel and the kld is not
702 The RAID-5 functionality is new in
704 Some problems have been
707 in combination with soft updates, but these are not reproducible on all
708 systems. If you are planning to use
710 in a production environment, please test carefully.
712 .Sh DEBUGGING PROBLEMS WITH VINUM
713 Solving problems with
715 can be a difficult affair. This section suggests some approaches.
716 .Ss Configuration problems
718 It is relatively easy (too easy) to run into problems with the
720 configuration. If you do, the first thing you should do is stop configuration
725 # \fBvinum setdaemon 4\fP
730 This will stop updates and any further corruption of the on-disk configuration.
732 Next, look at the on-disk configuration with the
734 command, for example:
738 # \fBvinum dumpconfig\fP
739 Drive 4: Device /dev/da3h
740 Created on crash.lemis.com at Sat May 20 16:32:44 2000
741 Config last updated Sat May 20 16:32:56 2000
742 Size: 601052160 bytes (573 MB)
745 volume raid state down
748 plex name obj.p0 state corrupt org concat vol obj
749 plex name obj.p1 state corrupt org striped 128b vol obj
750 plex name src.p0 state corrupt org striped 128b vol src
751 plex name src.p1 state up org concat vol src
752 plex name raid.p0 state faulty org disorg vol raid
753 plex name r.p0 state faulty org disorg vol r
754 plex name foo.p0 state up org concat vol foo
755 plex name foo.p1 state faulty org concat vol foo
756 sd name obj.p0.s0 drive drive2 plex obj.p0 state reborn len 409600b driveoffset 265b plexoffset 0b
757 sd name obj.p0.s1 drive drive4 plex obj.p0 state up len 409600b driveoffset 265b plexoffset 409600b
758 sd name obj.p1.s0 drive drive1 plex obj.p1 state up len 204800b driveoffset 265b plexoffset 0b
759 sd name obj.p1.s1 drive drive2 plex obj.p1 state reborn len 204800b driveoffset 409865b plexoffset 128b
760 sd name obj.p1.s2 drive drive3 plex obj.p1 state up len 204800b driveoffset 265b plexoffset 256b
761 sd name obj.p1.s3 drive drive4 plex obj.p1 state up len 204800b driveoffset 409865b plexoffset 384b
766 The configuration on all disks should be the same. If this is not the case,
767 please save the output to a file and report the problem. There is probably
768 little that can be done to recover the on-disk configuration, but if you keep a
769 copy of the files used to create the objects, you should be able to re-create
772 command does not change the subdisk data, so this will not cause data
773 corruption. You may need to use the
775 command if you have this kind of trouble.
778 In order to analyse a panic which you suspect comes from
780 you will need to build a debug kernel. See the online handbook at
781 .Pa /usr/share/doc/en/books/developers-handbook/kerneldebug.html
783 .Pa http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
784 for more details of how to do this.
786 Perform the following steps to analyse a
792 .Pa /usr/src/sys/modules/vinum/.gdbinit.crash ,
793 .Pa /usr/src/sys/modules/vinum/.gdbinit.kernel ,
794 .Pa /usr/src/sys/modules/vinum/.gdbinit.serial ,
795 .Pa /usr/src/sys/modules/vinum/.gdbinit.vinum
797 .Pa /usr/src/sys/modules/vinum/.gdbinit.vinum.paths
798 to the directory in which you will be performing the analysis, typically
801 Make sure that you build the
803 module with debugging information. The standard
805 builds a module with debugging symbols by default. If the version of
809 does not contain symbols, you will not get an error message, but the stack trace
810 will not show the symbols. Check the module before starting
813 $ file /modules/vinum.ko
814 /modules/vinum.ko: ELF 32-bit LSB shared object, Intel 80386,
815 version 1 (FreeBSD), not stripped
818 If the output shows that
819 .Pa /modules/vinum.ko
820 is stripped, you will have to find a version which is not. Usually this will be
822 .Pa /usr/obj/sys/modules/vinum/vinum.ko
828 .Pa /usr/src/sys/modules/vinum/vinum.ko
831 in this directory). Modify the file
832 .Pa .gdbinit.vinum.paths
835 Either take a dump or use remote serial
837 to analyse the problem. To analyse a dump, say
838 .Pa /var/crash/vmcore.5 ,
840 .Pa /var/crash/.gdbinit.crash
842 .Pa /var/crash/.gdbinit
846 # gdb -k kernel.debug vmcore.5
849 This example assumes that you have installed the correct debug kernel at
850 .Pa /var/crash/kernel.debug .
851 If not, substitute the correct name of the debug kernel.
853 To perform remote serial debugging,
855 .Pa /var/crash/.gdbinit.serial
857 .Pa /var/crash/.gdbinit
861 # gdb -k kernel.debug
866 file performs the functions necessary to establish connection. The remote
867 machine must already be in debug mode: enter the kernel debugger and select
871 file expects the serial connection to run at 38400 bits per second; if you run
872 at a different speed, edit the file accordingly (look for the
876 The following example shows a remote debugging session using the
883 GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc.
884 Debugger (msg=0xf1093174 "vinum debug") at ../../i386/i386/db_interface.c:318
886 #1 0xf108d9bc in vinumioctl (dev=0x40001900, cmd=0xc008464b, data=0xf6dedee0 "",
887 flag=0x3, p=0xf68b7940) at
888 /usr/src/sys/modules/Vinum/../../dev/Vinum/vinumioctl.c:102
889 102 Debugger ("vinum debug");
891 #0 Debugger (msg=0xf0f661ac "vinum debug") at ../../i386/i386/db_interface.c:318
892 #1 0xf0f60a7c in vinumioctl (dev=0x40001900, cmd=0xc008464b, data=0xf6923ed0 "",
893 flag=0x3, p=0xf688e6c0) at
894 /usr/src/sys/modules/vinum/../../dev/vinum/vinumioctl.c:109
895 #2 0xf01833b7 in spec_ioctl (ap=0xf6923e0c) at ../../miscfs/specfs/spec_vnops.c:424
896 #3 0xf0182cc9 in spec_vnoperate (ap=0xf6923e0c) at ../../miscfs/specfs/spec_vnops.c:129
897 #4 0xf01eb3c1 in ufs_vnoperatespec (ap=0xf6923e0c) at ../../ufs/ufs/ufs_vnops.c:2312
898 #5 0xf017dbb1 in vn_ioctl (fp=0xf1007ec0, com=0xc008464b, data=0xf6923ed0 "",
899 p=0xf688e6c0) at vnode_if.h:395
900 #6 0xf015dce0 in ioctl (p=0xf688e6c0, uap=0xf6923f84) at ../../kern/sys_generic.c:473
901 #7 0xf0214c0b in syscall (frame={tf_es = 0x27, tf_ds = 0x27, tf_edi = 0xefbfcff8,
902 tf_esi = 0x1, tf_ebp = 0xefbfcf90, tf_isp = 0xf6923fd4, tf_ebx = 0x2,
903 tf_edx = 0x804b614, tf_ecx = 0x8085d10, tf_eax = 0x36, tf_trapno = 0x7,
904 tf_err = 0x2, tf_eip = 0x8060a34, tf_cs = 0x1f, tf_eflags = 0x286,
905 tf_esp = 0xefbfcf78, tf_ss = 0x27}) at ../../i386/i386/trap.c:1100
906 #8 0xf020a1fc in Xint0x80_syscall ()
907 #9 0x804832d in ?? ()
908 #10 0x80482ad in ?? ()
909 #11 0x80480e9 in ?? ()
914 When entering from the debugger, it's important that the source of frame 1
917 file at the top of the example) contains the text
921 Debugger ("vinum debug");
926 This is an indication that the address specifications are correct. If you get
927 some other output, your symbols and the kernel module are out of sync, and the
928 trace will be meaningless.
931 For an initial investigation, the most important information is the output of
934 (backtrace) command above.
935 .Ss Reporting problems with Vinum
937 If you find any bugs in
939 please report them to Greg Lehey <grog@lemis.com>. Supply the following
949 Any messages printed in
950 .Pa /var/log/messages .
951 All such messages will be identified by the text
955 If you have a panic, a stack trace as described above.
958 .An Greg Lehey Aq grog@lemis.com .
963 The RAID-5 component of
965 was developed by Cybernet Inc.
967 for its NetMAX product.