From: Eric Sandeen <sandeen@sandeen.net>
To: Jesse Stroik <jstroik@ssec.wisc.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Seg fault during xfs repair (segmentation fault / segv)
Date: Wed, 01 Jul 2009 15:52:25 -0500 [thread overview]
Message-ID: <4A4BCC89.10202@sandeen.net> (raw)
In-Reply-To: <4A4BCC44.7050302@ssec.wisc.edu>
Jesse Stroik wrote:
> Eric,
>
> Thanks for addressing the issue with xfs_repair.
>
>
>> that's one crunchy filesystem you've got there; what happened to it?
>
>
> It's not entirely clear -- the JBOD and SAS controller seem to have
> gotten into inconsistent states and I was observing a few SCSI errors
> for those particular LUNs. While the system was exhibiting the SCSI
> errors, the user of this file system (and a few others like it on the
> host) noticed file corruption when reading/writing certain files, then
> spontaneous corruption after making copies of the files.
>
> I'll take a look at the new xfs_check and see what happens.
>
> Best,
> Jesse
>
Turns out that it runs to completion, but another run still finds
corruption. And a debug build trips asserts, so I guess there are still
issues.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-01 20:51 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
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 [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=4A4BCC89.10202@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jstroik@ssec.wisc.edu \
--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