[mylvmbackup] Re: File Descriptors Left Open

Hi, Matthew

One of the benefits of using innodb is that it doesn't have to be
flushed like myisam does. The flushing that mylvmbackup does is only
for synchronization of replication and myisam tables. The only way to
get innodb to close it's files is to shutdown mysql but that sort of
defeats the purpose of mysqllvmbackup. If you're only using innodb and
no replication you can take a lvm snapshot with no synchronization
with mysql.

-Eric

On Mon, Feb 9, 2009 at 8:05 AM, Boehm, Matthew <mboehm@xxxxxxxxxxxxx> wrote:
> Hey all,
>
>  Been using mylvmbackup in production environment across about 50 MySQL
> servers for past several months with no hiccups. Excellent program. One
> thing that bothers me is that we see this "error":
>
>
>
> File descriptor 3 left open
>
>
>
> What I can only guess this comes from is the InnoDB datafile or log files
> because InnoDB doesn't actually do the flushing like MyISAM does.
>
>
>
> Is there any way to have InnoDB properly close/let go of its open files
> before doing the snapshot?
>
>
>
> -Matthew
>
>
>
> Matthew Boehm
>
> Senior MySQL DBA, The Planet – Northstar Managed Hosting
>
> Certified MySQL 5.0 DBA
>
> Certified MySQL 5.1 Cluster DBA
>
> Office: 281-714-4018
>
> Mobile: 832-253-8258
>
> Email: mboehm@xxxxxxxxxxxxx
>
>



-- 
high performance mysql consulting.
http://provenscaling.com

Other related posts: