From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com, linux-xfs@oss.sgi.com
Subject: Re: free inodes remaining in 1tb
Date: Thu, 26 Sep 2013 20:03:45 -0300 [thread overview]
Message-ID: <20130926230345.GA18765@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <44qehaxod8.ln2@goaway.wombat.san-francisco.ca.us>
On Thu, Sep 26, 2013 at 03:47:00PM -0700, Keith Keller wrote:
> Hi all,
>
> I "recently" (a few months ago) came across the inode64 entries in the
> XFS FAQ. Unfortunately, I have a filesystem not mounted with inode64,
> and I would like to know how many more inodes I can create in the
> first 1TB before I run out,
The maximum amount of the filesystem that can be used by inodes (by default)
are:
25% for filesystems under 1TB, 5% for filesystems under 50TB and 1% for
filesystems over 50TB.
>so that I can plan for a migration to
> inode64 (if it's very few, I would make it a high priority; if not, it
> can be done in a few weeks instead, for example). Is there an easy
> way (or even a hard way) to query the filesystem for this information?
>
inode64 is a remountable option now (if you're using a relatively recent
kernel), so you don't need to umount and remount it.
> I also wanted to ask about the FAQ that says you can switch back from
> inode64 to inode32. How does that work if an inode is created past the
> 1TB mark? How would the kernel know how to find an inode64 inode that
> was created beyond the 1TB mark if the filesystem is subsequentely
> mounted without inode64?
>
inode32 option only dictates where the filesystem will create next inodes, not
where it will search for already created inodes.
bear in mind though that are some applications that can't read 64bit inodes.
> Thanks,
>
> --keith
>
> --
> kkeller@wombat.san-francisco.ca.us
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-26 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 22:47 free inodes remaining in 1tb Keith Keller
2013-09-26 23:03 ` Carlos Maiolino [this message]
2013-09-27 1:08 ` Dave Chinner
2013-09-27 8:18 ` Keith Keller
2013-09-27 9:26 ` Stefan Ring
2013-09-27 12:47 ` Carlos Maiolino
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=20130926230345.GA18765@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=linux-xfs@oss.sgi.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