public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: gbakos@cfa.harvard.edu
Cc: linux-xfs@oss.sgi.com
Subject: Re: unexpected XFS SB magic number
Date: Fri, 22 Dec 2006 17:33:06 -0600	[thread overview]
Message-ID: <458C6B32.5090004@sandeen.net> (raw)
In-Reply-To: <Pine.SOL.4.58.0612221824500.2856@titan.cfa.harvard.edu>

Gaspar Bakos wrote:
> Hi, Eric,
> 
> RE:
>>> xfs_check: unexpected XFS SB magic number 0x45464920
>> That spells "EFI"
> 
> Does this have any special meaning? E.g. I could figure out who
> labelled the disk (array)?

EFI is a bootloader....

>> looks like somebody came along & labeled your disk for you.  Dangers of
>> being on a san I suppose (if you are....)
> 
> Humm. This is an FC5 with SMP opteron. The RAID-5 (12 disks) is ran by
> an ARECA 1130-ML card.
> 
>> repair might fix it....
> 
> I worry that what repair will leave behind is pure numbers (and many of those), like
> 11212/
> 12133/
> 121212/
> ...
> and to reconstruct ~3Tb from that is not trivial...
> 
> This reminds me: what paranoid safety measures can one take? E.g keep
> an external log of the filesystem as well?
> 
> Thanks for the thoughts!
> 
> Gaspar
> 

  reply	other threads:[~2006-12-22 23:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22 17:42 unexpected XFS SB magic number Gaspar Bakos
2006-12-22 20:12 ` Russell Cattelan
2006-12-22 20:51   ` Gaspar Bakos
2006-12-22 23:15 ` Eric Sandeen
2006-12-22 23:28   ` Gaspar Bakos
2006-12-22 23:33     ` Eric Sandeen [this message]
2006-12-22 23:38     ` Eric Sandeen
2006-12-23 23:08       ` Gaspar Bakos
2006-12-24  3:50         ` Eric Sandeen
2006-12-24  6:08           ` Gaspar Bakos
2006-12-24 12:16         ` Iustin Pop
2007-10-07  9:47 ` qon
  -- strict thread matches above, loose matches on Subject: below --
2006-12-22 17:45 Gaspar Bakos

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=458C6B32.5090004@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=gbakos@cfa.harvard.edu \
    --cc=linux-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