From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Jens Axboe <axboe@suse.de>
Cc: "David S. Miller" <davem@redhat.com>,
viro@math.psu.edu, linux-kernel@vger.kernel.org,
tytso@valinux.com
Subject: Re: 2.4.0-test11 ext2 fs corruption
Date: Wed, 29 Nov 2000 12:41:28 MET-1 [thread overview]
Message-ID: <E3B2B45385F@vcnet.vc.cvut.cz> (raw)
On 29 Nov 00 at 1:43, Jens Axboe wrote:
> Could you try and reproduce with attached patch? If this would trigger
> I would assume fs corruption as well (which doesn't seem to be the
> case for you), but it's worth a shot.
I'll try, but it is not easily reproducible. Fortunately.
BTW, during night, it came to me that maybe I was biased with original
diagnostics (thing written twice), as there was (~3 weeks ago) unpacked
XF4.0.1-0phase?v27 on the same disk.
As font data did not change between these two versions, it is possible
that one 27 blocks chunk (*.c files) was lost (or written somewhere where
I did not found it yet), instead of another one (fonts) duplicated.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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 reply other threads:[~2000-11-29 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 12:41 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 12:21 2.4.0-test11 ext2 fs corruption 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 21:10 Petr Vandrovec
2000-11-28 20:04 ` David S. Miller
2000-11-28 20:41 ` Alexander Viro
2000-11-29 16:26 ` Daniel Phillips
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=E3B2B45385F@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--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 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.