All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Kirk Anderson <kirkande@tx.rr.com>
Cc: xfs@oss.sgi.com
Subject: Re: Buffalo LS-Q4.0 Raid 5 XFS errors
Date: Thu, 29 Mar 2012 17:40:54 +1100	[thread overview]
Message-ID: <20120329064054.GP5091@dastard> (raw)
In-Reply-To: <004b01cd0d3f$c6d4fbc0$547ef340$@tx.rr.com>

On Wed, Mar 28, 2012 at 07:06:22PM -0500, Kirk Anderson wrote:
> I have a Buffalo LS-QLF55 4TB Raid 5 box.  It is out of warranty.  It was
> using firmware 1.10.    The unit stopped responding and would not power down
> through the web interface, nor the power button on the front of the unit.  I
> unplugged the unit and plugged it back in.  The unit now shows the drives as
> unformatted.  I have provided some information below and would greatly
> appreciate some guidance as to what my next steps are to minimize my data
> loss.  Any and all help is greatly appreciated.  Thanks, Kirk

No unformatted:

> XFS: log mount/recovery failed: error 117
> 
> XFS: log mount failed

Basically your filesystem was corrupted by the crash.

> Filesystem "md2": Disabling barriers, not supported by the underlying device
> 
> XFS mounting filesystem md2
> 
> Starting XFS recovery on filesystem: md2 (logdev: internal)
> 
> Filesystem "md2": xfs_inode_recover: Bad inode magic number, dino ptr =
> 0xc6d2c000, dino bp = 0xc782fa80, ino = 256
> 
> Filesystem "md2": XFS internal error xlog_recover_do_inode_trans(1) at line
> 2310 of file fs/xfs/xfs_log_recover.c.  Caller 0xc017f368
> 
> [<c002b758>] (dump_stack+0x0/0x14) from [<c01666fc>]
> (xfs_error_report+0x54/0x64)
> 
> [<c01666a8>] (xfs_error_report+0x0/0x64) from [<c017eb2c>]
> (xlog_recover_do_inode_trans+0x28c/0x8ac)
> 
> [<c017e8a0>] (xlog_recover_do_inode_trans+0x0/0x8ac) from [<c017f368>]
> (xlog_recover_do_trans+0x80/0x154)
> 
> [<c017f2e8>] (xlog_recover_do_trans+0x0/0x154) from [<c017f478>]
> (xlog_recover_commit_trans+0x3c/0x54)
> 
> [<c017f43c>] (xlog_recover_commit_trans+0x0/0x54) from [<c017f5f4>]
> (xlog_recover_process_data+0x164/0x224)
> 
> r7:c725e204 r6:c0b802d8 r5:08be0000 r4:e5000000
> 
> [<c017f490>] (xlog_recover_process_data+0x0/0x224) from [<c017f9b4>]
> (xlog_do_recovery_pass+0x300/0x828)
> 
> [<c017f6b4>] (xlog_do_recovery_pass+0x0/0x828) from [<c017ff54>]
> (xlog_do_log_recovery+0x78/0x9c)
> 
> [<c017fedc>] (xlog_do_log_recovery+0x0/0x9c) from [<c017ff98>]
> (xlog_do_recover+0x20/0x138)

And this is saying that there are no inodes where there are supposed
to be inodes.

The usual recovery via xfs_repair steps should be taken....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2012-03-29  6:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  0:06 Buffalo LS-Q4.0 Raid 5 XFS errors Kirk Anderson
2012-03-29  6:40 ` Dave Chinner [this message]
     [not found]   ` <002501cd0dbe$24be21c0$6e3a6540$@tx.rr.com>
2012-03-29 21:31     ` Dave Chinner
2012-03-29 22:15       ` Kirk Anderson
2012-03-29 23:03         ` Dave Chinner
2012-03-29 23:29           ` Kirk Anderson
2012-03-29 23:52             ` Dave Chinner
     [not found]               ` <005601cd0e11$c0b62d90$422288b0$@tx.rr.com>
2012-03-30  4:46                 ` Eric Sandeen

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=20120329064054.GP5091@dastard \
    --to=david@fromorbit.com \
    --cc=kirkande@tx.rr.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.