mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Duncan Sands <duncan.sands@math.u-psud.fr>
To: "Avuton Olrich" <avuton@gmail.com>
Cc: "Nathan Scott" <nathans@sgi.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
Date: Sun, 25 Jun 2006 12:09:23 +0200	[thread overview]
Message-ID: <200606251209.23766.duncan.sands@math.u-psud.fr> (raw)
In-Reply-To: <3aa654a40606200120v5baf0304ka205f1ad8f136ad9@mail.gmail.com>

I just got a new XFS crash running 2.6.17, again with problems at block
16777216 - I'll try to make a copy of the corrupted filesystem available.
Interestingly enough, I'm also seeing ext3 corruption.  The usual
manifestation is that a program fails to run, with a message about it
not being in executable format (if it happens again I will take a note of
the exact message).  I've had no problems at all with 2.6.17.  It seems
to be happening randomly, which makes me suspect a race condition
(uniprocessor machine, but preemptable kernel), or memory corruption.
I will rebuild the kernel with all kernel debugging options turned
on, once I recover the filesystem.

Ciao,

D.

  parent reply	other threads:[~2006-06-25 10:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  7:44 Avuton Olrich
2006-06-19 10:35 ` daniel+devel.linux.lkml
2006-06-20  6:10 ` Nathan Scott
2006-06-20  6:38   ` Avuton Olrich
2006-06-20  6:43     ` Nathan Scott
2006-06-20  6:50       ` Avuton Olrich
2006-06-20  6:52         ` Nathan Scott
2006-06-20  8:20           ` Avuton Olrich
2006-06-20  8:39             ` Duncan Sands
2006-06-22  2:56             ` Nathan Scott
2006-06-25 10:09             ` Duncan Sands [this message]
2006-06-25 13:55               ` Duncan Sands
2006-06-20  6:40   ` Avuton Olrich
2006-06-20  8:57     ` Justin Piszcz
2006-06-20 17:01       ` Avuton Olrich
2006-06-20 17:15         ` Justin Piszcz
2006-06-20 17:21           ` Avuton Olrich

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=200606251209.23766.duncan.sands@math.u-psud.fr \
    --to=duncan.sands@math.u-psud.fr \
    --cc=avuton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.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
all inboxes | Powered by JetHome®