On 05/13/2010 01:56 AM, Willie Wong wrote:
On Thu, May 13, 2010 at 12:25:08AM +0200, Alex Schuster wrote:
The 5% is historical from days when disks are much smaller. If you
have a sensible partition scheme you only really need to reserve the
blocks on the $ROOT filesystem. If the partition in qu
On Thu, May 13, 2010 at 12:25:08AM +0200, Alex Schuster wrote:
> > The 5% is historical from days when disks are much smaller. If you
> > have a sensible partition scheme you only really need to reserve the
> > blocks on the $ROOT filesystem. If the partition in question (IIRC) is
> > only for /hom
Willie Wong writes:
> When the filesystem fills up, services can start failing left and
> right because they cannot write logs, cannot write temp files, etc. At
> this point human intervention is necessary: root has to log in and
> clear out the disk. But if the $ROOT filesystem is completely full
thanks! I'll set it to 0% then.
On Mon, May 10, 2010 at 12:48 PM, Willie Wong wrote:
> On Sun, May 09, 2010 at 07:39:01PM -0300, Crístian Viana wrote:
> > 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
On Sun, May 09, 2010 at 07:39:01PM -0300, Crístian Viana wrote:
> 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
> smal
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%
On 05/09/2010 01:46 AM, Crístian Viana wrote:
it doesn't seem so :-(
FilesystemInodes IUsed IFree IUse% Mounted on
/dev/sda620856832 108698 207481341% /home
I didn't know that the filesystem could run out of inodes before the
disk space itself! thanks for the in
On 05/09/2010 01:39 AM, Crístian Viana wrote:
I shutdown this computer everyday, those temp files shouldn't be alive
for months.
I ran lsof | grep deleted and it returned 132 lines, the biggest number
being 2032226 (2 MB?), belonging to the Chromium browser process. even
if every line had that v
On Sunday 09 May 2010 01:39:54 Crístian Viana wrote:
> I shutdown this computer everyday, those temp files shouldn't be alive for
> months.
>
> I ran lsof | grep deleted and it returned 132 lines, the biggest number
> being 2032226 (2 MB?), belonging to the Chromium browser process. even if
> ever
I shutdown this computer everyday, those temp files shouldn't be alive for
months.
I ran lsof | grep deleted and it returned 132 lines, the biggest number
being 2032226 (2 MB?), belonging to the Chromium browser process. even if
every line had that value (which is not), that would sum up 264 MB, b
You probably have files opened that have since been deleted. du doesn't report
them as the names are no longer in the directory and df doesn't report them as
they are pending deletion once the last handle to them is closed.
It's a nasty thing to find. Run this:
lsof | grep deleted
You should f
it doesn't seem so :-(
FilesystemInodes IUsed IFree IUse% Mounted on
/dev/sda620856832 108698 207481341% /home
I didn't know that the filesystem could run out of inodes before the disk
space itself! thanks for the information :-)
On Sat, May 8, 2010 at 4:07 PM, N
On 05/08/2010 09:21 PM, Crístian Viana wrote:
hi everyone,
something weird is happening on my system. I can't create new files, it
says "No space left on device", but the disk has several gigabytes of
free space!
The filesystem probably ran out of inodes. "df -i /home" will show
inode usage.
13 matches
Mail list logo
