From owner-freebsd-questions Tue Feb 5 11: 0:49 2002 Delivered-To: freebsd-questions@freebsd.org Received: from bfd.com (bfd.com [209.12.133.10]) by hub.freebsd.org (Postfix) with ESMTP id 2177F37B428 for ; Tue, 5 Feb 2002 11:00:40 -0800 (PST) Received: from HARLIE.bfd.com (HARLIE.bfd.com [192.168.1.10]) by bfd.com (8.11.1/8.11.1) with ESMTP id g15J0Yu18209 for ; Tue, 5 Feb 2002 11:00:34 -0800 (PST) Date: Tue, 5 Feb 2002 11:00:29 -0800 (PST) From: "Eric J. Schwertfeger" To: freebsd-questions@freebsd.org Subject: Using raw slices with InnoDB/MySQL? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm playing around with a new database server in the office before it goes live, and one thing I wanted to try was to use a raw disk slice as the storage area for MySQL/InnoDB tables. I've got a slice that was set up, and at one time even newfs'ed and mounted, but is no longer in use, /dev/da1s1e. Whenever anyone tries to write to the slice, including root, I get a readonly file error. Since the slice works fine if I newfs and mount it, I'm pretty sure that this is some kind of protection that FreeBSD enforces keeping filesystems from getting wiped. Can anyone tell me what I'm tripping over? I searched the handbook and the FAQ, and didn't find anything. As a side note, the InnoDB/MySQL combination allows for database files larger than 4GB on "some operating systems" but the InnoDB/MySQL docs don't mention which features are needed. Any FreeBSD MySQL users out there have the answer to this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message