Vinum / 4.8 / Referenced disk / Recovery

From: Michael G. Jung (mikej_at_confluenttech.com)
Date: 05/31/03

  • Next message: Peter Jeremy: "Re: Network stack cloning / virtualization patches" 
    Date: Fri, 30 May 2003 18:21:53 -0400
To: <freebsd-fs@freebsd.org>, <freebsd-hackers@freebsd.org>

    After a reboot on 4.8 I ended up with a degraded raid 5 partition...

    The only thing special about my setup is.... 4944 drives spread over 3 channels,
    running SMP kernel.....

    One sub disk was down and the and the drive was referenced... in scouring the
     mailing lists I saw where a referenced disk means you have referenced a
     non-existent drive - I read this as one vinum didn't think was defined.. in my
    case it was drive29 --> /dev/da29s1e

    I don't know how this got referenced !!! It's been reboot many times and this has
    not happened.

    So I boldly created a config file for vinum and re-created the drive.....

    --- config file ----
    drive drvie29 device /dev/da29e
    --- end ----

    but I still can not start the sub disk.....

    (root@jammin) /home/staff/mikej# vinum start raid5-1.p0.s15
    Can't start raid5-1.p0.s15: Drive is down (5)
    (root@jammin) /home/staff/mikej#

    Here is what vinum thinks...... Do I rm the sub disk and re-create it?????
    Will this kill my raid-5 partition ??

    Thanks !!

    (root@jammin) /home/staff/mikej# vinum printconfig
    # Vinum configuration of jammin.mikej.com, saved at Fri May 30 18:15:48 2003
    drive drive1 device /dev/da1s1e
    drive drive2 device /dev/da2s1e
    drive drive3 device /dev/da3s1e
    drive d2 device /dev/da15s1e
    drive drive16 device /dev/da16s1e
    drive drive17 device /dev/da17s1e
    drive drive18 device /dev/da18s1e
    drive drive19 device /dev/da19s1e
    drive d1 device /dev/da20s1e
    drive drive21 device /dev/da21s1e
    drive drive22 device /dev/da22s1e
    drive drive23 device /dev/da23s1e
    drive drive24 device /dev/da24s1e
    drive drive25 device /dev/da25s1e
    drive drive26 device /dev/da26s1e
    drive drive27 device /dev/da27s1e
    drive drive28 device /dev/da28s1e
    drive drive29 device /dev/da29s1e
    drive *invalid* device
    volume mirror1
    volume raid5-1
    plex name mirror1.p0 org concat vol mirror1
    plex name mirror1.p1 org concat vol mirror1
    plex name raid5-1.p0 org raid5 62s vol raid5-1
    sd name mirror.p0.s0 drive d1 plex mirror1.p0 len 35551232s driveoffset 265s plexoffset 0s
    sd name mirror.p1.s0 drive d2 plex mirror1.p1 len 35551232s driveoffset 265s plexoffset 0s
    sd name raid5-1.p0.s0 drive drive1 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 0s
    sd name raid5-1.p0.s1 drive drive2 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 62s
    sd name raid5-1.p0.s2 drive drive3 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 124s
    sd name raid5-1.p0.s3 drive drive16 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 186s
    sd name raid5-1.p0.s4 drive drive17 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 248s
    sd name raid5-1.p0.s5 drive drive18 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 310s
    sd name raid5-1.p0.s6 drive drive19 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 372s
    sd name raid5-1.p0.s7 drive drive21 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 434s
    sd name raid5-1.p0.s8 drive drive22 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 496s
    sd name raid5-1.p0.s9 drive drive23 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 558s
    sd name raid5-1.p0.s10 drive drive24 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 620s
    sd name raid5-1.p0.s11 drive drive25 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 682s
    sd name raid5-1.p0.s12 drive drive26 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 744s
    sd name raid5-1.p0.s13 drive drive27 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 806s
    sd name raid5-1.p0.s14 drive drive28 plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 868s
    sd name raid5-1.p0.s15 drive *invalid* plex raid5-1.p0 len 35551172s driveoffset 265s plexoffset 930s

    (root@jammin) /etc# vinum l
    18 drives:
    D drive1 State: up Device /dev/da1s1e Avail: 0/17359 MB (0%)
    D drive2 State: up Device /dev/da2s1e Avail: 0/17359 MB (0%)
    D drive3 State: up Device /dev/da3s1e Avail: 0/17359 MB (0%)
    D d2 State: up Device /dev/da15s1e Avail: 0/17359 MB (0%)
    D drive16 State: up Device /dev/da16s1e Avail: 0/17359 MB (0%)
    D drive17 State: up Device /dev/da17s1e Avail: 0/17359 MB (0%)
    D drive18 State: up Device /dev/da18s1e Avail: 0/17359 MB (0%)
    D drive19 State: up Device /dev/da19s1e Avail: 0/17359 MB (0%)
    D d1 State: up Device /dev/da20s1e Avail: 0/17359 MB (0%)
    D drive21 State: up Device /dev/da21s1e Avail: 0/17359 MB (0%)
    D drive22 State: up Device /dev/da22s1e Avail: 0/17359 MB (0%)
    D drive23 State: up Device /dev/da23s1e Avail: 0/17359 MB (0%)
    D drive24 State: up Device /dev/da24s1e Avail: 0/17359 MB (0%)
    D drive25 State: up Device /dev/da25s1e Avail: 0/17359 MB (0%)
    D drive26 State: up Device /dev/da26s1e Avail: 0/17359 MB (0%)
    D drive27 State: up Device /dev/da27s1e Avail: 0/17359 MB (0%)
    D drive28 State: up Device /dev/da28s1e Avail: 0/17359 MB (0%)
    D drive29 State: up Device /dev/da29s1e Avail: 17359/17359 MB (100%)
    D *invalid* State: referenced Device Avail: 0/0 MB

    2 volumes:
    V mirror1 State: up Plexes: 2 Size: 16 GB
    V raid5-1 State: up Plexes: 1 Size: 254 GB

    3 plexes:
    P mirror1.p0 C State: up Subdisks: 1 Size: 16 GB
    P mirror1.p1 C State: up Subdisks: 1 Size: 16 GB
    P raid5-1.p0 R5 State: degraded Subdisks: 16 Size: 254 GB

    18 subdisks:
    S mirror.p0.s0 State: up PO: 0 B Size: 16 GB
    S mirror.p1.s0 State: up PO: 0 B Size: 16 GB
    S raid5-1.p0.s0 State: up PO: 0 B Size: 16 GB
    S raid5-1.p0.s1 State: up PO: 31 kB Size: 16 GB
    S raid5-1.p0.s2 State: up PO: 62 kB Size: 16 GB
    S raid5-1.p0.s3 State: up PO: 93 kB Size: 16 GB
    S raid5-1.p0.s4 State: up PO: 124 kB Size: 16 GB
    S raid5-1.p0.s5 State: up PO: 155 kB Size: 16 GB
    S raid5-1.p0.s6 State: up PO: 186 kB Size: 16 GB
    S raid5-1.p0.s7 State: up PO: 217 kB Size: 16 GB
    S raid5-1.p0.s8 State: up PO: 248 kB Size: 16 GB
    S raid5-1.p0.s9 State: up PO: 279 kB Size: 16 GB
    S raid5-1.p0.s10 State: up PO: 310 kB Size: 16 GB
    S raid5-1.p0.s11 State: up PO: 341 kB Size: 16 GB
    S raid5-1.p0.s12 State: up PO: 372 kB Size: 16 GB
    S raid5-1.p0.s13 State: up PO: 403 kB Size: 16 GB
    S raid5-1.p0.s14 State: up PO: 434 kB Size: 16 GB
    S raid5-1.p0.s15 State: stale PO: 465 kB Size: 16 GB
    (root@jammin) /etc#
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

  • Next message: Peter Jeremy: "Re: Network stack cloning / virtualization patches"

    Relevant Pages

    • vinum limits disk size to 255MB
      ... I'm trying to set up vinum on a freshly installed FreeBSD 5.3-BETA7 ... drives to create a vinum volume. ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
      (freebsd-questions)
    • RE: FreeBSD5.1 Vinum Mirror root
      ... Machine will run one copy of FreeBSD5.1 and has three hard drives: ... The 200GB drives are mirrored root vinum ... - Web server configuration & website version control ... - Keeps FreeBSD 5.1 up-to-date using cvsup nightly. ...
      (freebsd-questions)
    • Re: vinum setup
      ... thanx Greg, you're right as always. ... I booted into single user from start up and sure enough everything was ... I set up 2 disks for vinum and want to allocate exisiting partitions to ... config, everything's peachy, drives rebuild, fsck sees no errors, I edit ...
      (freebsd-questions)
    • Re: Vinum Subdisk Crashed - How To Repair?
      ... >> as I don't have a backup. ... > This should go away if you stop and restart Vinum. ... Disabling configuration updates ...
      (freebsd-questions)
    • vinum on atapi raid
      ... i'm trying to set up a concatenated vinum volume. ... sectors/track: 63 ... something similar happens when i'm using the concat command to vinum: ...
      (freebsd-questions)