From: Ben Chu <ben@imben.com>
To: linux-kernel@vger.kernel.org
Cc: ben@imben.com
Subject: Re: 2.4.0-test10 oops
Date: Sat, 11 Nov 2000 20:30:46 -0700 [thread overview]
Message-ID: <3A0E0EE6.8833FE72@imben.com> (raw)
In-Reply-To: <fa.f0mv7ev.d5s60h@ifi.uio.no>
Jan Dvorak said:
>
> Hi,
>
> attached oops came from writing to vfat fs.
This problem was brought up a couple of times before as referenced
here
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0010.3/0652.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0006.1/1754.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0003.3/0594.html
but I've never seen a solution as of yet.
In my own experiences, the bug didn't occur as frequently and
reproducably as it did when I moved to the 2.4.0-test series yet it
appears to be a long-standing issue.
I use Netscape Messenger to read my mail with the actual mail files
stored on a vfat partition. The problem seems to occur when
messages are copied to the vfat partition after being downloaded
from the mail server.
As noted in one of the above articles, it appears to be a
problem with the truncate function and Netscape uses this function
to use it to increase the size of its .summary files. My kernel is
OOPSing almost daily because of this problem.
I'm no kernel hacker so I'm hoping someone out there who is will
take notice of this problem. I've got the output of my own ksymoops
run from 2.4.0-test10 as well if anyone takes interest.
--
Ben Chu
-
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-11-12 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.f0mv7ev.d5s60h@ifi.uio.no>
2000-11-12 3:30 ` Ben Chu [this message]
2000-11-09 22:37 2.4.0-test10 oops Jan Dvorak
-- strict thread matches above, loose matches on Subject: below --
2000-11-06 22:03 2.4.0-test10 Oops Frank van Maarseveen
2000-11-07 3:19 ` Keith Owens
2000-11-07 20:00 ` Frank van Maarseveen
2000-11-08 11:44 ` Ingo Oeser
2000-11-03 0:26 Burton Windle
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=3A0E0EE6.8833FE72@imben.com \
--to=ben@imben.com \
--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