From owner-freebsd-stable Thu Mar 15 17:25:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id EDCA637B71A for ; Thu, 15 Mar 2001 17:25:18 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2G1P6552546; Thu, 15 Mar 2001 17:25:06 -0800 (PST) (envelope-from dillon) Date: Thu, 15 Mar 2001 17:25:06 -0800 (PST) From: Matt Dillon Message-Id: <200103160125.f2G1P6552546@earth.backplane.com> To: Harald Schmalzbauer Cc: stable@FreeBSD.ORG Subject: Re: yet another vinum panic (was How to debug - find error?) References: <18530.984696495@www10.gmx.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This box has to collect data overnight (~250G at the moment) for caching it :to push it on tape at the weekend. Therefore I need the four 80G in one 320G :Volume. : :Last weekend the box died silently when I did a fsck on any VolumeManager. :This was a BIOS error from Supermicro. They sent me a new one, now :transferrate is doubled and nothing like that happens. : :But when I use vinum/ccd (doesn't matter which one) after some dozends of :Gigs, the box crashes. No matter whether I use concat or striped. For testing :I'm simultaniously coping data form the RAID and from a NFS mounted disk to :the striped volume because only using slow NFS, the box lives longer. : :Here my vinum.conf: :drive d1 device /dev/ad0e :drive d2 device /dev/ad1e :drive d3 device /dev/ad2e :drive d4 device /dev/ad3e The error you reported was related to your '/backup' filesystem. What is /backup represented by? The RAID volume or the vinum/ccd partition? Are the files you are copying lots of little files or a few really big files? Did you use any special filesystem parameters when you newfs'd your machine's filesystems? There are all sorts of possible sources to the problem unfortunately, it may not be possible to easily diagnose it. It could be the RAID, NFS, a bug in the kernel, a bug in the network stack... just about anything. For the last few months I've been trying to track down a problem similar to the one you've just reported with little success. The first thing I would do, if you haven't already, is upgrade to the absolute latest FreeBSD-stable kernel. -Matt :Thanks, : :-Harry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message