From: Jorg de Jong <j.e.s.de.jong@freeler.nl>
To: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: test12: innd bug came back?
Date: Mon, 18 Dec 2000 12:24:54 +0100 [thread overview]
Message-ID: <3A3DF406.8C3439C4@freeler.nl> (raw)
In-Reply-To: <Pine.GSO.4.21.0012171623240.20573-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
> 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 !)
>
> I.e. old contents resurfacing in active?
I tryed your test program and got correct results, a file with bytes 11-16385 being zero.
I will try to give a description of my problems:
after a reboot inn is 're-using' existing messages to store new
messages. It seems that after a renumber command the active file
is correced again. I have not checked to see if the active file
was corrutped before.
I am using a plain stock kernel, no other patches what so ever,
but am using LVM.
The blocksize the ext2 filesystem is using is 1024.
--
Jorg de Jong
Work : mailto:jorg.de.jong@ict.nl
Play : mailto:j.e.s.de.jong@freeler.nl
-
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 parent reply other threads:[~2000-12-18 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0012171623240.20573-100000@weyl.math.psu.edu>
2000-12-18 11:24 ` Jorg de Jong [this message]
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
2000-12-18 10:44 ` Chris Mason
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=3A3DF406.8C3439C4@freeler.nl \
--to=j.e.s.de.jong@freeler.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.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 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.