Date: Wed, 22 May 2002 09:01:10 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: chuck sumner <chuck@2inches.com> Cc: freebsd-questions@freebsd.org Subject: Re: vinum, softupdates, and fsck problems Message-ID: <20020522090110.I84431@wantadilla.lemis.com> In-Reply-To: <20020521110910.V8744-100000@ns1.2inches.com> References: <20020521110910.V8744-100000@ns1.2inches.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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?20020522090110.I84431>