All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Theodore Tso <tytso@mit.edu>,
	Ben Greear <greearb@candelatech.com>,
	Alan <alan@lxorguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 file system went read-only in 2.6.18.2 (plus hacks)
Date: Mon, 08 Jan 2007 15:00:26 -0800	[thread overview]
Message-ID: <45A2CD0A.3010405@candelatech.com> (raw)
In-Reply-To: <20070108225324.GA16474@thunk.org>

Theodore Tso wrote:
> Well, the filesystem obviously got corrupted.  The only question is
> *why* it got corrupted.  It could be memory corruption, or a bug in
> your propietary kernel patches, or some kind of hardware issue with
> the CF device.  There's really no way to say for sure.

Ok.  I certainly can't guarantee my code is not somehow causing
the problem.

> Were there any error messages in the system log from the device
> driver?

I looked and did not see anything obvious.  The file system
was not overly full (49MB free, not counting the reserved
space for the root user.)

I appreciate you looking at the report.  If we see it again or
manage to find some way to reliably reproduce this on other
hardware, I will of course let you know.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2007-01-08 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 21:38 ext3 file system went read-only in 2.6.18.2 (plus hacks) Ben Greear
2007-01-08 22:05 ` Alan
2007-01-08 22:18   ` Ben Greear
2007-01-08 22:53     ` Theodore Tso
2007-01-08 23:00       ` Ben Greear [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=45A2CD0A.3010405@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.