public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Adam Donald <Adam.Donald@gencopharma.com>
Cc: xfs@oss.sgi.com
Subject: Re: Correct usage of inode64/running out of inodes
Date: Mon, 29 Jun 2009 14:39:51 -0500	[thread overview]
Message-ID: <4A491887.8050509@sandeen.net> (raw)
In-Reply-To: <OF97A83ACB.604AE440-ON862575E4.00450F9F-862575E4.00475C94@genco.com>

Adam Donald wrote:
> 
> Hello
> 
> In short, I believe that I have used the indode64 option correctly in
> mounting my XFS device on my Centos 5.2 system, however, I seem to only
> have 59 free inodes available and 7.5TB of free space.  I would
> appreciate any insight as to what the best approach would be to fix this
> situation.  In case it is helpful, I have included output from various
> commands/files below, the XFS device in question is
> /dev/mapper/VolGroup01-DATA01.  Thank you in advance for your assistance!

It all looks sane to me; what are the actual symptoms of the problem
You can create 59 files and then -ENOSPC?  Any kernel messages?

Maybe this is a bug in the old xfs code in the centos module... though I
don't remember such a bug right now.s

-Eric

> uname:
> Linux NAS01 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:45:47 EDT 2008 x86_64
> x86_64 x86_64 GNU/Linux
> 
> df -h:
> Filesystem                            Size  Used Avail Use% Mounted on
> /dev/mapper/VolGroup00-LogVol00        71G   12G   55G  18% /
> /dev/sda1                              99M   25M   70M  26% /boot
> tmpfs                                 3.9G     0  3.9G   0% /dev/shm
> /dev/mapper/VolGroup01-DATA01          18T  9.9T  7.5T  57% /DATA01
> 
> df -ih:
> Filesystem                          Inodes   IUsed   IFree IUse% Mounted on
> /dev/mapper/VolGroup00-LogVol00        19M    123K     19M    1% /
> /dev/sda1                              26K      44     26K    1% /boot
> tmpfs                                 999K       1    999K    1% /dev/shm
> /dev/mapper/VolGroup01-DATA01          18G    297K     18G    1% /DATA01
> 
> mount:
> ...
> /dev/mapper/VolGroup01-DATA01 on /DATA01 type xfs (rw,inode64)
> ...
> 
> fstab:
> ...
> /dev/VolGroup01/DATA01  /DATA01                 xfs    
> rw,suid,dev,exec,auto,nouser,async,inode64      1 0
> ...

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-06-29 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 12:59 Correct usage of inode64/running out of inodes Adam Donald
2009-06-29 19:39 ` Eric Sandeen [this message]
2009-06-29 20:35   ` Adam Donald
2009-06-29 20:44     ` Eric Sandeen
2009-06-30 20:08       ` Adam Donald

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=4A491887.8050509@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=Adam.Donald@gencopharma.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