Date: Tue, 5 Feb 2002 13:51:49 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: "Eric J. Schwertfeger" <ejs@bfd.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Using raw slices with InnoDB/MySQL? Message-ID: <20020205195149.GJ12749@dan.emsphone.com> In-Reply-To: <Pine.BSF.4.21.0202050924260.98824-100000@harlie.bfd.com> References: <Pine.BSF.4.21.0202050924260.98824-100000@harlie.bfd.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Feb 05), Eric J. Schwertfeger said: > 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. A raw device will go readonly if you have a filesystem mounted on it, or if your securelevel is 1 or higher. Or if your disk is jumpered read-only :) > 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? InnoDB on FreeBSD should be able to go over 4gb with no problems (FreeBSD has always had 64-bit file offsets). -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020205195149.GJ12749>