Date: Fri, 04 Mar 2005 11:52:57 -0600 From: matt virus <mattvirus@navix.net> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org>, freebsd <freebsd-questions@FreeBSD.org> Subject: Re: Vinum raid5 problems...... Message-ID: <4228A079.40002@navix.net> In-Reply-To: <20050304014545.GT73981@wantadilla.lemis.com> References: <42278323.9080304@navix.net> <20050304014545.GT73981@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg 'groggy' Lehey wrote: > On Thursday, 3 March 2005 at 15:35:31 -0600, matt virus wrote: > >>Hi all: >> >>I have a FBSD 5.2.1 box running vinum. 7 *160gb drives in a raid5 array. >> >>I can post specific errors and logs and such later, i'm away from the >>box right now --- anybody have any thoughts ? > > > How about http://www.vinumvm.org/vinum/how-to-debug.html? > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply or reply to the original recipients. > For more information, see http://www.lemis.com/questions.html > See complete headers for address and phone numbers. freebsd 5.2.1 specific problems: 1) a post-mount FSCK causes a kernel panic 2) an FSCK from single user mode errors with "cannot allocate xxxxxxxx bytes for inphead" 3) in single user mode, the array will mount and do a small fsck - recalculate the superblock, and then allow me to traverse the array. When i try to access files on the array, i get an error : "null rqg" zero source changes Vinum List: vinum -> list 7 drives: D d7 State: up /dev/ad11s1d A: 0/156327 MB (0%) D d6 State: up /dev/ad10s1d A: 0/156327 MB (0%) D d5 State: up /dev/ad8s1d A: 0/156327 MB (0%) D d4 State: up /dev/ad7s1d A: 0/156327 MB (0%) D d3 State: up /dev/ad6s1d A: 0/156327 MB (0%) D d2 State: up /dev/ad5s1d A: 0/156327 MB (0%) D d1 State: up /dev/ad4s1d A: 0/156327 MB (0%) 1 volumes: V raid5 State: up Plexes: 1 Size: 915 GB 1 plexes: P raid5.p0 R5 State: up Subdisks: 7 Size: 915 GB 7 subdisks: S raid5.p0.s0 State: up D: d1 Size: 152 GB S raid5.p0.s1 State: up D: d2 Size: 152 GB S raid5.p0.s2 State: up D: d3 Size: 152 GB S raid5.p0.s3 State: up D: d4 Size: 152 GB S raid5.p0.s4 State: up D: d5 Size: 152 GB S raid5.p0.s5 State: up D: d6 Size: 152 GB S raid5.p0.s6 State: up D: d7 Size: 152 GB Vinum log extract: A few days ago, the array was "mucked" -- i saw one of subdisks was down...here's the log from that incident 2 Mar 2005 21:46:22.721677 *** vinum started *** 2 Mar 2005 21:46:25.871262 list 2 Mar 2005 21:46:28.935388 start 2 Mar 2005 21:46:31.153046 list 2 Mar 2005 21:46:46.616922 start raid5.p0.s6 2 Mar 2005 21:46:49.949753 quit Other than that - there is nothing of particular note in the vinum history - the entire file can be supplied if need be. Kernel dumps will be supplied later today or tomorrow - i'm not going to load up and dump the raid5 array for fear of further corruption. I'm gathering hardware to make an image of it onto a hardware raid5 controller and see if i can salvage it from there. If you need more, say the word. The kernel dumps will come soon -- Matt Virus ("veer-iss") http://www.mattvirus.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4228A079.40002>