Date: Thu, 7 Oct 1999 23:34:15 -0400 (EDT) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: grog@lemis.com (Greg Lehey) Cc: pds@uberhacker.org (Paul D . Schmidt), freebsd-questions@FreeBSD.ORG Subject: Re: vinum volume corrupted Message-ID: <199910080334.XAA19920@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <19991008112839.V78191@freebie.lemis.com> from Greg Lehey at "Oct 8, 1999 11:28:40 am"
next in thread | previous in thread | raw e-mail | index | archive | help
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? > > No. I don't know why your system takes a long time, but I'm pretty > sure it isn't because of Vinum. > > > I believe I read how to set this up in the freebsd diary, but it > > didn't say anything about how to stop vinum, just how to start > > it.... > > Well, the FreeBSD diary isn't exactly the definitive description of > Vinum. That's what man pages are for. To stop vinum, you enter the > command (wait for it) 'vinum stop'. But you don't need to do it > before a reboot. > > > Here is the output of vinum list: > > Configuration summary > > > > Drives: 1 (4 configured) > > Volumes: 1 (4 configured) > > Plexes: 1 (8 configured) > > Subdisks: 2 (16 configured) > > > > 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 > > >From vinum(4): > > crashed A subdisk entry which has been created completely. All > fields are correct, the disk has been updated, and the > data was valid, but since then the drive has gone down. > No attempt has been made to write to the subdisk since > the crash, so the data is valid. > > 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? -- Crist J. Clark cjclark@home.com 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?199910080334.XAA19920>