Date: Tue, 21 May 2002 21:24:22 -0700 (PDT) From: chuck sumner <chuck@2inches.com> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: freebsd-questions@FreeBSD.org Subject: Re: vinum, softupdates, and fsck problems Message-ID: <20020521212349.W9196-100000@ns1.2inches.com>
next in thread | raw e-mail | index | archive | help
thanks for the reply greg i used your page on replacing a failed drive and could not get the volume up with 'create configfile' im sorry i dont have the errors now... i read how someone else had used setupstate to force a drive up. i did this as a last ditch effort and because of what i (mis)understood about softupdates. i read how it was basically ok to not fsck a drive after a crash if using S.O. i mistakenly thought this meant the state of the drive, ie: the vinum state. this is a freebsd 4.6 RC as of Sun May 19 20:59:33 PDT 2002 no changes to the source tree vinum list reports: 4 drives: D drive1 State: up Device /dev/ad4s1e Avail: 0/39266 MB (0%) D drive2 State: up Device /dev/ad5s1e Avail: 0/39266 MB (0%) D drive3 State: up Device /dev/ad6s1e Avail: 0/39266 MB (0%) D drive4 State: up Device /dev/ad7s1e Avail: 0/39266 MB (0%) 1 volumes: V raid State: up Plexes: 1 Size: 115 GB 1 plexes: P raid.p0 R5 State: up Subdisks: 4 Size: 115 GB 4 subdisks: S raid.p0.s0 State: up PO: 0 B Size: 38 GB S raid.p0.s1 State: up PO: 512 kB Size: 38 GB S raid.p0.s2 State: up PO: 1024 kB Size: 38 GB S raid.p0.s3 State: up PO: 1536 kB Size: 38 GB snippet of vinum log: 20 May 2002 13:14:02.421565 *** vinum started *** 20 May 2002 13:14:10.464219 create /root/vinum.conf <-- snip conf file --> 20 May 2002 13:14:10.467704 *** Created devices *** 20 May 2002 13:14:18.953043 start 20 May 2002 13:14:29.374573 stop 20 May 2002 13:23:15.650297 *** vinum started *** 20 May 2002 13:23:30.354327 create /root/vinum.conf <-- snip conf file --> 20 May 2002 13:23:30.373413 *** Created devices *** 20 May 2002 13:23:40.290173 list 20 May 2002 13:23:59.090653 checkparity raid.p0 20 May 2002 13:27:16.839088 rebuildparity raid.p0 On Wed, 22 May 2002, Greg 'groggy' Lehey wrote: > On Tuesday, 21 May 2002 at 11:14:16 -0700, chuck sumner wrote: > > hi all > > i am unable to fsck a vinum & softupdates volume. the error is: > >> cannot alloc 690422180 bytes for inphead > > > > i cant seem to get around this. and its annoying because df reports the > > drive as: > >> /dev/vinum/raid 116913622 -2019559125 2127119658 -1878% /mnt > > which is obviously wrong and the kernel panics when i read from it. > > > > any ideas? am i screwed? > > thanks chuck > > > > the detailed saga follows: > > i have a file server with a 4 disk raid 5 vinum array and softupdates. > > earlier this week the system disk died. no big deal. i put in a new disk > > and rebuilt the system. > > cvsuped to stable and built world with a new kernel. > > turns out getting thevinum drive back up was non trivial. > > after hours of work i managed to recreate it with a create > > /path/to/config_file and the volume masrked as setstateup. > > i had to rebuildparity which took some time, but my data was > > mostly accessable. when i tried to fsck it i got thousands of errors. > > unreferenced inodes, weird errors. all bad. i mounted it read only and > > tried to back up what i could onto another array, but after a small, > > random amount of time the kernel panics with: > >> Panic: ffs_truncate: read only filesystem > > > > much of my data is corrupted or has bad file descriptors, and i can only > > get off small bits at a time. fsck breaks from lack of memory now and i > > cant seem to clean up the drive. > > any help? > > Well, I have a whole list of information I ask for for problems like > this, both in vinum(4) and at > http://www.vinumvm.org/vinum/how-to-debug.html. Judging by what > you've said, though, you've managed to intersperse junk with your > volume and tried to treat it as a file system. ufs doesn't like that > and panics. Note the man page: > > setstate state [volume | plex | subdisk | drive] > setstate sets the state of the specified objects to the specified > state. This bypasses the usual consistency mechanism of vinum > and should be used only for recovery purposes. It is possible to > crash the system by incorrect use of this command. > > It looks like you have used it incorrectly. Did you follow the > instructions at http://www.vinumvm.org/vinum/replacing-drive.html? > What went wrong? > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply. > For more information, see http://www.lemis.com/questions.html > See complete headers for address and phone numbers > 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?20020521212349.W9196-100000>