From: Frank van Maarseveen <F.vanMaarseveen@inter.NL.net>
To: Guest section DW <dwguest@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11 EXT2 corruption (closed)
Date: Mon, 11 Dec 2000 09:21:30 +0100 [thread overview]
Message-ID: <20001211092130.A9129@iapetus.localdomain> (raw)
In-Reply-To: <20001210161723.A1060@iapetus.localdomain> <20001210183101.A6947@iapetus.localdomain> <20001210213500.A17413@iapetus.localdomain> <20001210224402.A913@iapetus.localdomain> <20001211013736.A18862@win.tue.nl>
In-Reply-To: <20001211013736.A18862@win.tue.nl>; from dwguest@win.tue.nl on Mon, Dec 11, 2000 at 01:37:36AM +0100
On Mon, Dec 11, 2000 at 01:37:36AM +0100, Guest section DW wrote:
>
> I see lots of messages from you about corruption in 2.4.0-test11
> but we all know very well that 2.4.0-test11 corrupts things
> and further evidence is not necessary.
> Hopefully all, or at least the most significant, problems
> have been solved now, so you should upgrade to the most
> recent test kernel and see how things are there.
>
Thanks. test12-pre7 fixes this for me: it ran all night testing and
no problems so far.
--
Frank
-
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-11 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-10 15:17 2.4.0-test11 EXT2 corruption Frank van Maarseveen
2000-12-10 17:31 ` 2.4.0-test11 EXT2 corruption (2) Frank van Maarseveen
2000-12-10 20:35 ` 2.4.0-test11 EXT2 corruption (3) Frank van Maarseveen
2000-12-10 20:39 ` Jens Axboe
2000-12-10 21:44 ` 2.4.0-test11 EXT2 corruption: mixing up file contents Frank van Maarseveen
2000-12-11 0:37 ` Guest section DW
2000-12-11 8:21 ` Frank van Maarseveen [this message]
2000-12-11 12:08 ` 2.4.0-test11 EXT2 corruption (closed) Johan Bergström
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=20001211092130.A9129@iapetus.localdomain \
--to=f.vanmaarseveen@inter.nl.net \
--cc=dwguest@win.tue.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®