public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.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: Thu, 25 Jun 2015 18:41:32 +0200	[thread overview]
Message-ID: <20150625184132.773a5ecd@harpe.intellique.com> (raw)
In-Reply-To: <FD7C5F18-48F3-461B-9604-0E3BDBB7AD69@intomics.com>

Le Wed, 24 Jun 2015 09:39:45 +0200
Rasmus Borup Hansen <rbh@intomics.com> écrivait:

> 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).
> 
> I recently enabled user and project quota and updated from 3.13.0-53.
> The file system has been heavily used for the last month or so.
> 
> Does anyone have any thoughts on this? I'm tempted to stop using
> quotas when the file system (hopefully) works again, as it's my
> impression that project quotas are not widely used.

Did you first try remounting then unmounting the volume to clear the
log? That could clear out xfs_repair output.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

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

  reply	other threads:[~2015-06-25 16:41 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 [this message]
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
  -- 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=20150625184132.773a5ecd@harpe.intellique.com \
    --to=eflorac@intellique.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