public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: kevin.dual@gmail.com
Cc: xfs@oss.sgi.com
Subject: Re: Power loss causes bad magic number??
Date: Sat, 07 Feb 2009 15:54:11 -0600	[thread overview]
Message-ID: <498E0303.5000204@sandeen.net> (raw)
In-Reply-To: <498DF8AD.3020903@sandeen.net>

Eric Sandeen wrote:

> Dunno how much damage could have been done, or if you can just try to
> fix the assembly perhaps...?
> 
> -Eric

FWIW on a 3-disk raid5:

[root@inode tmp]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 loop3[2] loop2[1] loop1[0]
      262016 blocks level 5, 4k chunk, algorithm 2 [3/3] [UUU]

unused devices: <none>

it's the 0th device which should have the superblock:

[root@inode tmp]# file -s /dev/loop[123]
/dev/loop1: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
/dev/loop2: data
/dev/loop3: data

whereas yours was the 1st (not 0th)

(I wasn't sure how mdstat showed the order so double checked...)

-Eric

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

  reply	other threads:[~2009-02-07 22:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  2:18 Power loss causes bad magic number?? Stephen Porter
2008-07-16  2:40 ` Eric Sandeen
2008-07-16  7:01   ` Stephen Porter
2008-07-16  7:35     ` Dave Chinner
2008-07-16  8:17       ` Stephen Porter
2008-07-16 16:00         ` Chris Wedgwood
2008-07-17 13:36         ` Russell Cattelan
2008-07-17 21:52           ` Stephen Porter
2008-07-18 11:17             ` Andi Kleen
2008-07-18 18:19         ` Peter Grandi
2009-02-07 20:46 ` kevin.dual
2009-02-07 21:10   ` Eric Sandeen
2009-02-07 21:54     ` Eric Sandeen [this message]
2009-02-08  6:10     ` Kevin Dual

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=498E0303.5000204@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=kevin.dual@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox