From: Jesse Stroik <jstroik@ssec.wisc.edu>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: Seg fault during xfs repair (segmentation fault / segv)
Date: Tue, 30 Jun 2009 16:01:56 -0500 [thread overview]
Message-ID: <4A4A7D44.7040009@ssec.wisc.edu> (raw)
In-Reply-To: <4A4A5C4E.7030605@sandeen.net>
Eric,
Eric Sandeen wrote:
> Jesse Stroik wrote:
>> I have a server with a ~20TB xfs file system on Linux
>> (2.6.18-92.1.22.el5) and am running xfsprogs-2.9.4-4.el5. We had a few
>> corrupted files which I believe were due to a SCSI issue after a recent
>> power outage. Due to the corruption, I ran xfs_check and would like to
>> run xfs_repair on the system.
>
> It'd really be great to test more recent xfsprogs first, that one is
> about 2 years old.
>
> You can probably grab any recent fedora src.rpm and rebuild it, and
> later go back to the centos version if you wish.
I fetched the current version from SVN using these directions:
http://xfs.org/index.php/Getting_the_latest_source_code
I get identical results.
--------
...
reset bad sb for ag 31
reset bad agf for ag 31
reset bad agi for ag 31
Segmentation fault
$ ./xfs_repair -V
xfs_repair version 3.0.2
--------
If you want me to rebuild with debug and get you any specific
information, let me know.
Best,
Jesse
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-30 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 18:29 Seg fault during xfs repair (segmentation fault / segv) Jesse Stroik
2009-06-30 18:41 ` Eric Sandeen
2009-06-30 21:01 ` Jesse Stroik [this message]
2009-06-30 21:11 ` Eric Sandeen
2009-07-01 19:53 ` Eric Sandeen
2009-07-01 20:34 ` Eric Sandeen
2009-07-01 20:51 ` Jesse Stroik
2009-07-01 20:52 ` Eric Sandeen
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=4A4A7D44.7040009@ssec.wisc.edu \
--to=jstroik@ssec.wisc.edu \
--cc=sandeen@sandeen.net \
--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