Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Oct 1999 13:04:15 +0930
From:      Greg Lehey <grog@lemis.com>
To:        cjclark@home.com
Cc:        "Paul D . Schmidt" <pds@uberhacker.org>, freebsd-questions@FreeBSD.ORG
Subject:   Re: vinum volume corrupted
Message-ID:  <19991008130415.Z78191@freebie.lemis.com>
In-Reply-To: <199910080334.XAA19920@cc942873-a.ewndsr1.nj.home.com>
References:  <19991008112839.V78191@freebie.lemis.com> <199910080334.XAA19920@cc942873-a.ewndsr1.nj.home.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday,  7 October 1999 at 23:34:15 -0400, Crist J. Clark wrote:
> Greg Lehey wrote,
>> On Thursday,  7 October 1999 at 19:21:55 -0500, Paul D . Schmidt wrote:
>>> Hi, my vinum volume git corrupted somehow, but I don't seem to be able to
>>> get it back....
>>>
>>> can't fsck it:
>>> # fsck /dev/vinum/rbigdrive
>>> ** /dev/vinum/rbigdrive
>>>
>>> CANNOT READ: BLK 59113504
>>> CONTINUE? [yn] y
>>>
>>> THE FOLLOWING DISK SECTORS COULD NOT BE READ: 59113504, 59113505, 59113506, 59113507,
>>> /dev/vinum/rbigdrive: NOT LABELED AS A BSD FILE SYSTEM (unused)
>>>
>>>
>>> I always get this error when I boot up too:
>>> vinum: loaded
>>> Can't open history file /var/tmp/vinum_history: No such file or directory (2)
>>>
>>> Also, my system takes a really long time to halt, too...could it be because
>>> vinum isn't dying properly?  Should there be a vinum stop in rc.shutdown
>>> or something?
>>>
>>> D a                     State: up	Device /dev/wd1e	Avail: 12409/12409 MB (99%)
>>> D b                     State: referenced	Device 	Avail: 0/0 MB
>>>
>>> V bigdrive              State: up	Plexes:       1	Size:         28 GB
>>>
>>> P bigdrive.p0         C State: corrupt	Subdisks:     2	Size:         28 GB
>>>
>>> S bigdrive.p0.s0        State: up	PO:        0  B Size:         12 GB
>>> S bigdrive.p0.s1        State: crashed	PO:       12 GB Size:         16 GB
>>
>> The problem you have here is that your drive b isn't being found on
>> the system.  Where is it located?  Are the contents still valid?  Take
>> a look at vinum(4) and look at the on-disk configuration.
>
> Just a thought, what is the "vinum_drives" entry in your /etc/rc.conf
> set to?

Good point.  It shouldn't be set to anything; it's going away from
rc.conf.  Use 'start_vinum' instead.

Greg
--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




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