public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange write errors on FAT32 partition (maybe an FAT32 bug?!)
Date: Thu, 09 Nov 2006 19:32:46 +0100	[thread overview]
Message-ID: <4553744E.3050007@scientia.net> (raw)
In-Reply-To: <87psbzrss2.fsf@duaron.myhome.or.jp>

OGAWA Hirofumi wrote:
> Christoph Anton Mitterer <calestyo@scientia.net> writes:
>
>   
>> The strange thing is that one time the differences were found directly
>> after copying (thus one would thing RAM is damaged, because the data was
>> probalby (I cannot tell this for sure) taken from file cache).
>> and the other time after restarting with a certainly empty file cache.
>>
>> Any ideas? I'm willing to help debugging and so on but I must admit that
>> I need someone to say me what to do :D
>>     
>
> bit interesting. Could you send the output of diff? I'd like to see
> how it's breaking.
>   
Ok today I have perhaps some more information:
I've copied around 30 GBs from FAT32 to ext3.
I diffed everything,.. differences in one file. I recopied that one
file, rebooted, diffed again differences in another file:
euler:~# diff -q -r /mnt/tmp/CDDA_DATA_1 /mnt/CDDA/EAC_DATA_1 Files
/mnt/tmp/CDDA_DATA_1/LOTR 1/16.01.wav and /mnt/CDDA/EAC_DATA_1/LOTR
1/16.01.wav differ

Than after the complete diff was finished I diffed the single file again
euler:~# diff /mnt/tmp/CDDA_DATA_1/LOTR\ 1/16.01.wav
/mnt/CDDA/EAC_DATA_1/LOTR\ 1/16.01.wav
=> then,.. no differences?!
Am I crazy or what?

Is this know an memory problem? But if so why does memtest give me no
errors?

Regards,
Chris,


  parent reply	other threads:[~2006-11-09 18:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 15:21 Strange write errors on FAT32 partition (maybe an FAT32 bug?!) Christoph Anton Mitterer
2006-11-07 18:55 ` OGAWA Hirofumi
2006-11-07 21:32   ` Christoph Anton Mitterer
2006-11-09 18:32   ` Christoph Anton Mitterer [this message]
     [not found]     ` <45539188.5080607@atipa.com>
2006-11-09 20:45       ` Christoph Anton Mitterer
2006-11-09 20:54         ` Roger Heflin
2006-11-09 20:59           ` Christoph Anton Mitterer
2006-11-09 21:02             ` Roger Heflin
2006-11-09 21:57               ` Christoph Anton Mitterer
2006-11-09 22:02                 ` Roger Heflin
2006-11-09 22:08                   ` Christoph Anton Mitterer
2006-11-09 22:14                     ` Roger Heflin
2006-11-09 22:24                       ` Christoph Anton Mitterer
2006-11-09 22:35                         ` Roger Heflin
2006-11-09 22:38                           ` Christoph Anton Mitterer
2006-11-09 22:42                             ` Roger Heflin
2006-11-10  0:45                               ` Christoph Anton Mitterer
2006-11-10 10:28                     ` Alan Cox
2006-11-11 16:01                       ` Christoph Anton Mitterer
2006-11-09 21:03             ` Roger Heflin
2006-11-09 21:11               ` Christoph Anton Mitterer
2006-11-09 22:23   ` Christoph Anton Mitterer
2006-11-10  1:49     ` OGAWA Hirofumi
2006-11-10  2:55       ` Christoph Anton Mitterer

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=4553744E.3050007@scientia.net \
    --to=calestyo@scientia.net \
    --cc=hirofumi@mail.parknet.co.jp \
    --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