xfs
[Top] [All Lists]

Re: "Internal error xfs_attr3_leaf_write_verify at line 216", "directory

To: Rasmus Borup Hansen <rbh@xxxxxxxxxxxx>
Subject: Re: "Internal error xfs_attr3_leaf_write_verify at line 216", "directory flags set on non-directory inode" and other errors
From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Date: Thu, 2 Jul 2015 11:26:23 +0200
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <DBDC024E-67E6-4F11-995F-467AD085109F@xxxxxxxxxxxx>
Organization: Intellique
References: <FD7C5F18-48F3-461B-9604-0E3BDBB7AD69@xxxxxxxxxxxx> <20150625184132.773a5ecd@xxxxxxxxxxxxxxxxxxxx> <09CE9E14-9E6B-4587-9049-35B6C67016EF@xxxxxxxxxxxx> <DBDC024E-67E6-4F11-995F-467AD085109F@xxxxxxxxxxxx>
Le Thu, 2 Jul 2015 09:58:19 +0200
Rasmus Borup Hansen <rbh@xxxxxxxxxxxx> Ãcrivait:

> The file then turns up in lost+found and when I "ls" it I get the
> same errors again. I've tried deleting it from lost+found, but then
> xfs_repair finds it again with exactly the same output as show above
> and puts it back.
> 
> Apart from that, everything apparently works fine.
> 
> Is there a way to permanently get rid of the file in lost+found? Its
> size is apparently 0 bytes.

You should try the latest xfs_repair (3.2.3 IIRC) instead of the stock
Ubuntu version (3.1.x probably).

In case you don't know how to compile it, I've just uploaded it there:

http://update.intellique.com/pub/xfs_repair-3.2.3.gz

md5sum :
756a28228c7e657ce8626d27850f6261  xfs_repair-3.2.3.gz

Beware of binaries provided by strangers, however this one should be
fine :) gunzip it before use...

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

<Prev in Thread] Current Thread [Next in Thread>