From: Reinoud Zandijk <reinoud-qavaossjCcEdnm+yROfE0A@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Broken nilfs2 filesystem
Date: Thu, 6 Jun 2013 11:20:54 +0200 [thread overview]
Message-ID: <20130606092054.GA201@diablo.13thmonkey.org> (raw)
In-Reply-To: <1370501769.2202.36.camel@slavad-ubuntu>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Hi,
just my $0.02 so to say:
On Thu, Jun 06, 2013 at 10:56:09AM +0400, Vyacheslav Dubeyko wrote:
> First of all, unfortunately, I can't reproduce the issue yet, currently.
> I suspect that in this issue the aging state of volume, peculiarity of
> workload and environment play very important role. As I remember, all
> reporters of likewise symptoms (broken bnode error messages) talked
> about several months of successful working of NILFS2 file system.
sounds to me as if a b-tree is in a perculiar state and that updating the
btree results in this corruption.
Have you tried to mount one of the checkpoints/snapshots earlier as RO and see
if those are correct? If so, dumping both DATs and both btrees might give a
clue as to what went wrong. If only it gives a clue as to how complicated the
btree is before the updating and what actions are taken on it.
With regards,
Reinoud
[-- Attachment #2: Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2013-06-06 9:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 20:33 Broken nilfs2 filesystem Anton Eliasson
[not found] ` <519D2B96.9000106-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-22 20:36 ` Anton Eliasson
[not found] ` <519D2C32.5040600-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-23 1:40 ` Ryusuke Konishi
2013-05-23 6:44 ` Vyacheslav Dubeyko
2013-05-25 11:59 ` Anton Eliasson
[not found] ` <51A0A7A0.6010207-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-25 16:26 ` Anton Eliasson
[not found] ` <51A0E62D.5060600-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-26 12:54 ` Vyacheslav Dubeyko
2013-05-29 6:39 ` Vyacheslav Dubeyko
2013-05-29 14:37 ` Ryusuke Konishi
[not found] ` <20130529.233757.27789741.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-05-30 6:13 ` Vyacheslav Dubeyko
2013-05-30 6:55 ` Ryusuke Konishi
[not found] ` <20130530.155543.480320022.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-05-30 7:21 ` Vyacheslav Dubeyko
2013-06-06 6:56 ` Vyacheslav Dubeyko
2013-06-06 9:20 ` Reinoud Zandijk [this message]
[not found] ` <20130606092054.GA201-HNv6YvNvQKMNqjISwOrxaLFspR4gePGN@public.gmane.org>
2013-06-06 9:34 ` Vyacheslav Dubeyko
2013-06-06 14:19 ` Reinoud Zandijk
2013-06-12 20:12 ` Anton Eliasson
2013-06-12 20:31 ` Anton Eliasson
[not found] ` <51B8DA8E.6020802-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-06-13 10:01 ` Vyacheslav Dubeyko
2013-05-30 8:10 ` Anton Eliasson
[not found] ` <51A70971.40602-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-30 15:30 ` Anton Eliasson
[not found] ` <51A770A8.9070105-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-30 20:50 ` Anton Eliasson
[not found] ` <51A7BB84.3010505-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-31 6:39 ` Vyacheslav Dubeyko
[not found] <51A0A97A.4020503@antoneliasson.se>
[not found] ` <713B7146-DC0C-45AE-9ED2-30EB8F84FA57@dubeyko.com>
[not found] ` <713B7146-DC0C-45AE-9ED2-30EB8F84FA57-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-05-27 12:45 ` Anton Eliasson
[not found] ` <51A35558.1080503-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-05-27 13:23 ` Vyacheslav Dubeyko
[not found] <51F2A8A4.4020400@antoneliasson.se>
2013-07-26 16:52 ` Fwd: " Anton Eliasson
[not found] ` <51F2A945.6050909-17Olwe7vw2dLC78zk6coLg@public.gmane.org>
2013-07-27 16:23 ` Vyacheslav Dubeyko
[not found] ` <9016EBD5-1E01-476F-B1B9-66AE593F4728-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-07-27 22:32 ` Anton Eliasson
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=20130606092054.GA201@diablo.13thmonkey.org \
--to=reinoud-qavaossjccednm+yrofe0a@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slava-yeENwD64cLxBDgjK7y7TUQ@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