public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: xfs@oss.sgi.com
Cc: g.danti@assyoma.it
Subject: LVM snapshot and log record CRC mismatch
Date: Tue, 24 May 2016 14:58:51 +0200	[thread overview]
Message-ID: <ab81e19cd6fce41f9d63cdd3695c80f7@assyoma.it> (raw)

Hi list,
I have a question about LVM snapshot and XFS.

Some preliminary information: CentOS Linux release 7.0.1406 (Core), with 
kernel version 3.10.0-123.20.1.el7.x86_64

Basically, each time I mount a LVM snapshot (with the "nouuid" option), 
I have the following dmesg entries:

[824501.391058] XFS (dm-7): Mounting Filesystem
[824502.085459] XFS (dm-7): Starting recovery (logdev: internal)
[824502.120435] XFS (dm-7): log record CRC mismatch: found 0x324293f8, 
expected 0x43a1b3b5.
[824502.121035] ffffc90018271000: 00 00 00 10 00 00 00 00 69 01 00 00 6d 
a0 9d a7  ........i...m...
[824502.121649] ffffc90018271010: 00 00 00 10 69 00 00 00 4e 41 52 54 2a 
00 00 00  ....i...NART*...
[824502.122403] XFS (dm-7): log record CRC mismatch: found 0x873f6b2, 
expected 0x49045c16.
[824502.122952] ffffc90018271000: 00 00 00 10 00 00 00 08 aa 20 00 00 6e 
55 00 00  ......... ..nU..
[824502.123508] ffffc90018271010: 00 00 00 00 69 00 00 00 4e 41 52 54 2a 
00 00 00  ....i...NART*...
[824502.124239] XFS (dm-7): log record CRC mismatch: found 0x2f6e47af, 
expected 0x7efb222.
[824502.124792] ffffc90018271000: 00 00 00 10 00 00 00 00 69 01 00 00 a7 
66 d7 2e  ........i....f..
[824502.125359] ffffc90018271010: 00 00 00 10 69 00 00 00 4e 41 52 54 2a 
00 00 00  ....i...NART*...
[824502.126173] XFS (dm-7): log record CRC mismatch: found 0x324293f8, 
expected 0x43a1b3b5.
[824502.126751] ffffc900182b2000: 00 00 00 10 00 00 00 00 69 01 00 00 6d 
a0 9d a7  ........i...m...
[824502.127332] ffffc900182b2010: 00 00 00 10 69 00 00 00 4e 41 52 54 2a 
00 00 00  ....i...NART*...
[824502.153510] XFS (dm-7): log record CRC mismatch: found 0x873f6b2, 
expected 0x49045c16.
[824502.154158] ffffc900182b2000: 00 00 00 10 00 00 00 08 aa 20 00 00 6e 
55 00 00  ......... ..nU..
[824502.154818] ffffc900182b2010: 00 00 00 00 69 00 00 00 4e 41 52 54 2a 
00 00 00  ....i...NART*...
[824502.155654] XFS (dm-7): log record CRC mismatch: found 0x2f6e47af, 
expected 0x7efb222.
[824502.156258] ffffc900182b2000: 00 00 00 10 00 00 00 00 69 01 00 00 a7 
66 d7 2e  ........i....f..
[824502.156869] ffffc900182b2010: 00 00 00 10 69 00 00 00 4e 41 52 54 2a 
00 00 00  ....i...NART*...
[824502.906702] XFS (dm-7): Ending recovery (logdev: internal)
[824502.906714] SELinux: initialized (dev dm-7, type xfs), uses xattr

 From my understanding, this should be more or less the expected 
behavior: the snapshot is a "crash consistent" backup point, and 
mounting the snapshotted filesystem can led to mismatched CRC. Anyway, I 
can read from the snapshot without problems.

However, issuing a xfs_info on the original volume shows that crc 
options is 0 (crc=0), so I am somewhat puzzled about the warning above. 
Moreover, on a more recent CentOS 7.2 server (kernel version 
3.10.0-327.13.1.el7.x86_64), I can not reproduce this warning.

So I ask:
1) it really is the expected behavior, or should I be worried by the 
dmesg entries?
2) this is kernel-related, should I update the kernel to newer version?

Thanks.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2016-05-24 12:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 12:58 Gionatan Danti [this message]
2016-05-24 22:12 ` LVM snapshot and log record CRC mismatch Dave Chinner
2016-05-25  7:37   ` Gionatan Danti
2016-05-26 10:23     ` Emmanuel Florac
2016-05-26 11:17       ` Gionatan Danti
2016-05-26 11:34         ` Emmanuel Florac
2016-05-30  6:33           ` Gionatan Danti
2016-05-26 17:39         ` Eric Sandeen

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=ab81e19cd6fce41f9d63cdd3695c80f7@assyoma.it \
    --to=g.danti@assyoma.it \
    --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