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: Fri, 3 Jul 2015 17:24:08 +0200
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <E293B208-AA72-4076-97B0-753C8680D1AE@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> <20150702112623.1c83d473@xxxxxxxxxxxxxxxxxxxx> <E293B208-AA72-4076-97B0-753C8680D1AE@xxxxxxxxxxxx>
Le Fri, 3 Jul 2015 08:27:28 +0200
Rasmus Borup Hansen <rbh@xxxxxxxxxxxx> Ãcrivait:

> Thank you for the suggestion. I compiled a new xfs_repair, but I got
> similar results from running it.
> 

Get the inode number of the faulty file, umount the volume, open it
with xfs_db and remove the file through it:

http://xfs.org/index.php/XFS_FAQ#Q:_How_to_get_around_a_bad_inode_repair_is_unable_to_clean_up

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

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