From: Dave Chinner <david@fromorbit.com>
To: Amir Soroka <amirsoroka@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS corruption - Ubuntu 14.04 VM with RDM
Date: Tue, 1 Dec 2015 09:00:39 +1100 [thread overview]
Message-ID: <20151130220039.GN26718@dastard> (raw)
In-Reply-To: <CAN9JxOBRynxTiEcsgYWKO2SVNFwdeV7gDHfZcbPb4umWXsj5DQ@mail.gmail.com>
On Mon, Nov 30, 2015 at 10:48:45PM +0200, Amir Soroka wrote:
> Hello,
> We have a corruption issue. Would be happy to get a solution.
>
> Configuration is Ubuntu 14.04 (generic) as a VM over ESXi 5.5, with 1.6 TB
> RDM - storage has a Cache battery, Raid 6, SSD disks.
Please reproduce on bare metal, and with a recent kernel.
> During some heavy indexing activity we get a corruption as you can see
> below.
Doesn't tell me anything about the workload. Please include:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> Some more information:
> * Mount options: defaults,noatime,nodiratime,nobarrier,inode64,logbufs=8 0 0
> * XFS was created like this: mkfs.xfs -f -d su=131072,sw=8 -i size=1024
> /dev/sdb1
> * Parted command was: /sbin/parted -s $i mklabel gpt mkpart /dev/sdb1 xfs
> 2048s 100%
>
>
> [ 10.395575] XFS (sdb1): Mounting V4 Filesystem
> [ 10.430107] XFS (sdb1): Ending clean mount
> [ 675.504000] XFS (sdb1): Metadata corruption detected at
> xfs_agf_read_verify+0x61/0x100 [xfs], block 0x1
There should be lots more error logging than that. Where are the
stack traces, the hex dumps, etc that go along with normal
corruption reports?
> [84997.869987] XFS (sdb1): Metadata corruption detected at
> xfs_inode_buf_verify+0x7d/0xe0 [xfs], block 0x110
There's more than one type of corruption - I'd suggest that you have
a vmware/esx level problem....
> [84997.871163] XFS (sdb1): Unmount and run xfs_repair
> [84997.871760] XFS (sdb1): First 64 bytes of corrupted metadata buffer:
> [84997.874798] XFS (sdb1): metadata I/O error: block 0x110
Yup, you've removed all the detailed corruption information in the
output. i.e. all the bits that might tell us what went wrong.
Please post the logs *in full*.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-11-30 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 20:48 XFS corruption - Ubuntu 14.04 VM with RDM Amir Soroka
2015-11-30 22:00 ` Dave Chinner [this message]
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=20151130220039.GN26718@dastard \
--to=david@fromorbit.com \
--cc=amirsoroka@gmail.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