public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Crístian Viana" <cristiandeives@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: can't create file but disk isn't full
Date: Sun, 9 May 2010 19:39:01 -0300	[thread overview]
Message-ID: <m2g92ad22481005091539g946a689fha6ca75839c101894@mail.gmail.com> (raw)
In-Reply-To: <hs5498$cuf$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]

root can create new files! I created a big file with the remaining 17 GB
logged in with root. I'll run this tune2fs later, before shutting down the
machine.

what exactly is this reserved block count? is it about the number of inodes?
does that mean that, by default, regular users can only use 95% of the
inodes? and why did I use all these inodes? I don't think I have that many
small files on this partition...

On Sat, May 8, 2010 at 10:48 PM, Nikos Chantziaras <realnc@arcor.de> wrote:

> On 05/09/2010 01:46 AM, Crístian Viana wrote:
>
>> it doesn't seem so :-(
>>
>> Filesystem            Inodes   IUsed   IFree IUse% Mounted on
>> /dev/sda6            20856832  108698 20748134    1% /home
>>
>> I didn't know that the filesystem could run out of inodes before the
>> disk space itself! thanks for the information :-)
>>
>
> Long shot, but check if root can write files.  If yes, it probably means
> your reserved block count is a bit high (default is 5% I believe).  The
> reserved block count is a mechanism that disallows further writes to the
> filesystem if it gets too full, and only root can keep writing.
>
> If that's your problem, the reserved block count can be changed with the
> tune2fs tool.  To set it to, say 2%, you would run:
>
>  tune2fs -m 2 /dev/sda6
>
> I don't know if it's safe to do this while the filesystem is mounted. To
> play it safe, go to single user mode, umount /home, and only then run the
> above command.
>
>
>

[-- Attachment #2: Type: text/html, Size: 1947 bytes --]

  reply	other threads:[~2010-05-09 22:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-08 18:21 [gentoo-user] can't create file but disk isn't full Crístian Viana
2010-05-08 18:32 ` Volker Armin Hemmann
2010-05-08 19:07 ` [gentoo-user] " Nikos Chantziaras
2010-05-08 22:46   ` Crístian Viana
2010-05-08 23:00     ` Alan McKinnon
2010-05-08 23:39       ` Crístian Viana
2010-05-09  0:07         ` Alan McKinnon
2010-05-09  1:17         ` Johannes Kimmel
2010-05-09  1:48     ` Nikos Chantziaras
2010-05-09 22:39       ` Crístian Viana [this message]
2010-05-10 15:48         ` Willie Wong
2010-05-11  3:15           ` Crístian Viana
2010-05-12 22:25           ` Alex Schuster
2010-05-12 22:56             ` Willie Wong
2010-05-12 23:37               ` Nikos Chantziaras

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=m2g92ad22481005091539g946a689fha6ca75839c101894@mail.gmail.com \
    --to=cristiandeives@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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