From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Elmer Zhang <freeboy6716-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Which version of nilfs do you use?
Date: Thu, 27 Dec 2012 11:35:13 +0100 [thread overview]
Message-ID: <1902997.ayblf9kj7g@coil> (raw)
In-Reply-To: <AAEC3976-3D79-4170-B1DC-2A04499392DE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Elmer,
On Thursday 27 of December 2012 17:47:34 you wrote:
> I am trying to use NILFS2 to make MySQL cold backup, but the MySQL tables
> often be crashed. It seems there is some problems with nilfs filesystem.
>
> I have described how I use nilfs in this mail:
> http://www.mail-archive.com/linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg01481.html
>
> Can I know which version of nilfs do you use, and what do you use nilfs for?
FWIW, I have MySQL installation on NILFS2 and it works just fine. The server
is only under light load, thou. MySQL version 5.5.27 (and 5.1.50 earlier on);
NILFS2 from kernel v3.0 and later, up to v3.5.
Perhaps your problems have something to do with MySQL recovery of data from
the cold backup? In MySQL Reference Manual chapter 7 -- Backup and Recovery
covers the subject.
If I'm reading your other email correctly, it seems you copied MyISAM files
without shutting MySQL down first. That's not supposed to be done with non-
transactional tables, AFAIK, and I'd suspect this as the main trouble source.
On the other hand, InnoDB tables should survive being copied from working
MySQL, as long as you observe correct order of (table, log files) copying --
not sure which goes first, it's in the docs.
Cheers,
--
dexen deVries
[[[↓][→]]]
Reality is just a convenient measure of complexity.
-- Alvy Ray Smith
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-12-27 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 9:47 Which version of nilfs do you use? Elmer Zhang
[not found] ` <AAEC3976-3D79-4170-B1DC-2A04499392DE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-27 10:35 ` dexen deVries [this message]
2012-12-28 2:20 ` Elmer Zhang
[not found] ` <BB9A0F28-A902-4FE4-BA58-A66EA93290F8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-28 2:58 ` ARAI Shun-ichi
[not found] ` <20121228.115843.568913897223506746.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2012-12-28 6:14 ` Vyacheslav Dubeyko
2012-12-28 7:58 ` ARAI Shun-ichi
[not found] ` <20121228.165816.981117143166927771.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
2012-12-28 8:17 ` Vyacheslav Dubeyko
2012-12-28 6:06 ` Vyacheslav Dubeyko
2012-12-28 7:12 ` Elmer Zhang
[not found] ` <948BD9D2-CAF2-444D-A23B-00D689BA69CE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-28 7:33 ` Vyacheslav Dubeyko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1902997.ayblf9kj7g@coil \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=freeboy6716-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).