linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Strange disk corruption with Linux >= 2.6.13
Date: Sat, 1 Oct 2005 18:36:55 -0300	[thread overview]
Message-ID: <20051001213655.GE6397@ime.usp.br> (raw)
In-Reply-To: <1127863912.4802.52.camel@localhost>

On Sep 28 2005, Nigel Cunningham wrote:
> Hi Rogerio.

Hi, Nigel.

> On Tue, 2005-09-27 at 21:10, Rogério Brito wrote:
> > Hi there. I'm seeing a really strange problem on my system lately and I
> > am not really sure that it has anything to do with the kernels.
> 
> I've seen the thread mostly following the hardware line. I'd like to
> enquire down the kernel path because I've seen occasional, impossible
> to reproduce problems too.

Nice. I also don't want to rule out anything before I really understand
what's going on.

> Can I ask first a few questions:

Of course.

> 1) Are you using vanilla kernels, or do you have other patches applied?

Yes, all the kernels that I use are just plain vanilla kernels taken
straight from kernel.org. No other patches applied.

> 2) Are you using ext3 only?

Yes, I am.

> 3) Is the corruption only ever in memory, or seen on disk too?

I have noticed the problem mostly on disk. One strange situation was
when I was untarring a kernel tree (compressed with bzip2) and in the
middle of the extraction, bzip2 complained that the thing was
corrupted.

I removed what was extracted right away and tried again to extract the
tree (at this point, suspecting even that something in software had
problems). The problem with bzip2 occurred again. Then, I rebooted the
system an the problem magically went away.

> 4) Is the corruption only in one filesystem or spread across several
> (if applicable)? (ie in / but not /home or others?)

I only have one filesystem right now, but given the difficulties that
I'm seeing, I do plan to go back to a multiple filesystem setup (which I
always used but thought that was overkill---nothing like time to teach
us something what is safest).

If you want to know anything else, don't hesistate to ask.


Regards,

-- 
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/

  reply	other threads:[~2005-10-01 21:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 11:10 Strange disk corruption with Linux >= 2.6.13 Rogério Brito
2005-09-27 11:34 ` Diego Calleja
2005-09-27 11:58   ` Rogério Brito
2005-09-27 12:10     ` Rogério Brito
2005-09-27 11:57 ` Grant Coady
2005-09-27 12:43   ` Ondrej Zary
2005-10-01 21:22     ` Rogério Brito
2005-09-27 14:04   ` Lennart Sorensen
2005-10-01 21:28     ` Rogério Brito
2005-10-03 16:20       ` Lennart Sorensen
     [not found] ` <Pine.LNX.4.63.0509271331590.21130@alpha.polcom.net>
2005-09-27 12:20   ` Rogério Brito
2005-09-27 12:38     ` Grzegorz Kulewski
2005-09-27 19:42       ` Guennadi Liakhovetski
2005-09-27 21:01         ` Erik Mouw
2005-09-27 21:44           ` Guennadi Liakhovetski
2005-10-01 21:15         ` Rogério Brito
2005-10-08 22:35           ` Guennadi Liakhovetski
2005-10-09  9:30             ` Rogério Brito
2005-10-01 21:02       ` Rogério Brito
2005-09-27 23:31 ` Nigel Cunningham
2005-10-01 21:36   ` Rogério Brito [this message]
2005-10-02  0:06     ` Grant Coady
2005-10-03  4:17       ` Rogério Brito
2005-10-03  4:20         ` Willy Tarreau
2005-10-03  4:55     ` Nigel Cunningham
2005-10-04 10:28     ` Sander
2005-10-04 12:42       ` Nigel Cunningham
2005-09-28  8:43 ` Ville Herva
2005-09-28 23:23   ` Alan Cox
2005-09-29  6:29     ` Ville Herva
2005-09-29 16:14       ` Alan Cox
2005-10-03  5:05         ` Rogério Brito
2005-10-03  5:15   ` Rogério Brito
     [not found] <4RlFC-2ev-17@gated-at.bofh.it>
     [not found] ` <4Rxdq-2Tc-19@gated-at.bofh.it>
     [not found]   ` <4SXfs-7hM-27@gated-at.bofh.it>
2005-10-02  3:37     ` Bodo Eggert
2005-10-03  4:30       ` Rogério Brito

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=20051001213655.GE6397@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.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;
as well as URLs for NNTP newsgroup(s).