Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
O_DIRECT warnings & can I trust "innobackupex: completed OK!" message?
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Xavier  
View profile  
 More options Oct 7 2011, 11:23 am
From: Xavier <xssn...@gmail.com>
Date: Fri, 7 Oct 2011 08:23:38 -0700 (PDT)
Local: Fri, Oct 7 2011 11:23 am
Subject: O_DIRECT warnings & can I trust "innobackupex: completed OK!" message?

Good morning,

I have a gluster 3.2 filesystem I'm using for storage, mounted using the
gluster native mount (as opposed to nfs) for performance, and I'm perfoming
backups of a mysql-5.5.15-linux2.6-x86_64 server on Fedora release 10 with
innobackupex (InnoDB Backup Utility v1.5.1-xtrabackup) as described in the
Percona documentation. I get tons of these messages printed for both full
backup and prepare stages:

111006 17:01:31 InnoDB: Failed to set O_DIRECT on file
./myPorkyDB/myPorkyTable.ibd: OPEN: Invalid argument, continuing anyway
111006 17:01:31 InnoDB: O_DIRECT is known to result in 'Invalid argument' on
Linux on tmpfs, see MySQL Bug#26662

A little later on in each process I get:

111006 17:01:35 innobackupex: completed OK!

Does this mean that the backup succeeded irrespective of the messages
regarding the failure to set O_DIRECT since it was able to complete the
backup by "continuing anyway"?

Thank you for your time,
X.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Steven Ayre  
View profile  
 More options Oct 7 2011, 11:41 am
From: Steven Ayre <stevea...@gmail.com>
Date: Fri, 7 Oct 2011 16:41:53 +0100
Local: Fri, Oct 7 2011 11:41 am
Subject: Re: O_DIRECT warnings & can I trust "innobackupex: completed OK!" message?
I'm a not one of the developers, but AFAIK the O_DIRECT is only to
disable caching the read data since the copy will not go back over
data it has already copied so it's better not to add it to the cache.
I don't think it'll cause a problem.

-Steve

On 7 October 2011 16:23, Xavier <xssn...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Alexey Kopytov  
View profile  
 More options Oct 11 2011, 8:01 am
From: Alexey Kopytov <akopy...@gmail.com>
Date: Tue, 11 Oct 2011 16:01:43 +0400
Local: Tues, Oct 11 2011 8:01 am
Subject: Re: O_DIRECT warnings & can I trust "innobackupex: completed OK!" message?
Hi Xavier,

On 07.10.11 19:23, Xavier wrote:

The message is more a warning than an error. Apparently O_DIRECT is not
supported by gluster. So InnoDB first tries to use it, and falls back to
a buffered IO if that fails.

So yes, you can ignore those messages.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »