From: Dmitry Panov <dmitry.panov@yahoo.co.uk>
To: xfs@oss.sgi.com
Subject: Data corruption, md5 changes on every mount
Date: Sun, 11 Dec 2011 13:21:37 +0000 [thread overview]
Message-ID: <4EE4AE61.6000306@yahoo.co.uk> (raw)
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.
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.
Analyzing the differences I found that a 4k block that should contain
all zeros sometimes contains random garbage (luckily most of the files
are pcm wavs, so it's easy to verify). However I did not analyze every
occurrence so this may be not 100% true. The files do not look as they
are sparse according to du. Interestingly one of them appears to occupy
one block more than necessary.
Then I did cp -a file newfile, mv newfile file and re-ran the test. No
problems reported since.
As there were a few unclean umounts I think most likely it is a
filesystem corruption that went unspotted by xfs_repair. It would not
surprise me too much because xfs_repair took just 3.5 min.
Any ideas? I could just copy the files and pretend noting happened but
is there a guarantee that doing so won't corrupt other data?
Best regards,
--
Dmitry Panov
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-12-11 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 13:21 Dmitry Panov [this message]
2011-12-11 23:53 ` Data corruption, md5 changes on every mount Dave Chinner
2011-12-12 0:13 ` Dmitry Panov
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=4EE4AE61.6000306@yahoo.co.uk \
--to=dmitry.panov@yahoo.co.uk \
--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