From: Dmitry Panov <dmitry.panov@yahoo.co.uk>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Data corruption, md5 changes on every mount
Date: Mon, 12 Dec 2011 00:13:40 +0000 [thread overview]
Message-ID: <4EE54734.8050603@yahoo.co.uk> (raw)
In-Reply-To: <20111211235334.GJ14273@dastard>
Hi Dave,
On 11/12/2011 23:53, Dave Chinner wrote:
> On Sun, Dec 11, 2011 at 01:21:37PM +0000, Dmitry Panov wrote:
>> Hi guys,
>>
>> I have a 2TiB XFS which is about 60% full. Recently I've noticed
>> that the daily inc. backup reports file contents change for files
>> that are not supposed to change.
> What kernel/platform? What version of xfsprogs? What kind of
> storage?
It's linux kernel 3.0.0 at the moment, however it used to run different
versions and I can't tell for sure when the problem started. xfsprogs
version is 3.1.2.
The storage is a 2 node cluster with hardware RAID1+0 and drbd.
>> I've created an LVM snapshot and ran xfs_check/xfs_repair. xfs_check
>> did report a few problems (unknown node type). After that I ran a
>> simple test: mount, calculate md5 of the problematic files, report
>> if it changed, umount, sleep 10 sec. That script reported that md5
>> sum of at least one file was changing on every cycle.
> That sounds like you've got a dodgy drive.
That would be my guess too, however the problem occurs on both nodes
(i.e. it doesn't go away when the other node becomes active) and the
same files affected which makes hard drives or RAID controller or RAM
failure very unlikely.
Is there any way to perform a more thorough check, than xfs_check does?
Best regards,
--
Dmitry Panov
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-12-12 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 13:21 Data corruption, md5 changes on every mount Dmitry Panov
2011-12-11 23:53 ` Dave Chinner
2011-12-12 0:13 ` Dmitry Panov [this message]
2011-12-12 4:15 ` Dave Chinner
2011-12-12 1:56 ` Dmitry Panov
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=4EE54734.8050603@yahoo.co.uk \
--to=dmitry.panov@yahoo.co.uk \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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