From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OBFA2-0007xk-Hc for garchives@archives.gentoo.org; Sun, 09 May 2010 22:39:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DE5D2E0801; Sun, 9 May 2010 22:39:16 +0000 (UTC) Received: from mail-qy0-f183.google.com (mail-qy0-f183.google.com [209.85.221.183]) by pigeon.gentoo.org (Postfix) with ESMTP id BCDEFE0801 for ; Sun, 9 May 2010 22:39:16 +0000 (UTC) Received: by qyk13 with SMTP id 13so5029627qyk.1 for ; Sun, 09 May 2010 15:39:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=3KDfWmGJJ7AIhAB8f+U1olN9MgpeXrBAoKh+0MlxT8E=; b=ej9FgjUxGmdiGKypfbj84BW/rl9grx/PqL2IwSDSQQ5rjBE9j/SMWafy0xjcRYkhrL jb8/DRLCpD0yk5lV76iLhOJ71fnYElhv32CM3jk4EZIqyw5P78eOpvT7vXoVUMJYh99A G5BMQtLcK1MZWmJNGA2nL7eDUqhF/uU13xsJo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=fHtikMiN6OUvh789Am7oZxbcc2TfjQxc3aGQFByCfv6VM6YFEjSxlrK//gQptuV3g8 4RV3aBicqsQ7TH3q0TG3IxVMEd1q5VRpzmwsYpQmuHpnUBdtIgrShm4AWUWR3Q5WDrj2 Ebz+PtZAuS85X08O+JRl9rYHxo80EHTY/bxu0= Received: by 10.229.227.68 with SMTP id iz4mr2462941qcb.44.1273444756206; Sun, 09 May 2010 15:39:16 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.229.97.78 with HTTP; Sun, 9 May 2010 15:39:01 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?Q?Cr=C3=ADstian_Viana?= Date: Sun, 9 May 2010 19:39:01 -0300 Message-ID: Subject: Re: [gentoo-user] Re: can't create file but disk isn't full To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=00163628498255b808048630f6ec X-Archives-Salt: 053d9922-736c-4e10-9b8c-5d4a3af174a0 X-Archives-Hash: 84bd07489eff01979f23ced62417edaa --00163628498255b808048630f6ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 wrote: > On 05/09/2010 01:46 AM, Cr=C3=ADstian 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. > > > --00163628498255b808048630f6ec Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable root can create new files! I created a big file with the remaining 17 GB lo= gged in with root. I'll run this tune2fs later, before shutting down th= e machine.

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

On Sat, May 8, 2010 at 10:48 PM, Nikos Chant= ziaras <realnc@arco= r.de> wrote:
On 05/09/2010 01:46 AM, Cr=C3=ADstian Viana wrote:
it doesn't seem so :-(

Filesystem =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Inodes =C2=A0 IUsed =C2= =A0 IFree IUse% Mounted on
/dev/sda6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A020856832 =C2=A0108698 20= 748134 =C2=A0 =C2=A01% /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. =C2=A0If yes, it probably mea= ns your reserved block count is a bit high (default is 5% I believe). =C2= =A0The 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 th= e tune2fs tool. =C2=A0To set it to, say 2%, you would run:

=C2=A0tune2fs -m 2 /dev/sda6

I don't know if it's safe to do this while the filesystem is mounte= d. To play it safe, go to single user mode, umount /home, and only then run= the above command.



--00163628498255b808048630f6ec--