From: Oleg Drokin <green@namesys.com>
To: Dave Jones <davej@suse.de>,
Sebastian Dr?ge <sebastian.droege@gmx.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@zip.com.au>
Subject: Re: Current Reiserfs Update / 2.5.2-dj7 Oops
Date: Thu, 31 Jan 2002 15:53:25 +0300 [thread overview]
Message-ID: <20020131155325.A3629@namesys.com> (raw)
In-Reply-To: <20020130151420.40e81aef.sebastian.droege@gmx.de> <20020130173715.B2179@namesys.com> <20020130163951.13daca94.sebastian.droege@gmx.de> <20020130190905.A820@namesys.com> <20020130174011.L24012@suse.de> <20020130201054.6e150f78.sebastian.droege@gmx.de> <20020130201757.Q24012@suse.de> <20020131122424.A874@namesys.com> <20020131134931.A5948@suse.de>
In-Reply-To: <20020131134931.A5948@suse.de>
Hello!
On Thu, Jan 31, 2002 at 01:49:31PM +0100, Dave Jones wrote:
> > 2.5.2-dj7 breaks instantly on the first truncate call to reiserfs.
> > I tried to dig up the difference between these 2 kernels but have not found
> > anything that will change that behaviour yet. And resierfs code is identical.
> > But dj7 seems to have a lot of modifications in the mm/* and fs/* stuff
> > compared to 2.5.3
> One possible is that I've goofed whilst merging Andrew Mortons
> "out of disk space during truncate" fixes from 2.4. Andrew, could
> have a quick scan through the fs/ changes in -dj6 and see if anything
> jumps out at you ?
Hm, but I remember dj6 was reported as "working"?
> I'll take a look myself later too, but right now, it's a head-scratcher.
Do you have some place where one can see all separate patches 2.5.2-dj7
consist of?
Bye,
Oleg
next prev parent reply other threads:[~2002-01-31 12:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 14:14 Current Reiserfs Update / 2.5.2-dj7 Oops Sebastian Dröge
2002-01-30 14:37 ` Oleg Drokin
2002-01-30 15:39 ` Sebastian Dröge
2002-01-30 16:09 ` Oleg Drokin
2002-01-30 16:40 ` Dave Jones
2002-01-30 16:44 ` Oleg Drokin
2002-01-30 16:55 ` Dave Jones
2002-01-30 17:07 ` Oleg Drokin
2002-01-30 19:10 ` Sebastian Dröge
2002-01-30 19:17 ` Dave Jones
2002-01-31 6:09 ` Oleg Drokin
2002-01-31 9:24 ` Oleg Drokin
2002-01-31 12:49 ` Dave Jones
2002-01-31 12:53 ` Oleg Drokin [this message]
2002-01-31 13:11 ` Dave Jones
2002-01-31 16:44 ` Oleg Drokin
2002-01-31 17:23 ` Sebastian Dröge
2002-01-31 17:45 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 10:10 Martin Bahlinger
2002-01-31 13:03 ` Oleg Drokin
2002-01-31 17:20 ` Martin Bahlinger
2002-01-31 17:44 Martin Bahlinger
2002-01-31 20:44 ` Martin Bahlinger
2002-02-01 5:55 ` Oleg Drokin
2002-02-01 22:17 ` Martin Bahlinger
2002-02-02 8:30 ` Oleg Drokin
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=20020131155325.A3629@namesys.com \
--to=green@namesys.com \
--cc=akpm@zip.com.au \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.droege@gmx.de \
/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.