Gabriel,

----- Original Message ----- 
From: "Gabriel Ricard" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, October 27, 2003 6:46 PM
Subject: InnoDB on Raw partitions in OSX (was Re: MySQL/InnoDB-4.0.16 is
released + sneak peek of 4.1.1)

> On Monday, October 27, 2003, at 07:45  AM, Chris Nolan wrote:
>
> > 2. I personally use ReiserFS for all of my stuff, most of which is
> > based upon InnoDB. One thing you have to remember is that InnoDB
> > treats the space inside the tablespace as a Berkeley Fast
> > Filesystem-style space, using the underlaying filesystem minimally. To
> > quote
> > the manuals, raw partition usage can speed up IO on a number of UNIXes
> > (and Windows too seemingly). Regarding backup, you'd
> > need to use mysqldump or InnoDB Hot Backup to backup a raw-partition
> > setup. This isn't a bad thing though - I use mysqldump and
> > can get a consistant snapshot of a 12 GB DB without problems while the
> > thing is running.
>
> Just out of curiosity, has anyone been able to get InnoDB to use a raw
> partition in OSX? When I tried it, it complained about the file already
> existing.

did you add the newraw keyword?

http://www.innodb.com/ibman.html#Disk_io_and_raw_devices

"
12.1 Disk i/o and raw devices

Starting from 3.23.41, you can also use a raw disk partition (a raw device)
as a data file. When you create a new data file you have to put the keyword
newraw immediately after the data file size in innodb_data_file_path. The
partition must be equal to or larger than the size you specify. Note that 1M
in InnoDB is 1024 x 1024 bytes, while in disk specifications 1 MB usually
means 1000 000 bytes.

innodb_data_home_dir=
innodb_data_file_path=/dev/hdd1:3Gnewraw;/dev/hdd2:2Gnewraw

When you start the database again you MUST change the keyword to raw.
Otherwise InnoDB will write over your partition! Starting from 3.23.44, as a
safety measure InnoDB prevents a user from modifying data when any partition
with newraw is specified. After you have added a new partition, shut down
the database, edit my.cnf replacing newraw with raw, and restart.

innodb_data_home_dir=
innodb_data_file_path=/dev/hdd1:3Graw;/dev/hdd2:2Graw

By using a raw disk you can on Windows and on some Unixes perform
non-buffered i/o.
In Windows raw disk i/o, starting from 4.1.1, you can allocate a disk
partition as a data file like this:
innodb_data_home_dir=
innodb_data_file_path=//./D::10Gnewraw
"

> - Gabriel

Best regards,

Heikki Tuuri
Innobase Oy
http://www.innodb.com
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - hot backup tool for InnoDB which also backs up MyISAM
tables



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to