Re: "Internal error xfs_attr3_leaf_write_verify at line 216", "directory flags set on non-directory inode" and other errors

[Rasmus Borup Hansen <rbh@xxxxxxxxxxxx>]

I tried mounting the file system read-only (which triggered a quota check â does this make sense when the file system is read-only?) and then I scanned the file system for files with the spurious inodes to see if I could find a pattern. This took quite a while, and I didn't find any patterns, except that all the files in directories with project quotas were affected (but there were also other files). I'm now running xfs_repair without -n (and I had to mount and unmount the file system before it would start). I'll report back when it has finished.

Best,

Rasmus

Intomics is a contract research organization specialized in deriving core biological insight from large scale data. We help our clients in the pharmaceutical industry develop tomorrow's medicines better, faster, and cheaper through optimized use of biomedical data.

-----------------------------------------------------------------

Hansen, Rasmus Borup              Intomics - from data to biology

System Administrator              Diplomvej 377

Scientific Programmer             DK-2800 Kgs. Lyngby

                                  Denmark

E: rbh@xxxxxxxxxxxx               W: http://www.intomics.com/

P: +45 5167 7972                  P: +45 8880 7979

On 25 Jun 2015, at 18:41, Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> wrote:

Le Wed, 24 Jun 2015 09:39:45 +0200
Rasmus Borup Hansen <rbh@xxxxxxxxxxxx> Ã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@xxxxxxxxxxxxxx>
                   |   +33 1 78 94 84 02
------------------------------------------------------------------------

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