linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mateusz Marzantowicz <mateuszm@server.pl>
To: linux-admin@vger.kernel.org
Subject: Flooded by floppy
Date: Wed, 09 Jun 2004 17:13:26 +0200	[thread overview]
Message-ID: <40C72916.6050504@server.pl> (raw)

Hello

Yesterday when I tried to use my floppy I was a little bit confused.
My computer hanged up and I couldn't even as a root do anything.
I wasn't able to print processes working on my machine.
After hardware reboot (system hanged up when killing processes on 
shutdown) I saw that
on my system logs was a lot of lines like this:

Jun  8 23:56:47 webprog kernel: FAT: Filesystem panic (dev fd0)
Jun  8 23:56:47 webprog kernel: invalid access to FAT (entry 0x0000478c)
Jun  8 23:56:47 webprog kernel: File system has been set read-only
Jun  8 23:56:47 webprog kernel: FAT: Filesystem panic (dev fd0)
Jun  8 23:56:47 webprog kernel: invalid access to FAT (entry 0x0000ff30)
Jun  8 23:56:47 webprog kernel: FAT: Filesystem panic (dev fd0)
Jun  8 23:56:47 webprog kernel: fat_get_cluster: invalid cluster chain 
(i_pos 0)
Jun  8 23:57:22 webprog kernel: FAT: Filesystem panic (dev fd0)
Jun  8 23:57:22 webprog kernel: invalid access to FAT (entry 0x00008000)
Jun  8 23:57:22 webprog kernel: FAT: Filesystem panic (dev fd0)
Jun  8 23:57:22 webprog kernel: invalid access to FAT (entry 0x00000e0d)
Jun  8 23:58:26 webprog kernel: FAT: Filesystem panic (dev fd0)
Jun  8 23:58:26 webprog kernel: invalid access to FAT (entry 0x00007872)

As you can see 4-6 messages per second!
For me it's a kernel bug. But maby there is some solution not to repeat 
this situation?

Sorry for my English - I still learning.

Regards Mateusz Marzantowicz

                 reply	other threads:[~2004-06-09 15:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40C72916.6050504@server.pl \
    --to=mateuszm@server.pl \
    --cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).