vinum limits disk size to 255MB

From: Markus Hoenicka (markus.hoenicka_at_mhoenicka.de)
Date: 12/06/04

  • Next message: Noah: "create bootable drive"
    Date: Mon, 6 Dec 2004 00:28:01 +0100
    To: freebsd-questions@freebsd.org
    
    

    Hi all,

    I'm trying to set up vinum on a freshly installed FreeBSD 5.3-BETA7
    box. The system is installed on da0. I want to use three 18G SCSI
    drives to create a vinum volume.

    For some reason vinum believes the disks hold a mere 255MB. This is
    what vinum sets the subdisk length if I specify "0m" as the length
    (meaning "use all available space" according to the manual). If I
    specify any larger size manually, vinum complains that there is "No
    space left on device" which strikes me odd. I *believe* that the fdisk
    and bsdlabel outputs reprinted below show that the disks are indeed
    18G. According to my math, the appropriate size to specify in the
    vinum configuration would be 35566215s, that is the number of sectors
    of the smaller disks minus 265.

    I see only one minor problem: The disks are not identical, with
    da1 having a slightly larger capacity than da2 and da3.

    Can anyone throw me a ring here?

    Thanks,
    Markus

    fdisk da1 shows:
    ******* Working on device /dev/da1 *******
    parameters extracted from in-core disklabel are:
    cylinders=2231 heads=255 sectors/track=63 (16065 blks/cyl)

    Figures below won't work with BIOS for partitions not in cyl 1
    parameters to be used for BIOS calculations are:
    cylinders=2231 heads=255 sectors/track=63 (16065 blks/cyl)

    Media sector size is 512
    Warning: BIOS sector numbering starts with sector 1
    Information from DOS bootblock is:
    The data for partition 1 is:
    sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
        start 63, size 35840952 (17500 Meg), flag 80 (active)
            beg: cyl 0/ head 1/ sector 1;
            end: cyl 182/ head 254/ sector 63
    The data for partition 2 is:
    <UNUSED>
    The data for partition 3 is:
    <UNUSED>
    The data for partition 4 is:
    <UNUSED>

    fdisk da2 or da3 show:
    ******* Working on device /dev/da2 *******
    parameters extracted from in-core disklabel are:
    cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl)

    Figures below won't work with BIOS for partitions not in cyl 1
    parameters to be used for BIOS calculations are:
    cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl)

    Media sector size is 512
    Warning: BIOS sector numbering starts with sector 1
    Information from DOS bootblock is:
    The data for partition 1 is:
    sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
        start 63, size 35551782 (17359 Meg), flag 80 (active)
            beg: cyl 0/ head 1/ sector 1;
            end: cyl 1023/ head 254/ sector 63
    The data for partition 2 is:
    <UNUSED>
    The data for partition 3 is:
    <UNUSED>
    The data for partition 4 is:
    <UNUSED>

    bsdlabel -A da1 shows:
    # /dev/da1:
    type: unknown
    disk: amnesiac
    label:
    flags:
    bytes/sector: 512
    sectors/track: 63
    tracks/cylinder: 255
    sectors/cylinder: 16065
    cylinders: 2231
    sectors/unit: 35843670
    rpm: 3600
    interleave: 1
    trackskew: 0
    cylinderskew: 0
    headswitch: 0 # milliseconds
    track-to-track seek: 0 # milliseconds
    drivedata: 0

    8 partitions:
    # size offset fstype [fsize bsize bps/cpg]
      c: 35843670 0 unused 0 0 # "raw" part, don't edit
      e: 35843670 0 vinum

    bsdlabel -A da2 or da3 show:
    # /dev/da2:
    type: unknown
    disk: amnesiac
    label:
    flags:
    bytes/sector: 512
    sectors/track: 63
    tracks/cylinder: 255
    sectors/cylinder: 16065
    cylinders: 2213
    sectors/unit: 35566480
    rpm: 3600
    interleave: 1
    trackskew: 0
    cylinderskew: 0
    headswitch: 0 # milliseconds
    track-to-track seek: 0 # milliseconds
    drivedata: 0

    8 partitions:
    # size offset fstype [fsize bsize bps/cpg]
      c: 35566480 0 unused 0 0 # "raw" part, don't edit
      e: 35566480 0 vinum

    The vinum config file reads:
    drive ibma device /dev/da1s1e
    drive ibmb device /dev/da2s1e
    drive ibmc device /dev/da3s1e
    volume raid5 setupstate
      plex org concat
        sd length 0m drive ibma
        sd length 0m drive ibmb
        sd length 0m drive ibmc

    vinum -> create vinumconfig1
    3 drives:
    D ibma State: up /dev/da1s1e A:0/256 MB (0%)
    D ibmb State: up /dev/da2s1e A:0/256 MB (0%)
    D ibmc State: up /dev/da3s1e A:0/256 MB (0%)

    1 volumes:
    V raid5 State: up Plexes: 1 size: 767 MB

    3 subdisks:
    S raid5.p0.s0 State: up D: ibma Size: 255MB
    S raid5.p0.s1 State: up D: ibmb Size: 255MB
    S raid5.p0.s2 State: up D: ibmc Size: 255MB

    uname -a shows:
    FreeBSD wutz.mininet 5.3-BETA7 FreeBSD 5.3-BETA7 #0: Sat Oct 2 21:01:00 UTC 2004 root@wv1u.samsco.home:/usr/obj/usr/src/sys/GENERIC i386

    -- 
    Markus Hoenicka
    markus.hoenicka@cats.de
    (Spam-protected email: replace the quadrupeds with "mhoenicka")
    http://www.mhoenicka.de
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Noah: "create bootable drive"

    Relevant Pages

    • Re: Why SetFilePointerEx cant accept a negative number as the distance offset?
      ... It could be that files opened to the whole partition don't have "size" ... Even though we don't know in the physical hardware which sector is "last" ... remapping, RAID drives, virtual drives, etc.) there is no way to even ... "Even if I change the value -512 to 0, the call to SetFilePointerEx ...
      (microsoft.public.vc.mfc)
    • disklabel and fdisk cant write to disk. Interactive versions?
      ... When I run fdisk and dislabel from /stand/sysinstall, ... This happens on all four scsi drives on this system, ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
      (comp.unix.bsd.freebsd.misc)
    • Re: Anyone used paragon drive backup 5.5 with SCO partitions?
      ... > any type of partition because it can do a sector to sector copy. ... has the same geometry as the old ... transport partition data between IDE and SCSI drives. ...
      (comp.unix.sco.misc)
    • Re: Drive Image destroyed partition
      ... >I'm also curious as to how you have your cables set up to those drives. ... I started the morning by recovering my E partition, ... E. Then, because of that bad sector message, I did ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: [SOLVED] installkernel succeeds, but old kernel boots
      ... then running off the current drive once vinum got loaded. ... I am booting off a vinum root, ... have the a partition adjusted on both root drives so that it appears to be ... the drives that are on ad1s1. ...
      (freebsd-stable)