Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Apr 2003 10:25:50 +0930
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        Drew Tomlinson <drew@mykitchentable.net>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: How To Repair Vinum Subdisk?
Message-ID:  <20030425005550.GV49736@wantadilla.lemis.com>
In-Reply-To: <056601c30abf$661a0b40$6e2a6ba5@tagalong>
References:  <056601c30abf$661a0b40$6e2a6ba5@tagalong>

next in thread | previous in thread | raw e-mail | index | archive | help

--7XuS4gr/+Xj300Yp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thursday, 24 April 2003 at 17:12:28 -0700, Drew Tomlinson wrote:
> I recently added a new drive to a concatenated plex in vinum on a
> 4.8-RELEASE machine.  I edited the disklabel to type 'vinum' and then
> defined the drive as a subdisk in the plex.  The vinum 'list' command showed
> everything up and running so I used growfs to expand the file system.
> Everything appeared to finish OK.
>
> However upon my first reboot of the system, the vinum volume won't mount and
> the newly added subdisk shows a state of 'crashed'.  If I stop and restart
> the subdisk, then it shows a state of 'up' but the volume still won't mount
> as it is 'dirty' and needs to be fsck'ed.  But when I fsck the volume, the
> system core dumps on a signal 6.
>
> This particular volume consists of 3 80GB IDE drives.  The first two drives
> I've had running successfully in the machine for about a year.  Then when
> the volume filled, I bought an additional drive, put it in a firewire
> enclosure (I was out of space in the machine case), made the necessary mods
> to the kernel, and then plugged the drive into the machine.  Because I
> haven't added any additional data to the volume, there is nothing on the new
> subdisk to lose but I do want to preserve the data on the first two
> subdisks.  I also mention the firewire in case it makes a difference.
>
> Please let me know if there's any other information I can provide.  I
> attempted to go to www.vinumvm.org to find the details required for
> assistance but the site is unreachable as of 17:10 Pacific Daylight Time on
> April 24.

I see accesses round this time in the web log.  Anyway, I've checked,
and it's accessible now.  Take a look at
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

--7XuS4gr/+Xj300Yp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)

iD8DBQE+qIeWIubykFB6QiMRAgUKAJ9BfNhHs7npJe1yt3tEQMd9WY3TfQCgsQxY
BZWUMuj/udg8X06P2Lb5gnI=
=iMuo
-----END PGP SIGNATURE-----

--7XuS4gr/+Xj300Yp--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030425005550.GV49736>