All of lore.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: Sat, 23 Dec 2006 21:50:15 -0600	[thread overview]
Message-ID: <458DF8F7.5030104@sandeen.net> (raw)
In-Reply-To: <Pine.SOL.4.58.0612231748450.3446@titan.cfa.harvard.edu>

Gaspar Bakos wrote:
> Hi, Eric,

> One of the users was running quite memory and disk IO intensive tasks
> past week. This lead to a crash. (I was not around to keep an eye on
> it). The computer rebooted, and few days later another crash, etc.
> Finally, when I returned this week, I found it powered off.
> 
> And then I realized that the sdc1 partition can not be mounted any more.

Well, something put a gpt label on top of your xfs partition... and it 
wasn't xfs :)

>> i also remember something about parted (maybe...) finding a backup gpt
>> signature at the end of a disk, and "helpfully" copying it over the
>> front end if so.  This was a bug.  sgi guys do you remember?
> 
> But for this one has to invoke parted, and commit the operations done,
> am I right?

if I recall, even invoking parted could do this.

> Maybe there is a nasty daemon doing something. The fs was also exported
> as NFS and mounted by two other hosts.
> 
> ---------
> So the questions are:
> - what partition type to choose next time?
> - is there a simpler way of recovery (than xfs_recovery), i.e. the
>   first few bytes of the partition need to be changed back to something
>   XFS magic, and the rest is probably untouched?

i'd google around and find out how big the gpt header is; try to find 
out how much of the front of your partition got clobbered.  that'll give 
a clue as to how much you may have lost.

-Eric

  reply	other threads:[~2006-12-24  4:06 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
2006-12-22 23:38     ` Eric Sandeen
2006-12-23 23:08       ` Gaspar Bakos
2006-12-24  3:50         ` Eric Sandeen [this message]
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=458DF8F7.5030104@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 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.