From: Dave Chinner <david@fromorbit.com>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: bug? "directory flags set on non-directory inode 2877105"
Date: Thu, 5 Jul 2012 07:23:10 +1000 [thread overview]
Message-ID: <20120704212310.GJ19223@dastard> (raw)
In-Reply-To: <201207041759.05259.arekm@maven.pl>
On Wed, Jul 04, 2012 at 05:59:05PM +0200, Arkadiusz Miśkiewicz wrote:
>
> Hi.
>
> On two servers using 3.0.x kernels I've got like 10 mln of "directory flags
> set on non-directory inode xxx" errors when doing xfs_repair. Doesn't look
> like a corruption issue, right?
Can you run a xfs_io stat command on one ofthe files so we can see
what flag is set? i.e.
$ xfs_io -c stat $file
> Was there a bug in 2.6.3x or 3.0.x kernels that could get these flags set in
> such wrong way?
Not that I know of.
> ps. using project quota on both servers/fses
Which makes me think that the project quota inheritance flag has
been recursively set on all files, not just directories. The code
allows that to occur, even though it only has meaning for directory
inodes. If this is the case, then the above warning and removal of
the flag is harmless.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-04 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 15:59 bug? "directory flags set on non-directory inode 2877105" Arkadiusz Miśkiewicz
2012-07-04 21:23 ` Dave Chinner [this message]
2012-07-05 8:36 ` Arkadiusz Miśkiewicz
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=20120704212310.GJ19223@dastard \
--to=david@fromorbit.com \
--cc=arekm@maven.pl \
--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