From owner-freebsd-current  Sun Mar 26  0:51:12 2000
Delivered-To: freebsd-current@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP
	id 85E9A37B9BC; Sun, 26 Mar 2000 00:51:08 -0800 (PST)
	(envelope-from bright@fw.wintelcom.net)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.10.0/8.10.0) id e2Q9F7n17917;
	Sun, 26 Mar 2000 01:15:07 -0800 (PST)
Date: Sun, 26 Mar 2000 01:15:07 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: current@freebsd.org
Cc: phk@freebsd.org, grog@freebsd.org
Subject: vinum possible casulty of B_* patches?
Message-ID: <20000326011506.R21029@fw.wintelcom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm about to wander down vinum's source again.

With a kernel and vinum module dated approx Tue Feb 29 06:53:56
PST 2000 everything works fine.

I recently (tonight) I cvsup'd to 5.0 to play with Matt's SMP stuff
and came across a problem where it seems that 5.0 doesn't get any
IO down to my vinum striped disks.

I'll get panics, but then rebooting both my old and new kernels+modules
the vinum volume is "clean" which leads me to belive that somewhere
writes just aren't making it through to my disks.

If I do a reboot I'll loose something like thousands of buffers
but yet my vinum drive is "marked clean" on boot without the need
for fsck.

Anyhow, I just wanted to let you guys know what's going on hopefully
you'll have a solution faster than I will.

thanks,
-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message