public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Robert <xiaguowu2004@sina.com>
Cc: xfs@oss.sgi.com
Subject: Re: linux xfs filesystem corruption
Date: Mon, 28 Jul 2008 21:47:01 -0500	[thread overview]
Message-ID: <488E84A5.6040409@sandeen.net> (raw)
In-Reply-To: <010901c8f11f$9a9a68f0$3400a8c0@xgw>

Robert wrote:
> Dear all,
>       I have encoutered linux xfs filesystem corruption, I search this topic 
> on the
> web, but I can't find any useful information to fix my problem.
>       I build a raid5 with 'mdadm' on my own embeded system which is based 
> on
> arm, and format it with 'mkfs.xfs',  mount it to a directory to be set for 
> nfs
> share. On the host side, I mount the raid, and start writing data to this 
> raid,  for
> about 20hours later, I start to delete the data , but the following message 
> shows:
> 
> XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1610 of file
> fs/xfs/xfs_alloc.c, xfs_force_shutdown(md0,0x8) called from line 4073 of 
> file fs/xfs/xfs_bmap.c
> Filesystem "md0" corruption of in-memory data detected. Shutting down
> filesystem.Please umount the filesystem and rectify the problem.

arm has been problematic on several fronts.  The first was with the v2
directory code...

http://oss.sgi.com/archives/xfs/2008-06/msg00064.html

but that doesn't appear to be what you are hitting.  There have been
other problems with cache flushing that I don't remember all the details
of now ...


>      Although the filesystem crashed, the system did not hang. So I cd to 
> this directory,
> and ls, and find that all the data seems to be lost,  but 'df' reports that 
> the most of
> raid has been used, I try to repair it with xfs_repair, and everything is 
> OK.
>      But now I don't want to fix this problem by xfs_repair, if the problem 
> happens again,

and what did xfs_repair find?  Do you have a record of it?

> I have to reparit it again, it's too trouble, so if there is any way to 
> solve this prolbem?
> I want to find out what causes this error happend,
>    Anybody has experience in this problem?
>    The following is my system parameter:
>   linux version: 2.6.12.6

any other patches applied?  Can you try again with a more recent kernel?

-Eric

>   CPU: arm926ej
>   memory: 128M
>   If you answer this question ,Could you please cc to me? I didn't subscribe 
> this mailing list.
>  Thanks in advance!
> 
>  Robert 
> 
> 
> 

  reply	other threads:[~2008-07-29  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  2:05 linux xfs filesystem corruption Robert
2008-07-29  2:47 ` Eric Sandeen [this message]
2008-07-29  5:57   ` Robert
2008-07-29 18:52 ` Russell Cattelan

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=488E84A5.6040409@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    --cc=xiaguowu2004@sina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox