From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: ARAI Shun-ichi <hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Which version of nilfs do you use?
Date: Fri, 28 Dec 2012 10:14:49 +0400 [thread overview]
Message-ID: <1356675289.2126.10.camel@slavad-ubuntu> (raw)
In-Reply-To: <20121228.115843.568913897223506746.hermes-akuOmOme3sQYOdUovKs6ag@public.gmane.org>
On Fri, 2012-12-28 at 11:58 +0900, ARAI Shun-ichi wrote:
> In <BB9A0F28-A902-4FE4-BA58-A66EA93290F8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>;
> Elmer Zhang <freeboy6716-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote
> as Subject "Re: Which version of nilfs do you use?":
>
> > There is more than 2TB of data and a large number of databases, tables in our MySQL service. The conventional cold backup methods can not meet our needs. So we are trying to find some other methods.
>
> I posted report mail about the "bad btree node" error in 2012-11-30,
> I told about VirtualBox.
> When I met the error first, virtual disk file (approx. 16GB) was in
> NILFS FS.
>
> Zhang's DB is large. Perhaps there are files which has large size, I think.
> And these files are updated frequently.
>
> Can the common point (file size, update) cause inconsistency?
I think that it can be a synchronization issue. But it needs to
investigate the situation more deeply. As I can see, it is using 8 CPUs
in the case of the issue and it takes place frequent update. So, it can
be a ground for good issue reproducibility, from my point of view.
With the best regards,
Vyacheslav Dubeyko.
> --
> 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
--
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-28 6:14 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
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 [this message]
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=1356675289.2126.10.camel@slavad-ubuntu \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=hermes-akuOmOme3sQYOdUovKs6ag@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).