From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: "CZEH, Istvan" <iczeh@virusbuster.hu>
Subject: Re: reducing imaxpct on linux
Date: Fri, 12 Nov 2010 14:01:47 +0100 [thread overview]
Message-ID: <201011121401.52477@zmi.at> (raw)
In-Reply-To: <1289561141.20961.24.camel@sekli>
[-- Attachment #1.1: Type: Text/Plain, Size: 924 bytes --]
On Freitag, 12. November 2010 CZEH, Istvan wrote:
> What could happen if I reduce imaxpct? Is it safe or painful?
> What is really a chance that the 25% value is causing the error?
I don't believe reducing imaxpct results in more free space, because
that's the *maximum* Inodes can have.
I'm not a dev, but AFAIK the "no free space" problem comes when the
space in the first TeraByte is completely filled. I don't remember
exactly, either the FAQ tells you or look in the mailinglist archive.
The question about "no free space despite enough free" comes rather
often.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// ****** Radiointerview zum Thema Spam ******
// http://www.it-podcast.at/archiv.html#podcast-100716
//
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-12 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 11:25 reducing imaxpct on linux CZEH, Istvan
2010-11-12 13:01 ` Michael Monnerie [this message]
[not found] ` <1289571841.20961.44.camel@sekli>
2010-11-12 15:18 ` Michael Monnerie
2010-11-12 22:42 ` Eric Sandeen
2010-11-13 15:06 ` Michael Monnerie
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=201011121401.52477@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=iczeh@virusbuster.hu \
--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.