From owner-freebsd-bugs Wed Jun 7 1:10:53 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from eel.radicalmedia.com (eel.radicalmedia.com [204.254.246.9]) by hub.freebsd.org (Postfix) with ESMTP id 99EBE37B7F1; Wed, 7 Jun 2000 01:10:43 -0700 (PDT) (envelope-from phiber@eel.radicalmedia.com) Received: (from phiber@localhost) by eel.radicalmedia.com (8.9.3/8.9.3) id EAA04971; Wed, 7 Jun 2000 04:10:37 -0400 (EDT) Date: Wed, 7 Jun 2000 04:10:36 -0400 From: Mark Abene To: gnats-admin@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/19086: pseudo-device vn doesn't work properly with msdos filesystems Message-ID: <20000607041036.A4164@radicalmedia.com> References: <20000607070057.6C64437B8C4@hub.freebsd.org> <200006070710.AAA41125@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <200006070710.AAA41125@freefall.freebsd.org>; from gnats-admin@FreeBSD.org on Wed, Jun 07, 2000 at 12:10:05AM -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just did some poking around, and the problem is *not* with the vn driver at all, but the msdosfs driver. I just tried mounting a dos floppy and tried to read/write it, and ran into the exact same problem with "Argument list too long". I have MSDOSFS compiled into the kernel. Unfortunately, I don't have 4.0-RELEASE on any Intel boxes, only Alpha. I can verify that this problem doesn't exist with 3.4-RELEASE on Intel. -Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message