Date: Wed, 15 Aug 2001 10:21:39 +0930 From: Greg Lehey <grog@FreeBSD.org> To: Michael Lucas <mwlucas@blackhelicopters.org> Cc: Poul-Henning Kamp <phk@FreeBSD.org>, current@freebsd.org Subject: devfs and Vinum (was: any -current && vinum problems?) Message-ID: <20010815102139.A61413@wantadilla.lemis.com> In-Reply-To: <20010814192609.A44891@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Tue, Aug 14, 2001 at 07:26:09PM -0400 References: <20010814192609.A44891@blackhelicopters.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 14 August 2001 at 19:26:09 -0400, Michael Lucas wrote: > Before I start generating crash dumps & etc., are there any gotchas > with Vinum & -current? I'm using devfs on a SMP system, upgraded 3 > days ago. I get a panic whenever I stripe something. Ah, now you say devfs. There was a bug in devfs; I haven't checked whether it's been fixed. Basically, devfs as supplied in CURRENT had a 16 character limit on device names, and it didn't understand subdirectories: it treated the / as a part of the device name. Vinum device names can be much longer than 16 characters, so I changed the limit to 96 characters on my test machine, but wasn't able to get it to run reliably. I've told phk about this on IRC some months ago, but I haven't seen a commit fixing the problem. I could have missed something, of course. To help localize this problem, could you please try this same thing on a kernel without devfs? The dump you sent me did not look like a Vinum bug, as I said in my reply. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010815102139.A61413>