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 17:19:57 -0500 [thread overview]
Message-ID: <483F2C0D.1020401@sandeen.net> (raw)
In-Reply-To: <3607657a0805291446t79808c63l664780c1cbc3d871@mail.gmail.com>
Spam Magnet wrote:
>> try xfs_repair -n then maybe. Or update xfsprogs. check shouldn't
>> segfault, regardless of the fs state.
>>
>
> I updated xfsprogs to the latest version (cvs checkout) and it solved
> the segfault.
>
>> nah that's fine, images or disks, whichever.
>>
>
> So I guess it doesn't matter if I do the image either using dd or xfsdump.
> I'd prefer dd since I get a lot of issues trying to compile xfsprogs under Irix.
>
> Assuming that I get an image using dd, would a simple mount command suffice
> to use the xfs utils ? :
> $ mount -t xfs -o loop disk.img /mnt
that's fine, assuming your dd was of the partition that actually held
the xfs fs.
-Eric
next prev parent reply other threads:[~2008-05-29 22:19 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 [this message]
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=483F2C0D.1020401@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