linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Torsten Scheck <torsten.scheck@gmx.de>
To: andersen@codepoet.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Large-FAT32-Filesystem Bug
Date: Fri, 05 Dec 2003 18:54:21 +0100	[thread overview]
Message-ID: <3FD0C64D.5050804@gmx.de> (raw)
In-Reply-To: <20031205160746.GA18568@codepoet.org>

Erik Andersen wrote:
> On Fri Dec 05, 2003 at 10:52:31AM +0100, Torsten Scheck wrote:
[...]
>>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.
> 
> 
> Does this help?
> 
>  -Erik

[... int=>loff_t ino,inum-patch ...]

Hi Erik:

I applied your patch to 2.4.23 and it solved the problem. No more lost 
clusters. All data stays where it belongs.

I'll test it for a few days and get back to you later.

Thank you very much.

Torsten


For those who play with vfat filesystems now:

I noticed that fsck.vfat just pretends to repair a _mounted_ vfat 
filesystem. You have to unmount it, so it is actually repaired. An error 
message would be appropriate here. I'll contact the dosfsck maintainer, 
but I thought telling you might avoid confusion.


  reply	other threads:[~2003-12-05 17:54 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
2003-12-05 16:07 ` Erik Andersen
2003-12-05 17:54   ` Torsten Scheck [this message]
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=3FD0C64D.5050804@gmx.de \
    --to=torsten.scheck@gmx.de \
    --cc=andersen@codepoet.org \
    --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;
as well as URLs for NNTP newsgroup(s).