From: "David S. Miller" <davem@redhat.com>
To: VANDROVE@vc.cvut.cz
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org, tytso@valinux.com
Subject: Re: 2.4.0-test11 ext2 fs corruption
Date: Tue, 28 Nov 2000 12:04:01 -0800 [thread overview]
Message-ID: <200011282004.MAA01496@pizda.ninka.net> (raw)
In-Reply-To: <E2BA5DE1AE9@vcnet.vc.cvut.cz> (VANDROVE@vc.cvut.cz)
In-Reply-To: <E2BA5DE1AE9@vcnet.vc.cvut.cz>
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Date: Tue, 28 Nov 2000 21:10:36 MET-1
Yes, it is identical copy. But I do not think that hdd can write same
data into two places with one command...
Petr, did the af_inet.c assertions get triggered on this
same machine?
If yes, you seem to have some crazy kernel data corruptions
going on, and whatever it is would seem to be the cause of
both these problems you are reporting.
Later,
David S. Miller
davem@redhat.com
-
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-11-28 20:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 21:10 2.4.0-test11 ext2 fs corruption Petr Vandrovec
2000-11-28 20:04 ` David S. Miller [this message]
2000-11-28 20:41 ` Alexander Viro
2000-11-29 16:26 ` Daniel Phillips
2000-11-30 0:03 ` [PATCH] " Daniel Phillips
2000-11-30 0:33 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 12:41 Petr Vandrovec
2000-11-29 12:21 schwidefsky
2000-11-29 12:43 ` Alexander Viro
2000-11-28 21:46 Petr Vandrovec
2000-11-29 0:43 ` Jens Axboe
2000-11-29 1:08 ` Andrea Arcangeli
2000-11-29 1:11 ` Jens Axboe
2000-11-29 1:32 ` Andre Hedrick
2000-11-28 20:32 Petr Vandrovec
2000-11-28 20:02 ` Alexander Viro
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=200011282004.MAA01496@pizda.ninka.net \
--to=davem@redhat.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@valinux.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox