From: Reinoud Zandijk <reinoud-qavaossjCcEdnm+yROfE0A@public.gmane.org>
To: Kenneth Langga <klangga-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: NILFS: bad btree node
Date: Fri, 25 May 2012 20:06:49 +0200 [thread overview]
Message-ID: <20120525180649.GA1236@heethoofdje.13thmonkey.org> (raw)
In-Reply-To: <CAHmELnWvFNdiePs=mQJ=nqfsxJ_49zxawa9jncE-RJ2-omYHOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Kenneth.
On Fri, May 25, 2012 at 10:30:40PM +0800, Kenneth Langga wrote:
> NILFS: bad btree node (blocknr=111560943): level = 242, flags = 0x3f,
> nchildren = 23369
> NILFS error (device sdc2): nilfs_bmap_lookup_contig: broken bmap
> (inode number=19696)
>
> What is the correct course of action for this type of error? And what
> would have caused this?
What struck me is the very high level and the absurt number of number of
children. That can't be good. AFAIR NiLFS only has say upto 3 (or 4?) levels
in its B-tree. It *could* be failing in rebalancing or more likely pointing to
garbage?
Cheers,
Reinoud
--
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-05-25 18:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 14:30 NILFS: bad btree node Kenneth Langga
[not found] ` <CAHmELnWvFNdiePs=mQJ=nqfsxJ_49zxawa9jncE-RJ2-omYHOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-25 18:06 ` Reinoud Zandijk [this message]
[not found] ` <20120525180649.GA1236-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2012-05-25 18:15 ` Kenneth Langga
[not found] ` <CAHmELnVyRNGn1gda0Sw53YCSOAYMm5JUonebi-9NxaFBP7Uidw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-26 14:49 ` Christian Smith
[not found] ` <20120526144932.GG18110-Ng8wz+J301SNY5Lh21HnMTHS2PGA244I9dF7HbQ/qKg@public.gmane.org>
2012-05-26 16:43 ` Kenneth Langga
-- strict thread matches above, loose matches on Subject: below --
2012-12-20 2:46 张 磊
[not found] ` <86B5C141-ACFA-4541-999F-E17E09F22476-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-20 6:08 ` Vyacheslav Dubeyko
2012-12-20 9:08 ` 张 磊
[not found] ` <3455B0CD-EF89-4227-90E1-FC6B20F5F8EB-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-20 9:38 ` Vyacheslav Dubeyko
2012-12-20 10:16 ` 张 磊
[not found] ` <14BA4286-BF21-4BD3-8E41-2F8F9512D801-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-20 10:41 ` Vyacheslav Dubeyko
2012-12-20 11:02 ` 张 磊
[not found] ` <44056E9A-3487-4E8A-A56A-5B9228FC7895-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-25 6:02 ` Vyacheslav Dubeyko
2012-12-25 7:10 ` Elmer Zhang
2012-12-22 14:12 ` Seiji Kihara
[not found] ` <50D5BFD6.1080502-sG5X7nlA6pw@public.gmane.org>
2012-12-24 3:04 ` 张 磊
2012-12-27 10:43 ` 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=20120525180649.GA1236@heethoofdje.13thmonkey.org \
--to=reinoud-qavaossjccednm+yrofe0a@public.gmane.org \
--cc=klangga-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).