At 15:08 Uhr +0100 19.7.2001, Peter Duffy wrote:
>database table sql query
>I guess that it's thinking the tablespace is already initialised.
Yes, probably: it's the same if you have an ibdata file and no log
files and start mysql-innodb. I've noticed this while setting up
innodb with filesyste
database table sql query
OK, here's where I've got to.
1) After fiddling about with fdisk, disk geometry and kernel boot parms,
I've managed to define a partition which
appears to lseek as exactly 1000M (this was fairly horrible: if anyone
wants to replicate this step, I'll go over the process,
Christian Jaeger wrote:
>
> Just to the record: I've written a small program too, and it reports
> correct sizes for normal disk devices under both linux 2.2 and 2.4,
> as long as the partition sizes don't exceed the 2GB limit (I don't
> have large file support, since I use debian potato with jus
database,sql,query,table
Just to the record: I've written a small program too, and it reports
correct sizes for normal disk devices under both linux 2.2 and 2.4,
as long as the partition sizes don't exceed the 2GB limit (I don't
have large file support, since I use debian potato with just the
s,
Heikki
http://www.innodb.com
-Original Message-
From: Peter Duffy <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Date: Tuesday, July 17, 2001 8:27 PM
Subject: Re: innodb and raw disks
>Hi Heikki,
>
>You mean lseek? As far as I'm aware, fseek doesn
fdisk /dev/hdd and set up partition 1.
Then try using hdd1.
Peter Duffy wrote:
> Hi,
>
> In the InnoDB section of the MySQL manual, it mentions that InnoDB can
> be used with raw disks, rather than data files. I've been trying to get
> this to work under Linux (RedHat 6.2), but so far without
Hi,
In the InnoDB section of the MySQL manual, it mentions that InnoDB can
be used with raw disks, rather than data files. I've been trying to get
this to work under Linux (RedHat 6.2), but so far without success.
I installed a new slave disk on the second IDE bus, brought up the
system and veri
