[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

kern/76871: vinum / does not find its second drive



The following reply was made to PR kern/76871; it has been noted by GNATS.

From: Greg 'groggy' Lehey <grog_(_at_)_FreeBSD_(_dot_)_org>
To: Arne Woerner <arne_woerner_(_at_)_yahoo_(_dot_)_com>
Cc: freebsd-gnats-submit_(_at_)_FreeBSD_(_dot_)_org
Subject: Re: kern/76871: vinum / does not find its second drive
Date: Mon, 31 Jan 2005 08:29:26 +1030

 --kvWJmX0bB3Sab/3X
 Content-Type: text/plain; charset=iso-8859-1
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 [Format recovered--see http://www.lemis.com/email/email-format.html]
 
 Overlong text lines.
 
 Corrected From: name.
 
 Note that your name contains a non-ASCII character.  This is not legal
 in mail headers, so your name shows as Wrner.
 
 On Sunday, 30 January 2005 at 21:33:25 +0000, Arne Wrner wrote:
 >
 >> Number:         76871
 >> Category:       kern
 >> Synopsis:       vinum / does not find its second drive
 >> Confidential:   no
 >> Severity:       serious
 >> Priority:       medium
 >> Responsible:    freebsd-bugs
 >> State:          open
 >> Quarter:
 >> Keywords:
 >> Date-Required:
 >> Class:          sw-bug
 >> Submitter-Id:   current-users
 >> Arrival-Date:   Sun Jan 30 21:40:15 GMT 2005
 >> Closed-Date:
 >> Last-Modified:
 >> Originator:     Arne W=F6rner
 >> Release:        R5.3
 >> Organization:
 >> Environment:
 > FreeBSD neo.riddick.homeunix.org. 5.3-RELEASE FreeBSD 5.3-RELEASE #24: We=
 d Jan 26 20:08:08 UTC 2005     aw_(_at_)_neo_(_dot_)_riddick_(_dot_)_homeunix_(_dot_)_org_(_dot_)_:/opt/src/sys/i3=
 86/compile/RIDDICK  i386
 >
 >> Description:
 
 > After I used a 4.9-STABLE miniinst CD, vinum complained about
 > missing subdisks.
 
 Your system is complaining about a missing drive:
 
 > D riddick               State: referenced       unknown A: 0/0 MB
 > neo# vinum read
 > neo# vinum l
 > 2 drives:
 > D vaako                 State: up       /dev/ad0s1d     A: 0/32768 MB (0%)
 > D riddick               State: up       /dev/ad1s1d     A: 32767/32768 MB=
  (100%)
 >
 > 2 volumes:
 > V base                  State: up       Plexes:       2 Size:        512 =
 MB
 > V user                  State: up       Plexes:       2 Size:         31 =
 GB
 >
 > 4 plexes:
 > P base0               C State: up       Subdisks:     1 Size:        512 =
 MB
 > P user1               C State: faulty   Subdisks:     1 Size:         31 =
 GB
 > P user0               C State: up       Subdisks:     1 Size:         31 =
 GB
 > P base1               C State: faulty   Subdisks:     1 Size:        512 =
 MB
 >
 > 4 subdisks:
 > S base0.s0              State: up       D: vaako        Size:        512 =
 MB
 > S user1.s0              State: stale    D: riddick      Size:         31 =
 GB
 > S user0.s0              State: up       D: vaako        Size:         31 =
 GB
 > S base1.s0              State: stale    D: riddick      Size:        512 =
 MB
 
 And now there are no missing subdisks.
 
 > Here are both disklabels:
 
 These are not necessary.
 
 > Here is my vinum dumpconfig:
 
 =46rom http://www.vinumvm.org/vinum/how-to-debug.html:
 
  Please don't supply the following information unless I ask for it:
 
     * The output of the vinum printconfig command.
     * Your Vinum configuration file, unless your problem is that you
       can't start Vinum at all.
 
 > Here is my mount output:
 
 This is also unnecessary.
 
 Also from http://www.vinumvm.org/vinum/how-to-debug.html:
 
 What information to supply
 
   #  Supply an extract of the Vinum history file. Unless you have
      explicitly renamed it, it will be /var/log/vinum_history. This
      file can get very big; please limit it to the time around when
      you have the problems. Each line contains a timestamp at the
      beginning, so you will have no difficulty in establishing which
      data is of relevance.
 
   # Supply an extract of the file /var/log/messages. Restrict the
     extract to the same time frame as the history file. Again, each
     line contains a timestamp at the beginning, so you will have no
     difficulty in establishing which data is of relevance.
 
 Greg
 --
 When replying to this message, please take care not to mutilate the
 original text. =20
 For more information, see http://www.lemis.com/email.html
 See complete headers for address and phone numbers.
 
 --kvWJmX0bB3Sab/3X
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.6 (FreeBSD)
 
 iD8DBQFB/Vi+IubykFB6QiMRAlj+AJ40rjT3zvgg2djTqLxTXhP0Y1+ZRQCfVZ2z
 sn0HOY8O5/ybJwxUETURllc=
 =GfmM
 -----END PGP SIGNATURE-----
 
 --kvWJmX0bB3Sab/3X--