public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Spam Magnet <spam.wax@gmail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: XFS: SB validate failed
Date: Mon, 02 Jun 2008 12:08:42 +1000	[thread overview]
Message-ID: <4843562A.9030503@sgi.com> (raw)
In-Reply-To: <3607657a0805301019h4a49dc86ne8f1f019629a1c41@mail.gmail.com>

Spam Magnet wrote:
>> As Eric said.
>> We chose the ondisk format to have the byte ordering of IRIX so
>> it should not be a problem. However, parts of the log code in Linux
>> does not do the necessary endian conversion (due to lack of info at
>> the relevant points - it only knows as blobs of data) and so you
>> need the log to be clean. i.e. byte ordering problem just for the log.
>>
> 
> Thanks for this info, it's good to have 1 less problem to worry about :)
> 
>> OOI, as Eric asked, how were you able to mount it all of a sudden?
>>
> 
> I am not sure, as I said, to narrow down the problem I am experiencing
> with other disks, I decided to format an empty, healthy disk under Irix and
> try to mount it under Linux. The first try was not successful but the
> second was.
> 
> Right now I am making an image of the good/healthy disk using dd to
> see if I can mount that
> image under Linux. (It's not fun to copy 2GB disks through a
> USB1.1-SCSI adapter :)

:-)
If the fs is not too full then xfs_copy would be good I suppose as
it won't copy freespace.

--Tim

      parent reply	other threads:[~2008-06-02  2:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29 17:05 XFS: SB validate failed Spam Magnet
2008-05-29 17:19 ` Eric Sandeen
2008-05-29 19:55   ` Spam Magnet
2008-05-29 20:02     ` Eric Sandeen
2008-05-29 21:00       ` Spam Magnet
2008-05-29 21:06         ` Eric Sandeen
2008-05-29 21:46           ` Spam Magnet
2008-05-29 22:19             ` Eric Sandeen
2008-05-29 22:25             ` Stefan Smietanowski
2008-05-30  5:28             ` Timothy Shimmin
2008-05-30 17:19               ` Spam Magnet
2008-05-30 17:59                 ` Stefan Smietanowski
2008-05-30 23:26                   ` Hamid
2008-05-31  0:19                     ` Stefan Smietanowski
2008-05-31  0:22                       ` Stefan Smietanowski
2008-06-01  7:35                       ` Hamid
2008-06-01 10:46                         ` Stefan Smietanowski
2008-06-03 17:36                           ` Spam Magnet
2008-06-03 17:56                             ` Spam Magnet
2008-06-03 18:59                               ` Stefan Smietanowski
2008-06-03 19:39                                 ` Spam Magnet
2008-06-03 20:23                                   ` Stefan Smietanowski
2008-06-05 16:16                                     ` Spam Magnet
2008-06-02  2:08                 ` Timothy Shimmin [this message]

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=4843562A.9030503@sgi.com \
    --to=tes@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=spam.wax@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