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: Fri, 3 Jul 2015 17:24:08 +0200 [thread overview]
Message-ID: <20150703172408.52212ba6@harpe.intellique.com> (raw)
In-Reply-To: <E293B208-AA72-4076-97B0-753C8680D1AE@intomics.com>
Le Fri, 3 Jul 2015 08:27:28 +0200
Rasmus Borup Hansen <rbh@intomics.com> é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@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-07-03 15:24 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 [this message]
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=20150703172408.52212ba6@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