public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Rasmus Borup Hansen <rbh@intomics.com>
Cc: xfs@oss.sgi.com
Subject: Re: "Internal error xfs_attr3_leaf_write_verify at line 216", "directory flags set on non-directory inode" and other errors
Date: Tue, 30 Jun 2015 07:50:39 +1000	[thread overview]
Message-ID: <20150629215039.GF7943@dastard> (raw)
In-Reply-To: <FD7C5F18-48F3-461B-9604-0E3BDBB7AD69@intomics.com>

On Wed, Jun 24, 2015 at 09:39:45AM +0200, Rasmus Borup Hansen wrote:
> Hi! Yesterday I got the following error messages from the kernel (Ubuntu trusty, 3.13.0-55):
> 
> [601201.817664] ffff88016e03e000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00  ................
> [601201.818224] ffff88016e03e010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00  ..... ..........
> [601201.818827] ffff88016e03e020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
> [601201.819429] ffff88016e03e030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
> [601201.820013] XFS (dm-0): Internal error xfs_attr3_leaf_write_verify at line 216 of file /build/buildd/linux-3.13.0/fs/xfs/xfs_attr_leaf.c.  Caller 0xffffffffa00996f0

Probably fixed by commit c88547a ("xfs: fix directory hash ordering
bug"), which also affected attributes in leaf format.

> I'm currently running xfs_repair -n and so far I've seen the following output:
> 
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
>         - scan filesystem freespace and inode maps...
>         - found root inode chunk
> Phase 3 - for each AG...
>         - scan (but don't clear) agi unlinked lists...
>         - process known inodes and perform inode discovery...
>         - agno = 0
> doubling cache size to 591200
> directory flags set on non-directory inode 206624
> directory flags set on non-directory inode 206625
> directory flags set on non-directory inode 206626
> directory flags set on non-directory inode 206627
> directory flags set on non-directory inode 206628
> directory flags set on non-directory inode 206629
> directory flags set on non-directory inode 206630
> directory flags set on non-directory inode 206631
> directory flags set on non-directory inode 206632
> directory flags set on non-directory inode 206633
> directory flags set on non-directory inode 206634
> 
> Only the first 20 lines are included. There are currently 250000+
> more lines with "directory flags set on non-directory inode" and
> the check is still running (the mostly small files take up around
> 30 TB, so it'll probably take a while).

Harmless, but repair will fix it anyway.

Kernel is fixed by commit 9336e3a ("xfs: project id inheritance is a
directory only flag").

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  parent reply	other threads:[~2015-06-29 21:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  7:39 "Internal error xfs_attr3_leaf_write_verify at line 216", "directory flags set on non-directory inode" and other errors Rasmus Borup Hansen
2015-06-25 16:41 ` Emmanuel Florac
2015-06-26  6:14   ` Rasmus Borup Hansen
2015-07-02  7:58     ` Rasmus Borup Hansen
2015-07-02  9:26       ` Emmanuel Florac
2015-07-03  6:27         ` Rasmus Borup Hansen
2015-07-03 15:24           ` Emmanuel Florac
2015-07-03 23:55           ` Dave Chinner
2015-07-06 11:08             ` Rasmus Borup Hansen
2015-07-07  0:19               ` Dave Chinner
2015-07-08 10:28                 ` Rasmus Borup Hansen
2015-07-09  1:15                   ` Dave Chinner
2015-11-13  6:39                     ` Arkadiusz Bubała
2015-06-29 21:50 ` Dave Chinner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-19 13:03 Adam Błaszczykowski

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=20150629215039.GF7943@dastard \
    --to=david@fromorbit.com \
    --cc=rbh@intomics.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