Re: vinum experimentation

From: Greg 'groggy' Lehey (grog_at_FreeBSD.org)
Date: 12/31/03

  • Next message: Randy Bush: "panic"
    Date: Wed, 31 Dec 2003 09:30:24 +1030
    To: corbesero@cs.moravian.edu
    
    
    

    On Tuesday, 30 December 2003 at 14:15:44 -0500, Stephen Corbesero wrote:
    >
    > I hope this is information is useful. I am really hoping to have a
    > working vinum in FreeBSD 5.x.
    >
    > As we all know, vinum has been cranky for a little while now. It
    > seemed to work fine for me in the early 5.0's, but went 'south"
    > sometime as the 5.1's began coming out.

    Well, what happened were incompatibilities with changes introduced
    with GEOM. Specifically, swap on Vinum currently doesn't work, and
    it'll take a rewrite before it does.

    > I have been playing with it on a couple of machines at work, and I
    > have noticed the following behaviors. I am mostly playing with
    > mirroring some volumes on two IDE drives.
    >
    > * If I start vinum manually after the system is up, and shut it down
    > manually before I do a reboot, the configuration seems to survive
    > just fine. On the next boot, I can again start vinum manually,
    > the drives are read, and I can mount the partitions.
    >
    > * If I let vinum come up automatically (setting start_vinum="YES" in
    > rc.conf), then one of the following will happen.
    >
    > a) a system panic before the boot process is completed

    Do you have a dump?

    > b) at least one of the vinum can not be found, so anything that
    > drive is down/faulty. did discover, however, that if I
    > recreate the drive in vinum, the plexes cheerfully come
    > back.

    Do you have log files?

    > c) the vinum drives can be found, but no volumes are defined
    > anymore

    More details?

    > If this is useful, and someone would like more information, I'll be
    > happy to continue my experiments.

    This level of information is not very useful. I do all these things
    all the time, and I don't have problems. On the other hand, if you're
    having problems, I'd like to know why. Take a look at
    http://www.vinumvm.org/vinum/how-to-debug.html and supply the
    appropriate information. That way we have a hope of solving the
    problems.

    FWIW, most problems I've seen with Vinum have been pilot error.

    Greg

    --
    See complete headers for address and phone numbers.
    
    



  • Next message: Randy Bush: "panic"

    Relevant Pages

    • Re: Future of RAIDFrame and Vinum (was: Future of RAIDFrame)
      ... >> In a free software project, you can take any rule like that an put ... statistic are obviously rather crucial to the future of FreeBSD. ... Isolated features with a small user-communities, things like vinum, ... will not be fixing vinum in my own spare time. ...
      (freebsd-hackers)
    • Re: vinum related panic in 5.1-BETA2 (long backtrace)
      ... > I got this panic while running a cvs checkout of a part of the FreeBSD ... > source tree. ... Debug kernel and coredump is available if you need more info. ... If you need to contact me because of problems with Vinum, ...
      (freebsd-current)
    • Re: Large filesystems help/ideas
      ... vinum should not be used on 6.x and above, ... I understand that I could have up to 8 slices of 2 Tb, ... I've tried to install FreeBSD 7 with no success, ... Université Libre de Bruxelles (ULB) ...
      (freebsd-questions)
    • Re: The true meaning of / or root partition??
      ... > commercial UNIX systems have had these features for a while, ... in the form of vinum. ... FreeBSD is more on less in par with Linux in this domain featurewise. ...
      (comp.unix.bsd.freebsd.misc)
    • Re: Future of RAIDFrame
      ... >and extensible RAID stack to FreeBSD. ... I can't help thinking about how small the central group of developers ... As much as I would hate to see RF and Vinum disappar from our ... Greg has much chance of finding the significant amount of time ...
      (freebsd-current)