<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Eric Sandeen <sandeen@sandeen.net></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">Adam Donald <Adam.Donald@gencopharma.com></font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">xfs@oss.sgi.com</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">06/29/2009 02:39 PM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: Correct usage of inode64/running
out of inodes</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Adam Donald wrote:<br>
> <br>
> Hello<br>
> <br>
> In short, I believe that I have used the indode64 option correctly
in<br>
> mounting my XFS device on my Centos 5.2 system, however, I seem to
only<br>
> have 59 free inodes available and 7.5TB of free space. I would<br>
> appreciate any insight as to what the best approach would be to fix
this<br>
> situation. In case it is helpful, I have included output from
various<br>
> commands/files below, the XFS device in question is<br>
> /dev/mapper/VolGroup01-DATA01. Thank you in advance for your
assistance!<br>
<br>
It all looks sane to me; what are the actual symptoms of the problem<br>
You can create 59 files and then -ENOSPC? Any kernel messages?<br>
<br>
Maybe this is a bug in the old xfs code in the centos module... though
I<br>
don't remember such a bug right now.s<br>
<br>
-Eric<br>
<br>
> uname:<br>
> Linux NAS01 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:45:47 EDT 2008
x86_64<br>
> x86_64 x86_64 GNU/Linux<br>
> <br>
> df -h:<br>
> Filesystem
Size Used Avail Use% Mounted
on<br>
> /dev/mapper/VolGroup00-LogVol00 71G
12G 55G 18% /<br>
> /dev/sda1
99M 25M 70M
26% /boot<br>
> tmpfs
3.9G 0 3.9G
0% /dev/shm<br>
> /dev/mapper/VolGroup01-DATA01 18T
9.9T 7.5T 57% /DATA01<br>
> <br>
> df -ih:<br>
> Filesystem
Inodes IUsed IFree IUse%
Mounted on<br>
> /dev/mapper/VolGroup00-LogVol00 19M
123K 19M 1% /<br>
> /dev/sda1
26K 44
26K 1% /boot<br>
> tmpfs
999K
1 999K 1% /dev/shm<br>
> /dev/mapper/VolGroup01-DATA01 18G
297K 18G 1% /DATA01<br>
> <br>
> mount:<br>
> ...<br>
> /dev/mapper/VolGroup01-DATA01 on /DATA01 type xfs (rw,inode64)<br>
> ...<br>
> <br>
> fstab:<br>
> ...<br>
> /dev/VolGroup01/DATA01 /DATA01
xfs <br>
> rw,suid,dev,exec,auto,nouser,async,inode64 1 0<br>
> ...<br>
</font></tt>
<br><tt><font size=2>Thank you for your response. To be honest, I
only ran out of "space" (inodes) once on this volume a month
or so ago, and I recall receiving a ENOSPC type error at that time. At
the time I received out of space errors I found the xfs_db command and
have since started to monitor the ifree value, deleting files when I felt
that ifree was dipping too low, as I was unable to apply the inode64 option
without first taking down various production systems. When the time
came this past weekend to apply the inode64 option, I was expecting the
ifree option value to shoot up dramatically (several hundred, perhaps),
and instead the ifree value remained unaffected, the same as mounting the
volume without the inode64 option. </font></tt>
<br>
<br><tt><font size=2>Given the fact that I have this volume mounted with
the inode64 option, have roughly 7.5TB free, and show ifree with a double
digit number (currently 30 on our system), is there a an inconsistency
between the total amount of free space available and the number of free
inodes available?</font></tt>
<br>
<br><tt><font size=2>Thanks again for the input, I appreciate it!</font></tt>
<br>
<br>
<br><tt><font size=2>AD</font></tt>
<br>
<BR>
______________________________________________________________________<BR>
This email has been scanned by the MessageLabs Email Security System.<BR>
For more information please visit http://www.messagelabs.com/email <BR>
______________________________________________________________________<BR>