From: Eduard Bloch <edi@gmx.de>
To: Torsten Scheck <torsten.scheck@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Large-FAT32-Filesystem Bug
Date: Fri, 5 Dec 2003 16:26:18 +0100 [thread overview]
Message-ID: <20031205152618.GA10802@zombie.inka.de> (raw)
In-Reply-To: <3FD0555F.5060608@gmx.de>
Moin Torsten!
Torsten Scheck schrieb am Friday, den 05. December 2003:
> I found a critical FAT32 bug when I tried to store data onto an
> internal IDE 160 GB and onto an external USB2/FW-250 GB hard
> disk.
>
> From a certain fill level on, the data clusters of a newly added
> file entry get lost after a remount of the filesystem: the
> directory entry of the file has the size 0, the data is lost, and
> a fsck.vfat -r is needed to remove the unused clusters.
Funny (not), I noticed almost the same problem with a Firewire 250GB HD
(Maxtor). The data has been written to it (FAT32, 200gb-Partition), but
large files (IMO >= 1GB) got zero size and the data disappeared.
Scandisk from Windows could not find any errors, however the displayed
free space on this FAT filesystem has been lowered by the ammount of the
data written too it :(
I will try fsck.vfat later.
MfG,
Eduard.
next prev parent reply other threads:[~2003-12-05 15:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 9:52 Large-FAT32-Filesystem Bug Torsten Scheck
2003-12-05 13:17 ` jdow
2003-12-07 12:26 ` Helge Hafting
2003-12-07 12:20 ` Tomasz Torcz
2003-12-08 9:54 ` Helge Hafting
2003-12-08 14:10 ` Gene Heskett
2003-12-08 16:19 ` Randy.Dunlap
2003-12-07 13:56 ` Gene Heskett
2003-12-05 15:26 ` Eduard Bloch [this message]
2003-12-05 16:07 ` Erik Andersen
2003-12-05 17:54 ` Torsten Scheck
2003-12-05 22:10 ` Erik Andersen
2003-12-05 22:45 ` Mike Fedyk
2003-12-05 23:26 ` Måns Rullgård
2003-12-06 0:04 ` Andreas Schwab
2003-12-06 0:44 ` Måns Rullgård
2003-12-06 1:10 ` Andreas Schwab
2004-02-06 14:43 ` Torsten Scheck
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=20031205152618.GA10802@zombie.inka.de \
--to=edi@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torsten.scheck@gmx.de \
/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).