From: Jens Axboe <axboe@suse.de>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-dev@namesys.com, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc6-mm1 reiser4 oopses on mount
Date: Thu, 8 Jun 2006 12:15:13 +0200 [thread overview]
Message-ID: <20060608101513.GZ5207@suse.de> (raw)
In-Reply-To: <1149761288.6336.23.camel@tribesman.namesys.com>
On Thu, Jun 08 2006, Vladimir V. Saveliev wrote:
> Hello
>
> On Thu, 2006-06-08 at 10:19 +0200, Jens Axboe wrote:
> > Hi,
> >
> > With the recent talks on what to merge and what not, I thought I'd try
> > and see how reiser4 fares in the io testing I was going to do in
> > 2.6.17-rc6-mm1 anyways. I didn't get very far.
> >
>
> Am I correct that you have CONFIG_DEBUG_FS=n?
> If yes, please, try to test reiser4 with DEBUG_FS turned on, while I am
> making a fix for that.
Nope, I had CONFIG_DEBUG_FS=y when the oops happened. I then turned
debugfs off, and now it mounts fine.
So the opposite :-)
--
Jens Axboe
prev parent reply other threads:[~2006-06-08 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 8:19 2.6.17-rc6-mm1 reiser4 oopses on mount Jens Axboe
2006-06-08 10:08 ` Vladimir V. Saveliev
2006-06-08 10:15 ` Jens Axboe [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=20060608101513.GZ5207@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
--cc=vs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox