linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Elmer Zhang <freeboy6716-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org,
	"linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Which version of nilfs do you use?
Date: Fri, 28 Dec 2012 11:33:07 +0400	[thread overview]
Message-ID: <1356679987.2126.17.camel@slavad-ubuntu> (raw)
In-Reply-To: <948BD9D2-CAF2-444D-A23B-00D689BA69CE-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri, 2012-12-28 at 15:12 +0800, Elmer Zhang wrote:
> Hi,
> 
> There was three bad btree nodes:
> 
> Dec 20 16:12:08 yf237 kernel: NILFS: bad btree node (blocknr=710153406): level = 0, flags = 0x2, nchildren = 25088
> Dec 20 16:12:08 yf237 kernel: NILFS error (device sdb2): nilfs_bmap_last_key: broken bmap (inode number=321775)
> --
> Dec 21 10:10:07 yf237 kernel: NILFS: bad btree node (blocknr=711343917): level = 199, flags = 0x60, nchildren = 16670
> Dec 21 10:10:07 yf237 kernel: NILFS error (device sdb2): nilfs_bmap_last_key: broken bmap (inode number=324685)
> --
> Dec 21 10:13:41 yf237 kernel: NILFS: bad btree node (blocknr=14167806): level = 0, flags = 0x0, nchildren = 0
> Dec 21 10:13:41 yf237 kernel: NILFS error (device sdb2): nilfs_bmap_last_key: broken bmap (inode number=253710)
> 

I think that it makes sense to investigate dumps of the segments that
contains these blocks. Could you make dumps of #346754, #347335, #6917
segments and send only on my personal e-mail for analysis?

Example:

dd if=<device> of=<file> bs=4096 skip=710152192 count=2048

(710152192 == 346754 * 2048)

With the best regards,
Vyacheslav Dubeyko.

> I have not found new bad btree nodes in recent days. But the MyISAM tables still often be crashed and soon be ok without repairing.
> 
> 
> 在 2012-12-28,14:06,Vyacheslav Dubeyko <slava@dubeyko.com> 写道:
> 
> > Hi,
> > 
> > On Thu, 2012-12-27 at 17:47 +0800, Elmer Zhang wrote:
> >> Hi konishi ryusuke,
> >> 
> >> 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.
> >> 
> > 
> > As I remember, you reported initially the error message about issue with
> > (inode number=321775) and (blocknr=710153406). If you have new MySQL
> > tables' crashes then it means that you have new NILFS error messages in
> > your syslog. Do you have error messages about new inode numbers and
> > block numbers or about the same?
> > 
> > With the best regards,
> > Vyacheslav Dubeyko.
> > 
> >> 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?
> >> 
> >> Thanks,
> >> Elmer Zhang--
> >> 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


--
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

      parent reply	other threads:[~2012-12-28  7:33 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
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 [this message]

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=1356679987.2126.17.camel@slavad-ubuntu \
    --to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
    --cc=freeboy6716-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@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).