Date: Tue, 21 May 2002 11:14:16 -0700 (PDT) From: chuck sumner <chuck@2inches.com> To: freebsd-questions@freebsd.org Subject: vinum, softupdates, and fsck problems Message-ID: <20020521110910.V8744-100000@ns1.2inches.com>
next in thread | raw e-mail | index | archive | help
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? 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?20020521110910.V8744-100000>