replacement for mysqldump --all-databases

[sjau]

the first is normal... not sure about the second one. Running out of diskspace? is tht db damaged?

[Ovidiu]

the second might be a hardware problem. just did a hardware test through my provider and they are going to replace some hardware.

why would the first one be normal? I read that the information schema shouldn't be dumped by default anyway !?

Does this mean the first error doesn't affect my backups?

i.e.

mysqldump does not dump the INFORMATION_SCHEMA database by default. As of MySQL 5.1.38, mysqldump dumps INFORMATION_SCHEMA if you name it explicitly on the command line, although currently you must also use the --skip-lock-tables option. Before 5.1.38, mysqldump silently ignores INFORMATION_SCHEMA even if you name it explicitly on the command line.

[sjau]

the command looks up all databases including the INFORMATION_SCHEMA and tries to dump it.

You see, first is an command issued that build a list of the dbs in mysql and then it loops through that list and dumps each one to an own .sql file.

[sjau]

the command looks up all databases including the INFORMATION_SCHEMA and tries to dump it.

You see, first is an command issued that build a list of the dbs in mysql and then it loops through that list and dumps each one to an own .sql file.

[eyeoncomputers]

this is a little shifty but...you may be able to do an ls of /var/lib/mysql and scoop up the dbs in there, and exclude the ones you don't want, but include everything else.