Dan,
I see. My automake/autoconf script currently checks if there
exists fdatasync, and if not then it uses fsync. So we know
now that it calls fsync. I wrote to Steve and asked him to compile
a version where he sees the error number from fsync.
Thank you for the FreeBSD info.
Heikki
-----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 (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 call f(data)sync at all, but then you may have to run
>> repair if it crashes.
>>
>> I looked at FreeBSD manuals at www.freebsd.org and did not find any
>> notice that fdatasync would not work for NFS. Presumably with some
>> settings it should work, or maybe there is a bug in the OS/hardware
>> combination.
>
>fsync (FreeBSD doesn't have fdatasync) definitely does work with NFS.
>Knowing the errno that fsync() returned when it failed might help the
>debugging process, though.
>
>--
> Dan Nelson
> [EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
