From: Wolfgang Wegner <wolfgang@leila.ping.de>
To: linux-kernel@vger.kernel.org
Subject: e2fs corruption with 2.4.0-ac12
Date: Thu, 1 Feb 2001 23:59:30 +0100 (MET) [thread overview]
Message-ID: <200102012259.XAA02016@noefs.ping.de> (raw)
Hi,
just for the records, as I saw some reports about fs corruption:
I had a case of e2fs corruption under 2.4.0-ac12 on an IDE drive
(Intel BX chipset) yesterday.
I was not able to reproduce it, all I can say it seemed to be related
to a single file on a 1GB partition, filled about 70%. I noticed
mkisofs reading from this filesystem aborting with an I/O error,
resulting in "attempt to access beyond end of device". The
filesystem was generated some days ago under 2.2.14 using
mke2fs 1.18.
The machine itself is running fine under 2.2.14 for several
months, the only flaw is this partition being unused up to
now.
If this of any interest and there is any more information
I should provide, let me know.
Regards,
Wolfgang
-
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:[~2001-02-01 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 22:59 Wolfgang Wegner [this message]
2001-02-02 4:07 ` e2fs corruption with 2.4.0-ac12 Patrice Belleville
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=200102012259.XAA02016@noefs.ping.de \
--to=wolfgang@leila.ping.de \
--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