Date: Sun, 13 Feb 2000 14:21:00 +1030 From: Greg Lehey <grog@lemis.com> To: Jaye Mathisen <mrcpu@internetcds.com> Cc: questions@FreeBSD.ORG Subject: Re: Vinum question... Message-ID: <20000213142100.T89378@freebie.lemis.com> In-Reply-To: <Pine.BSF.4.10.10002120514180.17547-100000@schizo.cdsnet.net> References: <Pine.BSF.4.10.10002120514180.17547-100000@schizo.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[Format recovered--see http://www.lemis.com/email/email-format.html] On Saturday, 12 February 2000 at 5:17:38 -0800, Jaye Mathisen wrote: > > > What am I missing here? http://www.lemis.com/email.html and http://www.lemis.com/vinum/how-to-debug.html? > # Vinum configuration of proxy-03-real.cdsnet.net, saved at Sat Feb 12 > 04:08:22 2000 > drive d1 device /dev/da1d > drive d2 device /dev/da2d > drive d3 device /dev/da3d > drive d4 device /dev/da4d > drive d5 device /dev/da5d > drive d6 device /dev/da6d > volume raid > plex name plex1 org raid5 1024s vol raid > sd name plex1.s0 drive d1 plex plex1 len 4193280s driveoffset 265s plexoffset 0s > sd name plex1.s1 drive d2 plex plex1 len 4193280s driveoffset 265s plexoffset 1024s > sd name plex1.s2 drive d3 plex plex1 len 4193280s driveoffset 265s plexoffset 2048s > sd name plex1.s3 drive d4 plex plex1 len 4193280s driveoffset 265s plexoffset 3072s > sd name plex1.s4 drive d5 plex plex1 len 4193280s driveoffset 265s plexoffset 4096s > sd name plex1.s5 drive d6 plex plex1 len 4193280s driveoffset 265s plexoffset 5120s > > vinum -> l > Configuration summary > > Drives: 6 (8 configured) > Volumes: 1 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 6 (16 configured) > > D d1 State: up Device /dev/da1d Avail: 0/2047 MB (0%) > D d2 State: up Device /dev/da2d Avail: 0/2047 MB (0%) > D d3 State: up Device /dev/da3d Avail: 0/2047 MB (0%) > D d4 State: up Device /dev/da4d Avail: 0/2047 MB (0%) > D d5 State: up Device /dev/da5d Avail: 0/2047 MB (0%) > D d6 State: up Device /dev/da6d Avail: 0/2047 MB (0%) > > V raid State: up Plexes: 1 Size: 9 GB > > P plex1 R5 State: up Subdisks: 6 Size: 9 GB > > S plex1.s0 State: up PO: 0 B Size: 2047 MB > S plex1.s1 State: up PO: 512 kB Size: 2047 MB > S plex1.s2 State: up PO: 1024 kB Size: 2047 MB > S plex1.s3 State: up PO: 1536 kB Size: 2047 MB > S plex1.s4 State: up PO: 2048 kB Size: 2047 MB > S plex1.s5 State: up PO: 2560 kB Size: 2047 MB > > proxy-03-real# mount /dev/vinum/raid /mnt > mount: /dev/vinum/raid on /mnt: incorrect super block Have you newfs'd? > proxy-03-real# newfs /dev/vinum/rraid > newfs: /dev/vinum/rraid: `d' partition is unavailable From newfs(8): -v Specify that the disk does not contain any partitions, and that newfs should build a file system on the whole disk. This option is useful for synthetic disks such as vinum. From vinum(8): Creating file systems on Vinum volumes You do not need to run disklabel before creating a file system on a vinum volume. Just run newfs against the raw device. Use the -v option to state that the device is not divided into partitions. For example, to create a file system on volume mirror, enter the following command: # newfs -v /dev/vinum/rmirror > proxy-03-real# vinum > vinum -> label raid > > Doesn't make any difference... From vinum(8): label volume The label command writes a ufs style volume label on a volume. It is a simple alternative to an appropriate call to disklabel. This is needed because some ufs commands still read the disk to find the label instead of using the correct ioctl call to access it. vinum maintains a volume label separately from the volume data, so this command is not needed for newfs. This command is deprecated. > proxy-03-real# disklabel -r /dev/vinum/rraid > # /dev/vinum/rraid: > type: Vinum > disk: vinum > label: raid > flags: > bytes/sector: 512 > sectors/track: 20966400 > tracks/cylinder: 1 > sectors/cylinder: 20966400 > cylinders: 1 > sectors/unit: 20966400 > rpm: 14400 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 3 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 20966400 0 4.2BSD 1024 8192 0 # (Cyl. 0 - 0) > b: 20966400 0 swap # (Cyl. 0 - 0) > c: 20966400 0 unused 0 0 # (Cyl. 0 - 0) > proxy-03-real# From vinum(4): DISK LABELS Conventional disk special devices have a disk label in the second sector of the device. See disklabel(5) for more details. This disk label de- scribes the layout of the partitions within the device. vinum does not subdivide volumes, so volumes do not contain a physical disk label. For convenience, vinum implements the ioctl calls DIOCGDINFO (get disk la- bel), DIOCGPART (get partition information), DIOCWDINFO (write partition information) and DIOCSDINFO (set partition information). DIOCGDINFO and DIOCGPART refer to an internal representation of the disk label which is not present on the volume. As a result, the -r option of disklabel(8), which reads the "raw disk", will fail. In general, disklabel(8) serves no useful purpose on a vinum volume. If you run it, it will show you three partitions, a, b and c, all the same except for the fstype, for example: 3 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2048 0 4.2BSD 1024 8192 0 # (Cyl. 0 - 0) b: 2048 0 swap # (Cyl. 0 - 0) c: 2048 0 unused 0 0 # (Cyl. 0 - 0) > So why can't I mount or newfs this? > > proxy-03-real# uname -a > FreeBSD proxy-03-real.cdsnet.net 3.4-STABLE FreeBSD 3.4-STABLE #0: Sat Feb 12 03:17:07 PST 2000 > root@proxy-03-real.cdsnet.net:/n/FreeBSD/RELENG_3-2000-02-12/src/sys/compile/UDB-02i386 > > On a nearly identical machine using the stripe commands on the same > configuration of drives worked fine... > > I'm missing something obvious... Yup, the man pages. They're your friend. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers 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?20000213142100.T89378>