From: Nick Dokos <nicholas.dokos@hp.com>
To: Dan Carpenter <error27@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, nicholas.dokos@hp.com
Subject: Re: ext3: deleting files doesn't free up space
Date: Mon, 10 Jan 2011 01:07:37 -0500 [thread overview]
Message-ID: <18505.1294639657@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Dan Carpenter <error27@gmail.com> of "Mon, 10 Jan 2011 08:22:25 +0300." <AANLkTimwDpUz9GUmx3UutYir0UuoTSAXNzphWeEX9sKh@mail.gmail.com>
> I filled up my partition last night.
> I deleted 5 gigs of movies.
> The "Used" number went down to 125G.
> The "Free" number stayed at 0.
> I rebooted the system but it's still the same.
>
> $ echo foo > foo
> bash: echo: write error: No space left on device
>
> $ df .
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 136236548 130363620 0 100% /media/old_sys
>
> $ mount | grep old
> /dev/sda1 on /media/old_sys type ext3 (rw,nosuid,nodev)
> /media/old_sys/home on /home type none (rw,bind)
>
> This is with 2.6.37-rc5+. Is there a way to debug this?
>
I don't think there is anything to debug. ext3 reserves by default 5% of
the space for root's use. You will see "Available" go positive when
"Used" is reduced to below 0.95*136236548 blocks = 129424720 blocks
roughly. You can check your numbers by running
dumpe2fs -h /dev/sda1
and checking the "Block count" and "Reserved block count" fields.
You should be able to write to the filesystem as root though, as long
as Used < Total number of blocks. And you can adjust the reserved space
with ``tune2fs -m <N>''.
See e.g https://wiki.archlinux.org/index.php/Ext3_Filesystem_Tips
(the first hit from a Google search for "ext3 reserved").
Nick
next prev parent reply other threads:[~2011-01-10 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 5:22 ext3: deleting files doesn't free up space Dan Carpenter
2011-01-10 6:07 ` Nick Dokos [this message]
2011-01-10 6:10 ` Daniel K.
2011-01-10 7:48 ` Rogier Wolff
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=18505.1294639657@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=error27@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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