From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: kernel crash with damaged XFS
Date: Sat, 7 Nov 2009 08:37:20 +0100 [thread overview]
Message-ID: <200911070837.21003@zmi.at> (raw)
In-Reply-To: <88ED0857-A754-4E3C-BA26-FC5EE85D7394@sandeen.net>
On Freitag 06 November 2009 Eric Sandeen wrote:
> > I had that during the last days on my system. It kept on running
> > despite
> > this error. I xfs_repair'ed the fs again and now it's working.
> > This is the same server I talked about with Eric last time, where
> > he improved xfs_repair and that repaired my fs. I had to run
> > xfs_repair several times again until all errors were solved,
> > and now nothing is reported anymore.
> > The server had no crash or whatever since the last repair, so I
> > wonder where these corruptions come from.
> >
> > Nov 2 00:01:12 orion.i.zmi.at kernel: Filesystem "dm-0": corrupt
> > inode 3858839593 ((a)extents = 7). Unmount and run xfs_repair.
>
> Just FWIW this is not a crash, it is XFS properly handling
> corrruption it encountered. The corruption could be due to a bug
> in XFS or other code, or a hardware problem. Does repair fix it this
> time?
Yes Eric, that's what I wrote but I see it can be misinterpreted as
belonging to the old case. I meant the actual problem when saying:
I had to run xfs_repair several times again until all errors were
solved, and now nothing is reported anymore. The server had no crash or
whatever since the last repair, so I wonder where these corruptions come
from.
Seems to be time to make a memory check. I have no other idea where the
problem could come from.
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-11-07 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 9:17 kernel crash with damaged XFS Michael Monnerie
2009-11-06 13:38 ` Eric Sandeen
2009-11-07 7:37 ` Michael Monnerie [this message]
2009-11-07 11:28 ` Justin Piszcz
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=200911070837.21003@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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