Re: freebsd 5.3 have any problem with vinum ?

From: Greg 'groggy' Lehey (grog_at_FreeBSD.org)
Date: 10/28/04

  • Next message: Vince Refiti: "Fetchyahoo does not get message IDs" 
    Date: Thu, 28 Oct 2004 17:37:56 +0200
To: secmgr <security@jim-liesl.org>, FreeBSD Release Engineering Team <re@FreeBSD.org>

    On Monday, 25 October 2004 at 14:21:33 -0600, secmgr wrote:
    > Andrew Konstantinov wrote:
    >
    >> On Mon, 2004-10-25 at 05:55, Oliver Torres Delgado wrote:
    >>
    >>
    >>> I have freebsd 5.3 rc1 installed perfectly, i configure vinum with the
    >>> handbook and all work perfect
    >>> but when try run vinum with rc.conf there display the error:
    >>>
    >>> panic: unmount: dangling vnode
    >>> ...
    >>
    >> Just like me, you should have checked the mailing list archive first.
    >> Here is a nice solution:
    >> http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035547.html
    >
    > thanks, I appreciate the pointer. That being said, if this is a "KNOWN"
    > problem (as far back as August) how come no mention in either the
    > release notes OR errata.

    Good question.

    > I like and use FreeBSD for it's stability, but at this point in
    > time, I've got broken vinum-classic (with workarounds) raid5 in 4.10
    > and raid 1 in 5.3-stable. Both of these installed per current
    > documentation. I haven't logged bug reports becasue it seems like
    > everything is moving to gvinum, and they'd probably just end up
    > closed out as FINV

    A bit of background: we know that 'gvinum' will replace Vinum; the
    original intention had been to do it seamlessly, but for various
    reasons that did happen. Then we decided that we should leave them
    both in the tree until gvinum had the full functionality of Vinum.
    It's beginning to look like that's a bad idea. Lukas is
    (understandably) working only on gvinum, and since I know it's nearly
    there, I'm not going to do any further work on Vinum in FreeBSD 5.
    Given the problems, I'd suggest that we yank it. I'm copying the
    release engineering team. Re, what do you think?

    Greg 

    --
See complete headers for address and phone numbers
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
  • Next message: Vince Refiti: "Fetchyahoo does not get message IDs"

    Relevant Pages

    • Re: FreeBSD 5.x raid...
      ... vinum in all commands. ... Also, as mentioned before, gvinum is not yet feature complete so some of the ... things listed in the documentation for vinum doesn't work yet. ... I can't say how gmirror differs ...
      (freebsd-questions)
    • Re: Vinum configuration lost at vinum stop / start
      ... While 5.3 is IMHO pretty stable, gvinum is quite new ... > So if you need a critically stable vinum environment you would be better off ... <ACPI PCI bus> on pcib0 ... atapci1: port ...
      (freebsd-questions)
    • Re: vinum or gvinum
      ... do _NOT_ use vinum on 5.4, use gvinum. ... sd length 2080m drive pain ...
      (freebsd-stable)
    • Re: software raid survey
      ... > dump/restore to move /home from the mirror to the stripe. ... Anyways, i agree with you, vinum is extraordinary flexible and powerful, ... In the case of gvinum there is the further problem that only a small ...
      (comp.unix.bsd.freebsd.misc)
    • vinum or gvinum
      ... this is vinum v gvinum. ... Mounting root from ufs:/dev/gvinum/root ... Tried to configure the same with gvinum replicating the vinum.conf, ... Please note that whilst best efforts are made, neither the company nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments. ...
      (freebsd-stable)