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 $
38 .\" $DragonFly: src/share/man/man4/vinum.4,v 1.15 2008/09/02 11:50:46 matthias Exp $
45 .Nd Logical Volume Manager
47 .Cd "pseudo-device vinum"
50 is a logical volume manager inspired by, but not derived from, the Veritas
52 It provides the following features:
55 It provides device-independent logical disks, called
58 not restricted to the size of any disk on the system.
60 The volumes consist of one or more
62 each of which contain the
63 entire address space of a volume.
64 This represents an implementation of RAID-1
66 Multiple plexes can also be used for
67 .\" XXX What about sparse plexes? Do we want them?
70 Increased read throughput.
72 will read data from the least active disk, so if a volume has plexes on multiple
73 disks, more data can be read in parallel.
75 reads data from only one plex, but it writes data to all plexes.
77 Increased reliability.
78 By storing plexes on different disks, data will remain
79 available even if one of the plexes becomes unavailable.
81 RAID-5 plex (see below), using multiple plexes requires more storage space, but
82 gives better performance, particularly in the case of a drive failure.
84 Additional plexes can be used for on-line data reorganization.
86 additional plex and subsequently detaching one of the older plexes, data can be
87 moved on-line without compromising access.
89 An additional plex can be used to obtain a consistent dump of a file system.
91 attaching an additional plex and detaching at a specific time, the detached plex
92 becomes an accurate snapshot of the file system at the time of detachment.
93 .\" Make sure to flush!
96 Each plex consists of one or more logical disk slices, called
98 Subdisks are defined as a contiguous block of physical disk storage.
100 consist of any reasonable number of subdisks (in other words, the real limit is
101 not the number, but other factors, such as memory and performance, associated
102 with maintaining a large number of subdisks).
104 A number of mappings between subdisks and plexes are available:
107 .Em "Concatenated plexes"
108 consist of one or more subdisks, each of which
109 is mapped to a contiguous part of the plex address space.
112 consist of two or more subdisks of equal size.
114 address space is mapped in
116 integral fractions of the subdisk
118 Consecutive plex address space is mapped to stripes in each subdisk in
132 "plex 0" at SD0.n+(0,.2)
133 "subdisk 0" rjust at SD0.w-(.2,0)
134 "subdisk 1" rjust at SD1.w-(.2,0)
135 "subdisk 2" rjust at SD2.w-(.2,0)
139 The subdisks of a striped plex must all be the same size.
142 require at least three equal-sized subdisks.
144 resemble striped plexes, except that in each stripe, one subdisk stores parity
146 This subdisk changes in each stripe: in the first stripe, it is the
147 first subdisk, in the second it is the second subdisk, etc.
151 will recover the data based on the information stored on the remaining subdisks.
152 This mapping is particularly suited to read-intensive access.
154 RAID-5 plex must all be the same size.
155 .\" Make sure to flush!
159 are the lowest level of the storage hierarchy.
160 They represent disk special
164 offers automatic startup.
169 volumes contain all the configuration information needed to ensure that they are
170 started correctly when the subsystem is enabled.
171 This is also a significant
172 advantage over the Veritas\(tm File System.
173 This feature regards the presence
175 It does not mean that the volumes will be mounted
176 automatically, since the standard startup procedures with
178 perform this function.
180 .Sh KERNEL CONFIGURATION
182 is currently supplied as a KLD module, and does not require
184 As with other klds, it is absolutely necessary to match the kld
185 to the version of the operating system.
186 Failure to do so will cause
188 to issue an error message and terminate.
190 It is possible to configure
192 in the kernel, but this is not recommended.
193 To do so, add this line to the
194 kernel configuration file:
196 .D1 Cd "pseudo-device vinum"
198 The current version of
200 both the kernel module and the user program
202 include significant debugging support.
203 It is not recommended to remove
204 this support at the moment, but if you do you must remove it from both the
205 kernel and the user components.
206 To do this, edit the files
207 .Pa /usr/src/sbin/vinum/Makefile
209 .Pa /sys/dev/raid/vinum/Makefile
212 variable to remove the
218 into the kernel, either specify the line
220 .D1 Cd "options VINUMDEBUG"
222 in the kernel configuration file or remove the
225 .Pa /usr/src/sbin/vinum/Makefile
230 variables do not match,
232 will fail with a message
233 explaining the problem and what to do to correct it.
236 was previously available in two versions: a freely available version which did
237 not contain RAID-5 functionality, and a full version including RAID-5
238 functionality, which was available only from Cybernet Systems Inc.
242 includes the RAID-5 functionality.
248 It does not require installation.
249 To start it, start the
251 program, which will load the kld if it is not already present.
254 it must be configured.
257 for information on how to create a
261 Normally, you start a configured version of
279 is loaded as a kld (the recommended way), the
281 command will unload it
284 You can also do this with the
288 The kld can only be unloaded when idle, in other words when no volumes are
289 mounted and no other instances of the
292 Unloading the kld does not harm the data in the volumes.
293 .Ss Configuring and Starting Objects
296 utility to configure and start
301 calls are intended for the use of the
303 configuration program only.
304 They are described in the header file
305 .Pa /sys/dev/raid/vinum/vinumio.h .
307 Conventional disk special devices have a
309 in the second sector of the device.
313 This disk label describes the layout of the partitions within
316 does not subdivide volumes, so volumes do not contain a physical disk label.
319 implements the ioctl calls
323 (get partition information),
325 (write partition information) and
327 (set partition information).
332 representation of the disk label which is not present on the volume.
344 serves no useful purpose on a
352 .Dv DIOCSDINFO ioctls, since there is nothing to change.
353 As a result, any attempt to modify the disk label will be silently ignored.
354 .Sh MAKING FILE SYSTEMS
357 volumes do not contain partitions, the names do not need to conform to the
358 standard rules for naming disk partitions.
359 For a physical disk partition, the
360 last letter of the device name specifies the partition identifier (a to p).
362 volumes need not conform to this convention, but if they do not,
364 will complain that it cannot determine the partition.
365 To solve this problem,
370 For example, if you have a volume
372 use the following command to create a
376 .Dl "newfs -v /dev/vinum/concat"
379 assigns default names to plexes and subdisks, although they may be overridden.
380 We do not recommend overriding the default names.
383 volume manager, which allows arbitrary naming of objects, has shown that this
384 flexibility does not bring a significant advantage, and it can cause confusion.
386 Names may contain any non-blank character, but it is recommended to restrict
387 them to letters, digits and the underscore characters.
388 The names of volumes,
389 plexes and subdisks may be up to 64 characters long, and the names of drives may
390 up to 32 characters long.
391 When choosing volume and plex names, bear in mind
392 that automatically generated plex and subdisk names are longer than the name
393 from which they are derived.
398 creates or deletes objects, it creates a directory
400 in which it makes device entries for each volume.
406 in which it stores device entries for the plexes and subdisks. In addition, it
407 creates two more directories,
410 .Pa /dev/vinum/drive ,
411 in which it stores hierarchical information for volumes and drives.
415 creates three super-devices,
416 .Pa /dev/vinum/control ,
417 .Pa /dev/vinum/Control
419 .Pa /dev/vinum/controld .
420 .Pa /dev/vinum/control
423 when it has been compiled without the
426 .Pa /dev/vinum/Control
429 when it has been compiled with the
432 .Pa /dev/vinum/controld
436 The two control devices for
438 are used to synchronize the debug status of kernel and user modules.
444 volumes are not subdivided into partitions, and thus do not contain a disk
446 Unfortunately, this confuses a number of utilities, notably
448 which normally tries to interpret the last letter of a
450 volume name as a partition identifier.
451 If you use a volume name which does not
460 in order to tell it to ignore this convention.
463 Plexes do not need to be assigned explicit names.
464 By default, a plex name is
465 the name of the volume followed by the letters
467 and the number of the
469 For example, the plexes of volume
472 .Pa vol3.p0 , vol3.p1
474 These names can be overridden, but it is not recommended.
476 Like plexes, subdisks are assigned names automatically, and explicit naming is
478 A subdisk name is the name of the plex followed by the letters
480 and a number identifying the subdisk.
481 For example, the subdisks of
485 .Pa vol3.p0.s0 , vol3.p0.s1
491 This makes it possible to move a drive to a different location
492 and still recognize it automatically.
493 Drive names may be up to 32 characters
499 objects described in the section
500 .Sx "CONFIGURATION FILE"
506 .Bd -literal -offset indent
509 crwxr-xr-- 1 root wheel 91, 2 Mar 30 16:08 concat
510 crwx------ 1 root wheel 91, 0x40000000 Mar 30 16:08 control
511 crwx------ 1 root wheel 91, 0x40000001 Mar 30 16:08 controld
512 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 drive
513 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 plex
514 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 rvol
515 drwxrwxrwx 2 root wheel 512 Mar 30 16:08 sd
516 crwxr-xr-- 1 root wheel 91, 3 Mar 30 16:08 strcon
517 crwxr-xr-- 1 root wheel 91, 1 Mar 30 16:08 stripe
518 crwxr-xr-- 1 root wheel 91, 0 Mar 30 16:08 tinyvol
519 drwxrwxrwx 7 root wheel 512 Mar 30 16:08 vol
520 crwxr-xr-- 1 root wheel 91, 4 Mar 30 16:08 vol5
524 crw-r----- 1 root operator 4, 15 Oct 21 16:51 drive2
525 crw-r----- 1 root operator 4, 31 Oct 21 16:51 drive4
529 crwxr-xr-- 1 root wheel 91, 0x10000002 Mar 30 16:08 concat.p0
530 crwxr-xr-- 1 root wheel 91, 0x10010002 Mar 30 16:08 concat.p1
531 crwxr-xr-- 1 root wheel 91, 0x10000003 Mar 30 16:08 strcon.p0
532 crwxr-xr-- 1 root wheel 91, 0x10010003 Mar 30 16:08 strcon.p1
533 crwxr-xr-- 1 root wheel 91, 0x10000001 Mar 30 16:08 stripe.p0
534 crwxr-xr-- 1 root wheel 91, 0x10000000 Mar 30 16:08 tinyvol.p0
535 crwxr-xr-- 1 root wheel 91, 0x10000004 Mar 30 16:08 vol5.p0
536 crwxr-xr-- 1 root wheel 91, 0x10010004 Mar 30 16:08 vol5.p1
540 crwxr-xr-- 1 root wheel 91, 0x20000002 Mar 30 16:08 concat.p0.s0
541 crwxr-xr-- 1 root wheel 91, 0x20100002 Mar 30 16:08 concat.p0.s1
542 crwxr-xr-- 1 root wheel 91, 0x20010002 Mar 30 16:08 concat.p1.s0
543 crwxr-xr-- 1 root wheel 91, 0x20000003 Mar 30 16:08 strcon.p0.s0
544 crwxr-xr-- 1 root wheel 91, 0x20100003 Mar 30 16:08 strcon.p0.s1
545 crwxr-xr-- 1 root wheel 91, 0x20010003 Mar 30 16:08 strcon.p1.s0
546 crwxr-xr-- 1 root wheel 91, 0x20110003 Mar 30 16:08 strcon.p1.s1
547 crwxr-xr-- 1 root wheel 91, 0x20000001 Mar 30 16:08 stripe.p0.s0
548 crwxr-xr-- 1 root wheel 91, 0x20100001 Mar 30 16:08 stripe.p0.s1
549 crwxr-xr-- 1 root wheel 91, 0x20000000 Mar 30 16:08 tinyvol.p0.s0
550 crwxr-xr-- 1 root wheel 91, 0x20100000 Mar 30 16:08 tinyvol.p0.s1
551 crwxr-xr-- 1 root wheel 91, 0x20000004 Mar 30 16:08 vol5.p0.s0
552 crwxr-xr-- 1 root wheel 91, 0x20100004 Mar 30 16:08 vol5.p0.s1
553 crwxr-xr-- 1 root wheel 91, 0x20010004 Mar 30 16:08 vol5.p1.s0
554 crwxr-xr-- 1 root wheel 91, 0x20110004 Mar 30 16:08 vol5.p1.s1
558 crwxr-xr-- 1 root wheel 91, 2 Mar 30 16:08 concat
559 drwxr-xr-x 4 root wheel 512 Mar 30 16:08 concat.plex
560 crwxr-xr-- 1 root wheel 91, 3 Mar 30 16:08 strcon
561 drwxr-xr-x 4 root wheel 512 Mar 30 16:08 strcon.plex
562 crwxr-xr-- 1 root wheel 91, 1 Mar 30 16:08 stripe
563 drwxr-xr-x 3 root wheel 512 Mar 30 16:08 stripe.plex
564 crwxr-xr-- 1 root wheel 91, 0 Mar 30 16:08 tinyvol
565 drwxr-xr-x 3 root wheel 512 Mar 30 16:08 tinyvol.plex
566 crwxr-xr-- 1 root wheel 91, 4 Mar 30 16:08 vol5
567 drwxr-xr-x 4 root wheel 512 Mar 30 16:08 vol5.plex
569 /dev/vinum/vol/concat.plex:
571 crwxr-xr-- 1 root wheel 91, 0x10000002 Mar 30 16:08 concat.p0
572 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 concat.p0.sd
573 crwxr-xr-- 1 root wheel 91, 0x10010002 Mar 30 16:08 concat.p1
574 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 concat.p1.sd
576 /dev/vinum/vol/concat.plex/concat.p0.sd:
578 crwxr-xr-- 1 root wheel 91, 0x20000002 Mar 30 16:08 concat.p0.s0
579 crwxr-xr-- 1 root wheel 91, 0x20100002 Mar 30 16:08 concat.p0.s1
581 /dev/vinum/vol/concat.plex/concat.p1.sd:
583 crwxr-xr-- 1 root wheel 91, 0x20010002 Mar 30 16:08 concat.p1.s0
585 /dev/vinum/vol/strcon.plex:
587 crwxr-xr-- 1 root wheel 91, 0x10000003 Mar 30 16:08 strcon.p0
588 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 strcon.p0.sd
589 crwxr-xr-- 1 root wheel 91, 0x10010003 Mar 30 16:08 strcon.p1
590 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 strcon.p1.sd
592 /dev/vinum/vol/strcon.plex/strcon.p0.sd:
594 crwxr-xr-- 1 root wheel 91, 0x20000003 Mar 30 16:08 strcon.p0.s0
595 crwxr-xr-- 1 root wheel 91, 0x20100003 Mar 30 16:08 strcon.p0.s1
597 /dev/vinum/vol/strcon.plex/strcon.p1.sd:
599 crwxr-xr-- 1 root wheel 91, 0x20010003 Mar 30 16:08 strcon.p1.s0
600 crwxr-xr-- 1 root wheel 91, 0x20110003 Mar 30 16:08 strcon.p1.s1
602 /dev/vinum/vol/stripe.plex:
604 crwxr-xr-- 1 root wheel 91, 0x10000001 Mar 30 16:08 stripe.p0
605 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 stripe.p0.sd
607 /dev/vinum/vol/stripe.plex/stripe.p0.sd:
609 crwxr-xr-- 1 root wheel 91, 0x20000001 Mar 30 16:08 stripe.p0.s0
610 crwxr-xr-- 1 root wheel 91, 0x20100001 Mar 30 16:08 stripe.p0.s1
612 /dev/vinum/vol/tinyvol.plex:
614 crwxr-xr-- 1 root wheel 91, 0x10000000 Mar 30 16:08 tinyvol.p0
615 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 tinyvol.p0.sd
617 /dev/vinum/vol/tinyvol.plex/tinyvol.p0.sd:
619 crwxr-xr-- 1 root wheel 91, 0x20000000 Mar 30 16:08 tinyvol.p0.s0
620 crwxr-xr-- 1 root wheel 91, 0x20100000 Mar 30 16:08 tinyvol.p0.s1
622 /dev/vinum/vol/vol5.plex:
624 crwxr-xr-- 1 root wheel 91, 0x10000004 Mar 30 16:08 vol5.p0
625 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 vol5.p0.sd
626 crwxr-xr-- 1 root wheel 91, 0x10010004 Mar 30 16:08 vol5.p1
627 drwxr-xr-x 2 root wheel 512 Mar 30 16:08 vol5.p1.sd
629 /dev/vinum/vol/vol5.plex/vol5.p0.sd:
631 crwxr-xr-- 1 root wheel 91, 0x20000004 Mar 30 16:08 vol5.p0.s0
632 crwxr-xr-- 1 root wheel 91, 0x20100004 Mar 30 16:08 vol5.p0.s1
634 /dev/vinum/vol/vol5.plex/vol5.p1.sd:
636 crwxr-xr-- 1 root wheel 91, 0x20010004 Mar 30 16:08 vol5.p1.s0
637 crwxr-xr-- 1 root wheel 91, 0x20110004 Mar 30 16:08 vol5.p1.s1
640 In the case of unattached plexes and subdisks, the naming is reversed.
642 are named after the disk on which they are located, and plexes are named after
646 This mapping is still to be determined.
655 uses this state to determine the handling of the object.
657 Volumes may have the following states:
660 The volume is completely inaccessible.
662 The volume is up and at least partially functional.
663 Not all plexes may be
667 Plexes may have the following states:
670 A plex entry which has been referenced as part of a volume, but which is
673 A plex which has gone completely down because of I/O errors.
675 A plex which has been taken down by the administrator.
677 A plex which is being initialized.
680 The remaining states represent plexes which are at least partially up.
683 A plex entry which is at least partially up.
684 Not all subdisks are available,
685 and an inconsistency has occurred.
686 If no other plex is uncorrupted, the volume
687 is no longer consistent.
689 A RAID-5 plex entry which is accessible, but one subdisk is down, requiring
690 recovery for many I/O requests.
692 A plex which is really up, but which has a reborn subdisk which we do not
693 completely trust, and which we do not want to read if we can avoid it.
695 A plex entry which is completely up.
699 Subdisks can have the following states:
702 A subdisk entry which has been created completely.
703 All fields are correct, and
704 the disk has been updated, but the on the disk is not valid.
706 A subdisk entry which has been referenced as part of a plex, but which is
709 A subdisk entry which has been created completely and which is currently being
713 The following states represent invalid data.
716 A subdisk entry which has been created completely.
717 All fields are correct, the
718 config on disk has been updated, and the data was valid, but since then the
719 drive has been taken down, and as a result updates have been missed.
721 A subdisk entry which has been created completely.
722 All fields are correct, the
723 disk has been updated, and the data was valid, but since then the drive has been
724 crashed and updates have been lost.
727 The following states represent valid, inaccessible data.
730 A subdisk entry which has been created completely.
731 All fields are correct, the
732 disk has been updated, and the data was valid, but since then the drive has gone
734 No attempt has been made to write to the subdisk since the crash, so the
737 A subdisk entry which was up, which contained valid data, and which was taken
738 down by the administrator.
741 The subdisk is currently in the process of being revived.
746 The following states represent accessible subdisks with valid data.
749 A subdisk entry which has been created completely.
750 All fields are correct, the
751 disk has been updated, and the data was valid, but since then the drive has gone
753 No updates were lost, but it is possible that the subdisk
755 We won't read from this subdisk if we have a choice.
757 is the only subdisk which covers this address space in the plex, we set its
758 state to up under these circumstances, so this status implies that there is
759 another subdisk to fulfil the request.
761 A subdisk entry which has been created completely.
762 All fields are correct, the
763 disk has been updated, and the data is valid.
766 Drives can have the following states:
769 At least one subdisk refers to the drive, but it is not currently accessible to
771 No device name is known.
773 The drive is not accessible.
775 The drive is up and running.
777 .Sh DEBUGGING PROBLEMS WITH VINUM
778 Solving problems with
780 can be a difficult affair.
781 This section suggests some approaches.
782 .Ss Configuration problems
783 It is relatively easy (too easy) to run into problems with the
786 If you do, the first thing you should do is stop configuration
789 .Dl "vinum setdaemon 4"
791 This will stop updates and any further corruption of the on-disk configuration.
793 Next, look at the on-disk configuration with the
795 command, for example:
799 # \fBvinum dumpconfig\fP
800 Drive 4: Device /dev/da3s0h
801 Created on crash.lemis.com at Sat May 20 16:32:44 2000
802 Config last updated Sat May 20 16:32:56 2000
803 Size: 601052160 bytes (573 MB)
806 volume raid state down
809 plex name obj.p0 state corrupt org concat vol obj
810 plex name obj.p1 state corrupt org striped 128b vol obj
811 plex name src.p0 state corrupt org striped 128b vol src
812 plex name src.p1 state up org concat vol src
813 plex name raid.p0 state faulty org disorg vol raid
814 plex name r.p0 state faulty org disorg vol r
815 plex name foo.p0 state up org concat vol foo
816 plex name foo.p1 state faulty org concat vol foo
817 sd name obj.p0.s0 drive drive2 plex obj.p0 state reborn len 409600b driveoffset 265b plexoffset 0b
818 sd name obj.p0.s1 drive drive4 plex obj.p0 state up len 409600b driveoffset 265b plexoffset 409600b
819 sd name obj.p1.s0 drive drive1 plex obj.p1 state up len 204800b driveoffset 265b plexoffset 0b
820 sd name obj.p1.s1 drive drive2 plex obj.p1 state reborn len 204800b driveoffset 409865b plexoffset 128b
821 sd name obj.p1.s2 drive drive3 plex obj.p1 state up len 204800b driveoffset 265b plexoffset 256b
822 sd name obj.p1.s3 drive drive4 plex obj.p1 state up len 204800b driveoffset 409865b plexoffset 384b
827 The configuration on all disks should be the same.
828 If this is not the case,
829 please save the output to a file and report the problem.
831 little that can be done to recover the on-disk configuration, but if you keep a
832 copy of the files used to create the objects, you should be able to re-create
836 command does not change the subdisk data, so this will not cause data
838 You may need to use the
840 command if you have this kind of trouble.
842 In order to analyse a panic which you suspect comes from
844 you will need to build a debug kernel.
845 See the online handbook at
846 .Pa http://www.dragonflybsd.org/docs/user/list/DebugKernelCrashDumps/
847 for more details of how to do this.
849 Perform the following steps to analyse a
854 Copy the following files to the directory in which you will be
855 performing the analysis, typically
860 .Pa /sys/dev/raid/vinum/.gdbinit.crash ,
862 .Pa /sys/dev/raid/vinum/.gdbinit.kernel ,
864 .Pa /sys/dev/raid/vinum/.gdbinit.serial ,
866 .Pa /sys/dev/raid/vinum/.gdbinit.vinum
869 .Pa /sys/dev/raid/vinum/.gdbinit.vinum.paths
872 Make sure that you build the
874 module with debugging information.
877 builds a module with debugging symbols by default.
882 does not contain symbols, you will not get an error message, but the stack trace
883 will not show the symbols.
884 Check the module before starting
887 $ file /boot/modules/vinum.ko
888 /boot/modules/vinum.ko: ELF 32-bit LSB shared object, Intel 80386,
889 version 1 (SYSV), dynamically linked, not stripped
892 If the output shows that
893 .Pa /boot/modules/vinum.ko
894 is stripped, you will have to find a version which is not.
897 .Pa /usr/obj/usr/src/sys/SYSTEM_NAME/usr/src/sys/dev/raid/vinum/vinum.ko
901 .Dq Li "make world" )
903 .Pa /sys/dev/raid/vinum/vinum.ko
908 .Pa .gdbinit.vinum.paths
911 Either take a dump or use remote serial
913 to analyse the problem.
914 To analyse a dump, say
915 .Pa /var/crash/vmcore.5 ,
917 .Pa /var/crash/.gdbinit.crash
919 .Pa /var/crash/.gdbinit
921 .Bd -literal -offset indent
923 kgdb kernel.debug vmcore.5
926 This example assumes that you have installed the correct debug kernel at
927 .Pa /var/crash/kernel.debug .
928 If not, substitute the correct name of the debug kernel.
930 To perform remote serial debugging,
932 .Pa /var/crash/.gdbinit.serial
934 .Pa /var/crash/.gdbinit
936 .Bd -literal -offset indent
943 file performs the functions necessary to establish connection.
945 machine must already be in debug mode: enter the kernel debugger and select
952 file expects the serial connection to run at 38400 bits per second; if you run
953 at a different speed, edit the file accordingly (look for the
957 The following example shows a remote debugging session using the
964 GDB 4.16 (i386-unknown-dragonfly), Copyright 1996 Free Software Foundation, Inc.
965 Debugger (msg=0xf1093174 "vinum debug") at ../../i386/i386/db_interface.c:318
967 #1 0xf108d9bc in vinumioctl (dev=0x40001900, cmd=0xc008464b, data=0xf6dedee0 "",
968 flag=0x3, p=0xf68b7940) at
969 /usr/src/sys/dev/raid/vinum/vinumioctl.c:102
970 102 Debugger ("vinum debug");
972 #0 Debugger (msg=0xf0f661ac "vinum debug") at ../../i386/i386/db_interface.c:318
973 #1 0xf0f60a7c in vinumioctl (dev=0x40001900, cmd=0xc008464b, data=0xf6923ed0 "",
974 flag=0x3, p=0xf688e6c0) at
975 /usr/src/sys/dev/raid/vinum/vinumioctl.c:109
976 #2 0xf01833b7 in spec_ioctl (ap=0xf6923e0c) at ../../miscfs/specfs/spec_vnops.c:424
977 #3 0xf0182cc9 in spec_vnoperate (ap=0xf6923e0c) at ../../miscfs/specfs/spec_vnops.c:129
978 #4 0xf01eb3c1 in ufs_vnoperatespec (ap=0xf6923e0c) at ../../ufs/ufs/ufs_vnops.c:2312
979 #5 0xf017dbb1 in vn_ioctl (fp=0xf1007ec0, com=0xc008464b, data=0xf6923ed0 "",
980 p=0xf688e6c0) at vnode_if.h:395
981 #6 0xf015dce0 in ioctl (p=0xf688e6c0, uap=0xf6923f84) at ../../kern/sys_generic.c:473
982 #7 0xf0214c0b in syscall (frame={tf_es = 0x27, tf_ds = 0x27, tf_edi = 0xefbfcff8,
983 tf_esi = 0x1, tf_ebp = 0xefbfcf90, tf_isp = 0xf6923fd4, tf_ebx = 0x2,
984 tf_edx = 0x804b614, tf_ecx = 0x8085d10, tf_eax = 0x36, tf_trapno = 0x7,
985 tf_err = 0x2, tf_eip = 0x8060a34, tf_cs = 0x1f, tf_eflags = 0x286,
986 tf_esp = 0xefbfcf78, tf_ss = 0x27}) at ../../i386/i386/trap.c:1100
987 #8 0xf020a1fc in Xint0x80_syscall ()
988 #9 0x804832d in ?? ()
989 #10 0x80482ad in ?? ()
990 #11 0x80480e9 in ?? ()
995 When entering from the debugger, it is important that the source of frame 1
998 file at the top of the example) contains the text
999 .Dq Li "Debugger (\*[q]vinum debug\*[q]);" .
1001 This is an indication that the address specifications are correct.
1003 some other output, your symbols and the kernel module are out of sync, and the
1004 trace will be meaningless.
1007 For an initial investigation, the most important information is the output of
1010 (backtrace) command above.
1011 .Ss Reporting Problems with Vinum
1012 If you find any bugs in
1014 please report them to
1015 .An Greg Lehey Aq grog@lemis.com .
1016 Supply the following
1026 Any messages printed in
1027 .Pa /var/log/messages .
1028 All such messages will be identified by the text
1032 If you have a panic, a stack trace as described above.
1043 The RAID-5 component of
1045 was developed by Cybernet Inc.\&
1046 .Pq Pa http://www.cybernet.com/ ,
1047 for its NetMAX product.
1049 .An Greg Lehey Aq grog@lemis.com .
1053 Bugs can be expected.
1054 The configuration mechanism is not yet
1056 If you have difficulties, please look at the section
1057 .Sx "DEBUGGING PROBLEMS WITH VINUM"
1058 before reporting problems.
1062 pseudo-device appear to work, but are not supported.
1063 If you have trouble with
1064 this configuration, please first replace the kernel with a
1066 kernel and test with the kld module.
1068 Detection of differences between the version of the kernel and the kld is not
1071 The RAID-5 functionality is new in
1073 Some problems have been
1076 in combination with soft updates, but these are not reproducible on all
1078 If you are planning to use
1080 in a production environment, please test carefully.