All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Stor?? <289471341@qq.com>, Jeff Liu <jeff.liu@oracle.com>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: 回复： 【xfs_metadump   xfs_mdrestore  xfsdump  xfsrestore】
Date: Tue, 17 Dec 2013 11:29:47 -0600	[thread overview]
Message-ID: <20131217172946.GU1935@sgi.com> (raw)
In-Reply-To: <52B005A6.9050704@oracle.com>

Hey,

On Tue, Dec 17, 2013 at 04:04:54PM +0800, Jeff Liu wrote:
> On 12/17 2013 15:45 PM, Stor?? wrote:
> >  
> >  thank you.
> > 1.  XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1676 of file
> > fs/xfs/xfs_alloc.c.  Caller 0xffffffffa023496d

http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=blob;f=fs/xfs/xfs_alloc.c;h=1956f83489f1b8378f4459844e422547d421e0ec;hb=1f4c79cdb3fd856edde28af25576bcd8341eef78#l1676

We were trying to remove an entry in the by-size freespace btree and found that
the entry to the right was not there as expected.

> > Pid: 7579, comm: smbd Tainted: G          2.6.27.19-5-default #7
> > Call Trace:
> >  [<ffffffff8020d899>] show_trace_log_lvl+0x41/0x58
> >  [<ffffffff8020deff>] dump_stack+0x69/0x6f
> >  [<ffffffffa023308f>] xfs_free_ag_extent+0x45a/0x6bb [xfs]
> >  [<ffffffffa023496d>] xfs_free_extent+0xa9/0xc9 [xfs]
> >  [<ffffffffa023d446>] xfs_bmap_finish+0xee/0x15f [xfs]
> >  [<ffffffffa025d647>] xfs_itruncate_finish+0x190/0x2ba [xfs]
> >  [<ffffffffa027626d>] xfs_inactive+0x216/0x450 [xfs]
> >  [<ffffffffa0280e01>] xfs_fs_clear_inode+0xb0/0xf4 [xfs]
> >  [<ffffffff802bca41>] clear_inode+0x75/0xcc
> >  [<ffffffff802bcbb5>] generic_delete_inode+0xd6/0x14e
> >  [<ffffffff802b476f>] do_unlinkat+0xda/0x14d
> >  [<ffffffff8020befb>] system_call_fastpath+0x16/0x1b
> >  [<00007f6af6256b77>] 0x7f6af6256b77
> > xfs_force_shutdown(dm-1,0x8) called from line 4269 of file
> > fs/xfs/xfs_bmap.c.  Return address = 0xffffffffa023d47b
> > Filesystem "dm-1": Corruption of in-memory data detected.  Shutting down
> > filesystem: dm-1
> > Please umount the filesystem, and rectify the problem(s)
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> > Filesystem "dm-1": xfs_log_force: error 5 returned.
> >  
> > Why is this so,
> > In order to protect the data.Which command with the backup file system.
> > xfs_dump or xfs_metadump.
> xfsdump.  This looks like an internal corruptions, maybe run xfs_repair
> -n can give more hints.

In addition to the xfs_repair -n output, a metadump might also be helpful.

Regards,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2013-12-17 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  6:46 =?gb18030?B?ob54ZnNfbWV0YWR1bXAgICB4ZnNfbWRyZXN0b3JlICB4ZnNkdW1wICB4ZnNyZXN0b3Jlob8=?= =?gb18030?B?U3Rvcj8/?=
2013-12-17  7:25 ` 【xfs_metadump xfs_mdrestore xfsdump xfsrestore】 Jeff Liu
2013-12-17  7:45   ` 回复： " Stor??
2013-12-17  8:04     ` Jeff Liu
2013-12-17 17:29       ` Ben Myers [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=20131217172946.GU1935@sgi.com \
    --to=bpm@sgi.com \
    --cc=289471341@qq.com \
    --cc=jeff.liu@oracle.com \
    --cc=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.