public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Karsten Becker <KB@Karsten-Becker.de>
Cc: linux-fsdevel@vger.kernel.org,
	Gordon Chaffee <chaffee@cs.berkeley.edu>,
	Roman Hodek <roman@hodek.net>
Subject: Re: Problems with big vfat
Date: Tue, 4 Jun 2002 17:05:14 -0700	[thread overview]
Message-ID: <20020605000514.GC448@matchmail.com> (raw)
In-Reply-To: <3CFB9B8F.4020701@Karsten-Becker.de>

On Mon, Jun 03, 2002 at 06:38:39PM +0200, Karsten Becker wrote:
> Hi,
> I've got a very big (367GB) Fat32-FS. I need this partition for data 
> exchange between windows and linux.
> When I have mounted the FS for a longer time and do some changes on this 
> I got lost filesegments in scandisk. The partition is on a 6*100GB Raid5 
> (3ware 7810). Has anyone an idea what the problem might be?
> Is there any better way to exchange Data with windows?  (reiserfs,ext3 
> rw-driver for windows?)
> Cheers,
> Karsten

Can you do some tests with non-important data?

If so, try to stress the vfat filesystem and scandisk in dos.  If scandisk
finds errors, don't fix them.  Reboot back into linux and run fsck on it
there.

Now report the errors that fsck finds, if any (read the documentation first,
there are some tips).  Maybe they can get enough information on the type of
corruption there is to update vfatfs, and fsck.vfat. 

Gordon, Roman (vfat & fsck.vfat maintainer respectively), do you have anything to
say about this? 

Thanks,

Mike

  parent reply	other threads:[~2002-06-05  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03 16:38 Problems with big vfat Karsten Becker
2002-06-04  3:35 ` Mike Fedyk
2002-06-04  8:41   ` Karsten Becker
2002-06-04  8:47     ` Andreas Dilger
2002-06-05  0:05 ` Mike Fedyk [this message]
2002-06-05 11:11   ` Karsten Becker

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=20020605000514.GC448@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=KB@Karsten-Becker.de \
    --cc=chaffee@cs.berkeley.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=roman@hodek.net \
    /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