linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Comolli <fabio.comolli@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Theodore Tso <tytso@mit.edu>
Subject: Re: Crash in 2.6.28.7 - ext4 related
Date: Thu, 26 Feb 2009 10:18:29 +0100	[thread overview]
Message-ID: <b637ec0b0902260118o19f74acal567440a6f049512@mail.gmail.com> (raw)
In-Reply-To: <b637ec0b0902251203i1fe5f081vfd06350dbf5060e9@mail.gmail.com>

OK, I see that my message didn't reach neither linux-kernel nor
linux-fsdevel, maybe because of the image size (484K).

If anyone is interested in details, please let me know.

Regards,
Fabio



On Wed, Feb 25, 2009 at 9:03 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
> Hi all.
> I experience hard crashes with latest stable kernel (but also in every
> 2.6.28.y release). This time I was trying to remove a large directory
> (a kernel tree) in a clean (fsck -f from a previous crash) ext4
> partition.
>
> The partition is an ext3 converted one, with extents enabled. It's
> about 20gb in size.
>
> When the crash happened the sistem was just booted in single user;
> fsck -f; mount; rm -rf <dir>; bang. Please look at the attached
> picture.
>
> The kernel is vanilla 2.6.28.7 + opensuse bootsplash patch.
>
> Please let me know if you need more details. Unfortunately for me it
> seems to be pretty easily reproduceable. By the way, some of the
> previous crashes did not involve file removals.
>
> Regards,
> Fabio
>

           reply	other threads:[~2009-02-26  9:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <b637ec0b0902251203i1fe5f081vfd06350dbf5060e9@mail.gmail.com>]

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=b637ec0b0902260118o19f74acal567440a6f049512@mail.gmail.com \
    --to=fabio.comolli@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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).