public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Spam Magnet <spam.wax@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS: SB validate failed
Date: Thu, 29 May 2008 16:06:53 -0500	[thread overview]
Message-ID: <483F1AED.3010808@sandeen.net> (raw)
In-Reply-To: <3607657a0805291400h3c50165lea6fbea919deed0f@mail.gmail.com>

Spam Magnet wrote:
>> Byte ordering is only an issue for the log replay; you'd get a message
>> about that if it were the issue.
>>
>> Does file -s /dev/sdb? say that any of those things even look like an
>> xfs filesystem?
>>
>> If so point xfs_db at it like:
>>
>> xfs_db -r -c "sb 0" -c "p" /dev/sdb<whatever>
>>
> it's indeed an xfs filesystem:
> $ sudo file -s /dev/sdb8
> /dev/sdb8: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs)
> 

...

> 
> I can mount and see the content of this disk: using:
> mount -t xfs /dev/sdb8 /mnt

oh, I thought you couldn't mount it :)

> But xfs_check still crashes on me :(
> /usr/sbin/xfs_check: line 28: 26782 Segmentation fault (core dumped)
> xfs_db$DBOPTS -i -p xfs_check -c "check$OPTS" $1

try xfs_repair -n then maybe.  Or update xfsprogs.  check shouldn't
segfault, regardless of the fs state.

> Will it be ok if I made a 1:1 image of my disks under Irix (using dd):
> 
> $ dd if=/dev/dsk/dks1d3vol of=disk.img bs=512 conv=ignerror,sync
> 
> And tried to use xfs module in Linux to mount them ? or this programs
> are only meant to work with actual device rather than an image file ?

nah that's fine, images or disks, whichever.

-Eric

> thanks for your patience
> 

  reply	other threads:[~2008-05-29 21:06 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 [this message]
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

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=483F1AED.3010808@sandeen.net \
    --to=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