From: Dave Chinner <david@fromorbit.com>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: xfs@oss.sgi.com
Subject: Re: strange behavior of a larger xfs directory
Date: Wed, 6 Mar 2013 11:57:45 +1100 [thread overview]
Message-ID: <20130306005744.GA4549@dastard> (raw)
In-Reply-To: <1517139.CltWl8VXzZ@xrated>
On Wed, Mar 06, 2013 at 12:48:25AM +0100, Hans-Peter Jansen wrote:
> Am Mittwoch, 6. März 2013, 09:29:41 schrieb Dave Chinner:
> > On Tue, Mar 05, 2013 at 09:32:02PM +0100, Hans-Peter Jansen wrote:
> > attr_list and attr_multi are supplied by libattr, you should not
> > need the *by_handle variants at all - they are special sauce used by
> > xfsdump, not xfs_reno....
>
> Ahh, I see. These interfaces cannot be exercised much, given that google
> didn't relate them to libattr prominently..
Attributes are not widely used by applications for some reason...
> Hmm, any idea on how xfs can be tricked into generating 64 bit inodes without
> the need to create an excessive big test fs, or is this an accepted practice?
The usual trick is to use a sparse loopback device and create the
filesystem on that. see, for example, xfstests 078, where it is
testing growfs on filesystems up to 16TB in size on a loopback
device...
> Note to myself: xfs_reno could use some mount option check. Forgot to remount
> one partition with inode32 and, consequently, moved the offending inodes to
> another 64 bit value..
I'd just use a wrapper script that checked /proc/mounts for the
inode64 flag being set first....
....
> Index: b/configure.ac
> ===================================================================
> --- a/configure.ac
> +++ b/configure.ac
....
The patch looks sane - can you add a commit description and s
Signed-off-by line to it, and then we can use it directly....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-03-06 0:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 16:40 strange behavior of a larger xfs directory Hans-Peter Jansen
2013-03-04 22:55 ` Hans-Peter Jansen
2013-03-04 23:18 ` Dave Chinner
2013-03-04 23:05 ` Dave Chinner
2013-03-05 20:32 ` Hans-Peter Jansen
2013-03-05 22:29 ` Dave Chinner
2013-03-05 23:48 ` Hans-Peter Jansen
2013-03-06 0:57 ` Dave Chinner [this message]
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=20130306005744.GA4549@dastard \
--to=david@fromorbit.com \
--cc=hpj@urpla.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.