Re: Vinum raid5 problems......

From: matt virus (mattvirus_at_navix.net)
Date: 03/04/05

  • Next message: Gary Kline: "Re: any ideas why these xorg hassles???"
    Date: Fri, 04 Mar 2005 11:52:57 -0600
    To: "Greg 'groggy' Lehey" <grog@FreeBSD.org>, freebsd <freebsd-questions@FreeBSD.org>
    
    

    Greg 'groggy' Lehey wrote:
    > On Thursday, 3 March 2005 at 15:35:31 -0600, matt virus wrote:
    >
    >>Hi all:
    >>
    >>I have a FBSD 5.2.1 box running vinum. 7 *160gb drives in a raid5 array.
    >>
    >>I can post specific errors and logs and such later, i'm away from the
    >>box right now --- anybody have any thoughts ?
    >
    >
    > How about http://www.vinumvm.org/vinum/how-to-debug.html?
    >
    > Greg
    > --
    > When replying to this message, please copy the original recipients.
    > If you don't, I may ignore the reply or reply to the original recipients.
    > For more information, see http://www.lemis.com/questions.html
    > See complete headers for address and phone numbers.

    freebsd 5.2.1

    specific problems:

    1) a post-mount FSCK causes a kernel panic
    2) an FSCK from single user mode errors with "cannot allocate xxxxxxxx
    bytes for inphead"
    3) in single user mode, the array will mount and do a small fsck -
    recalculate the superblock, and then allow me to traverse the array.
    When i try to access files on the array, i get an error :
    "null rqg"

    zero source changes

    Vinum List:

    vinum -> list
    7 drives:
    D d7 State: up /dev/ad11s1d A: 0/156327 MB (0%)
    D d6 State: up /dev/ad10s1d A: 0/156327 MB (0%)
    D d5 State: up /dev/ad8s1d A: 0/156327 MB (0%)
    D d4 State: up /dev/ad7s1d A: 0/156327 MB (0%)
    D d3 State: up /dev/ad6s1d A: 0/156327 MB (0%)
    D d2 State: up /dev/ad5s1d A: 0/156327 MB (0%)
    D d1 State: up /dev/ad4s1d A: 0/156327 MB (0%)

    1 volumes:
    V raid5 State: up Plexes: 1 Size: 915 GB

    1 plexes:
    P raid5.p0 R5 State: up Subdisks: 7 Size: 915 GB

    7 subdisks:
    S raid5.p0.s0 State: up D: d1 Size: 152 GB
    S raid5.p0.s1 State: up D: d2 Size: 152 GB
    S raid5.p0.s2 State: up D: d3 Size: 152 GB
    S raid5.p0.s3 State: up D: d4 Size: 152 GB
    S raid5.p0.s4 State: up D: d5 Size: 152 GB
    S raid5.p0.s5 State: up D: d6 Size: 152 GB
    S raid5.p0.s6 State: up D: d7 Size: 152 GB

    Vinum log extract:

    A few days ago, the array was "mucked" -- i saw one of subdisks was
    down...here's the log from that incident

    2 Mar 2005 21:46:22.721677 *** vinum started ***
      2 Mar 2005 21:46:25.871262 list
      2 Mar 2005 21:46:28.935388 start
      2 Mar 2005 21:46:31.153046 list
      2 Mar 2005 21:46:46.616922 start raid5.p0.s6
      2 Mar 2005 21:46:49.949753 quit

    Other than that - there is nothing of particular note in the vinum
    history - the entire file can be supplied if need be.

    Kernel dumps will be supplied later today or tomorrow - i'm not going to
    load up and dump the raid5 array for fear of further corruption. I'm
    gathering hardware to make an image of it onto a hardware raid5
    controller and see if i can salvage it from there.

    If you need more, say the word. The kernel dumps will come soon

    -- 
    Matt Virus ("veer-iss")
    http://www.mattvirus.net
    _______________________________________________
    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: Gary Kline: "Re: any ideas why these xorg hassles???"

    Relevant Pages

    • RE: Hardware RAID
      ... > great thing if you need reliability for a lower price. ... Well that may be so but RAID reliability is kind of like this: ... vinum install that blew my array - which is online for anyone to download ...
      (freebsd-questions)
    • Re: vinum setup
      ... > thanx Greg, you're right as always. ... > vinum mirrored volumes. ... > fstab, reboot, vinum module loads but root can not be mounted as a vinum ...
      (freebsd-questions)
    • Re: Yet another crash in FreeBSD 5.1
      ... > This is BS, Greg. ... Terry, why don't you come to my debug tutorial at the BSDCon next ... > question, Vinum is loaded as a module, and it's the FreeBSD code ... > that Vinum calls, not Vinum, that's causing the crash. ...
      (freebsd-current)
    • Re: Yet another crash in FreeBSD 5.1
      ... >> Please take a look at an older thread named vinum or geom bug? ... >> Greg asked for special debug output, but it never happened again for me. ... > A real murphy bug - it happend on three machines once a day and after ...
      (freebsd-current)
    • Vinum, replaced disk -- fsck error.
      ... I had a failed disk in my RAID-0 Vinum array. ...
      (freebsd-questions)