public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Huszár Viktor Dénes" <hvd@dwo.hu>
To: 'Emmanuel Florac' <eflorac@intellique.com>, xfs@oss.sgi.com
Subject: RE: free space problem
Date: Thu, 29 May 2008 12:20:49 +0200	[thread overview]
Message-ID: <20080529102107.73D6D1CA6D0@cuda.sgi.com> (raw)
In-Reply-To: <20080331093951.100ec125@galadriel.home>

Okay guys, we figured out what is the real problem with the xfs, I just need
your help now.

Currently our server has an 880448 number as icount, which we figured out
like this:

xfs_db -r -c sb -c p /dev/a/a | egrep icount\|ifree
icount = 880448
ifree = 0

although df -i sates this:

df -i
Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/md0                5.3M    301K    5.0M    6% /
tmpfs                   2.0M       5    2.0M    1% /lib/init/rw
udev                    2.0M     475    2.0M    1% /dev
tmpfs                   2.0M       1    2.0M    1% /dev/shm
/dev/mapper/a-a          60M    860K     59M    2% /var/www/users

If we delete a file ifree is going to be 1. if we delete 200 files, ifree
becomes 200 so there is an obvious relationship here. If ifree is 0, we can
not upload anymore.

So the question is: how can we increase the icount without formatting the
partition?

Please help!! Thank you in advance,

Viktor

-----Original Message-----
From: Emmanuel Florac [mailto:eflorac@intellique.com] 
Sent: Monday, March 31, 2008 9:40 AM
To: Huszár Viktor Dénes; xfs@oss.sgi.com
Subject: Re: free space problem

Le Mon, 31 Mar 2008 02:31:16 +0200 vous écriviez:

> There is nothing extraordinary in it, you can see umount-mount and
> that it was mounted after all xfs activity (check, repair, db).

Then maybe you simply ran out of inodes. It's common if you have lots
of small files. There is a way to increase the number of inodes but I
don't remember it right now.

-- 
--------------------------------------------------
Emmanuel Florac               www.intellique.com   
--------------------------------------------------


__________ Information from ESET NOD32 Antivirus, version of virus signature
database 2986 (20080331) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3143 (20080529) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 

  parent reply	other threads:[~2008-05-29 10:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080331093951.100ec125@galadriel.home>
2008-03-31 17:36 ` free space problem Huszár Viktor Dénes
2008-04-01  0:35   ` David Chinner
2008-04-01  3:08     ` Huszár Viktor Dénes
2008-04-06 16:09     ` Huszár Viktor Dénes
2008-04-06 16:26       ` KELEMEN Peter
2008-04-06 16:38         ` Huszár Viktor Dénes
2008-04-07  2:18       ` David Chinner
2008-05-29 10:20 ` Huszár Viktor Dénes [this message]
2008-05-29 10:29   ` Emmanuel Florac
2008-05-29 10:55     ` Emmanuel Florac
2008-05-29 13:26       ` Huszár Viktor Dénes
2008-05-29 14:57         ` Dave Chinner
2008-05-29 17:37           ` Huszár Viktor Dénes
     [not found]       ` <20080529132624.19286105D9@mailwash5.pair.com>
2008-05-29 13:30         ` Emmanuel Florac
2008-03-30 20:29 Huszár Viktor Dénes
2008-03-30 21:54 ` Emmanuel Florac
2008-03-31  0:31   ` Huszár Viktor Dénes
2008-03-31  0:38 ` David Chinner
2008-03-31 17:43   ` Huszár Viktor Dénes

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=20080529102107.73D6D1CA6D0@cuda.sgi.com \
    --to=hvd@dwo.hu \
    --cc=eflorac@intellique.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