age-
> From: Dan Nelson [mailto:[EMAIL PROTECTED]]
> Sent: 15 June, 2001 19:58
> To: Heikki Tuuri
> Cc: [EMAIL PROTECTED]
> Subject: Re: mysql died with innodb
>
>
> *This message was transferred with a trial version of
> CommuniGate(tm) Pro*
> In the last ep
-Original Message-
From: Dan Nelson <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date: Friday, June 15, 2001 9:27 PM
Subject: Re: mysql died with innodb
>In the last episode
In the last episode (Jun 15), Heikki Tuuri said:
> of course InnoDB could catch the error and send the error message to
> the client. But the problem is that we have to get NFS to flush the
> files, otherwise we may very easily get database corruption in case
> of a crash.
>
> MyISAM does not cal
<[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, June 15, 2001 8:57 PM
Subject: Re: mysql died with innodb
>In the last episode (Jun 15), Heikki Tuuri said:
>> Sven,
>>
>> line 637 in m
In the last episode (Jun 15), Heikki Tuuri said:
> Sven,
>
> line 637 in mysql/innobase/os/os0file.c asserts that
>
> TRUE == os_file_flush(file)
>
> If you look at about line 557, you see how InnoDB does
> the file flush: the default is to call fdatasync.
>
> To solve the problem we should loo
