All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Danny Milosavljevic" <danny_milo@yahoo.com>
To: reiserfs-list@namesys.com
Subject: Re: reiser4 cryptcompress test setup: bug
Date: Tue, 7 Nov 2006 15:13:30 +0000 (UTC)	[thread overview]
Message-ID: <eiq7qq$de5$1@sea.gmane.org> (raw)
In-Reply-To: 200611062207.kA6M7Gsj002629@turing-police.cc.vt.edu

Hi,

On Mon, 06 Nov 2006 17:07:16 -0500, Valdis.Kletnieks wrote:

> On Mon, 06 Nov 2006 19:27:57 GMT, Danny Milosavljevic said:
>> Hi Edward,
>> 
>> I finally tried your cryptcompress setup (2.6.18-mm3) and just did the
>> first evil thing I could think of:
>> 
>> the reiser4 partition with ccreg40 enabled is /dev/sda1 (/mnt/tmp/)
>> (mkfs'ed, thus empty).
> 
>> [  372.564358]  [<c01b6400>] ext3_dirty_inode+0x30/0x90
>> [  372.564364]  [<c016b4b9>] cp_new_stat64+0xf9/0x110
> 
> You might want to check /home sometime - this looks like an ext3 botch
> rather than a reiserfs botch, unless reiser4 is stomping on something
> behind ext3's back.

Well, I thought so at first, but:
/home is reiser4
/ is ext3 
no other ext3s

~/doc/literatur is on /home (checked via 'df .').

So, well, although it looks like it ext3 is the culprit, it is improbable
that it actually was the one triggering first (I never saw that
backtrace before, too). Naturally once Edwards says he doesn't need the
partition for analyzing, I'll nuke it and try to reproduce it again :)

cheers,
  Danny


      reply	other threads:[~2006-11-07 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 19:27 reiser4 cryptcompress test setup: bug Danny Milosavljevic
2006-11-06 22:07 ` Valdis.Kletnieks
2006-11-07 15:13   ` Danny Milosavljevic [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='eiq7qq$de5$1@sea.gmane.org' \
    --to=danny_milo@yahoo.com \
    --cc=danny.milo@scratchpost.org \
    --cc=reiserfs-list@namesys.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 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.