DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=Pr5ZJWwTv2xee7AOnOXbQFVm1YQN2fR4fiZVf4rnGZyyCkw9jfXY6Tubt6cn8WmhZcd/eYqjKjwUpliHijvfGU2e/hFcLm3L6XOTmp2bjcojewVUK7FlfmSs4FHbxNMSnx85BBLlGcUVN5JeLQ77+yVaUqqfBgtr7joEQc8RCNg=;
Message-ID: <1338992680.29947.YahooMailNeo@web122006.mail.ne1.yahoo.com>
Date: Wed, 6 Jun 2012 07:24:40 -0700 (PDT)
From: Bob Sullivan <bobsullivan60@yahoo.com>
Reply-To: Bob Sullivan <bobsullivan60@yahoo.com>
Subject: file corruption in loop device in 3.4.0
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1006
Lines: 21

We have a EXT3 filesystem contained in a file
(a disk image mapped to a file using loop device).
Using diff, observed random differences between
files on the image and a backup copies of those files.
This problem is reproducible,
tried booting several times with 3.3.8 and 3.4.0.
No problems on 3.3.8.
But every time on 3.4.0, randomly a few files showed corruption.
Some files that were corrupt become ok again after rebooting/remounting.
About 5% of the file contents was garbage, rest was correct, the file size was correct.

Seems to be a memory problem in 3.4.0?
chkdsk never showed any problem (in the disk image file).

Using Debian 6.? Ran memtest86+, chkdsk, badblocks -- no errors.
Disk image was created mkfs.ext3 with the smallest inode/block size.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/