From: henrik@storner.dk (Henrik Størner)
To: linux-kernel@vger.kernel.org
Subject: Re: test12: innd bug came back?
Date: 17 Dec 2000 22:43:49 +0100 [thread overview]
Message-ID: <91jc2l$7tn$1@osiris.storner.dk> (raw)
In-Reply-To: <3A3D06D3.93041108@freeler.nl> <Pine.GSO.4.21.0012171626000.20573-100000@weyl.math.psu.edu>
In <Pine.GSO.4.21.0012171626000.20573-100000@weyl.math.psu.edu> Alexander Viro <viro@math.psu.edu> writes:
>On Sun, 17 Dec 2000, Jorg de Jong wrote:
>> > >On 13 Dec 2000, Henrik [ISO-8859-1] Størner wrote:
>> > >
>> > >> Just to add a "me too" on this. I didn't report when I saw it last week
>> I'd like to second that. ME TOO !
>> Since I switched to 2.4.0.test12 I again have the innd bug.
>> ( well at least the same symptoms !)
>Guys, what blocksize are you using?
I am using Reiserfs, and I hear it has some problems with the changes
introduced in pre12. So I will report back once the Reiserfs guys get
this settled.
--
Henrik Storner | "Crackers thrive on code secrecy. Cockcroaches breed
<henrik@storner.dk> | in the dark. It's time to let the sunlight in."
|
| Eric S. Raymond, re. the Frontpage backdoor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-17 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 4:36 test12: innd bug came back? Anton Petrusevich
2000-12-13 21:29 ` Henrik Størner
2000-12-13 21:56 ` Alexander Viro
2000-12-13 22:03 ` Linus Torvalds
2000-12-13 17:51 ` Albert Cranford
2000-12-17 18:32 ` Jorg de Jong
2000-12-17 21:35 ` Alexander Viro
2000-12-17 21:43 ` Henrik Størner [this message]
2000-12-18 10:44 ` Chris Mason
[not found] <Pine.GSO.4.21.0012171623240.20573-100000@weyl.math.psu.edu>
2000-12-18 11:24 ` Jorg de Jong
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='91jc2l$7tn$1@osiris.storner.dk' \
--to=henrik@storner.dk \
--cc=linux-kernel@vger.kernel.org \
/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.