All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: CAI Qian <caiqian@redhat.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: 3.9.0: XFS rootfs corruption
Date: Wed, 22 May 2013 19:46:48 +1000	[thread overview]
Message-ID: <20130522094648.GJ29466@dastard> (raw)
In-Reply-To: <2013798179.4502334.1369212536770.JavaMail.root@redhat.com>

On Wed, May 22, 2013 at 04:48:56AM -0400, CAI Qian wrote:
> 
> 
> ----- Original Message -----
> > From: "CAI Qian" <caiqian@redhat.com>
> > To: "Eric Sandeen" <sandeen@sandeen.net>
> > Cc: xfs@oss.sgi.com
> > Sent: Wednesday, May 22, 2013 12:10:07 PM
> > Subject: Re: 3.9.0: XFS rootfs corruption
> > 
> > OK, this has never been reproduced in 3.9-rc1 so far. It may because the
> > rootfs became full after crash dump testing though.
> > CAI Qian
> Oops, it is still there,

Have you run xfs_repair -n  <dev>  to determine what is corrupted on
disk? Can you post the output when you do?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2013-05-22  9:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2105365384.7582278.1367825507929.JavaMail.root@redhat.com>
2013-05-06  7:50 ` 3.9.0: XFS rootfs corruption CAI Qian
2013-05-06 14:31   ` Eric Sandeen
2013-05-07  7:53     ` CAI Qian
2013-05-07 19:08       ` Eric Sandeen
2013-05-14  2:28         ` CAI Qian
2013-05-14  3:17           ` Dave Chinner
2013-05-22  4:10         ` CAI Qian
2013-05-22  8:48           ` CAI Qian
2013-05-22  9:46             ` Dave Chinner [this message]
2013-06-03  7:44               ` CAI Qian
2013-06-03  8:09         ` CAI Qian
2013-06-04  4:36           ` Dave Chinner
2013-06-04  4:48             ` CAI Qian
2013-06-04  5:02             ` CAI Qian

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=20130522094648.GJ29466@dastard \
    --to=david@fromorbit.com \
    --cc=caiqian@redhat.com \
    --cc=sandeen@sandeen.net \
    --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.