-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID: <alpine.LSU.2.20.1608011420580.18210@xxxxxxxxxxxxxxxxxxxx>
El 2016-08-01 a las 15:00 +0300, Lista Unx escribiÃ:
El 2016-07-30 a las 09:35 +1000, Dave Chinner escribiÃ:
That is, inodes are dynamically allocated so the number of supported
inodes is directly proportional to the amount of free space left in
the filesystem. You have filesystems with different amounts
NO! Booth systems are almost identical (minor differencies) and this has been
stated very clear on my first post. That's not necessary to comment each line
in my post, just to point us in the right direction.
They are identical, except that one has free space and the other does
not.
Number of inodes is dynamic and associated to free space. No free space,
thus, almost no inodes available. One thing follows from the other.
That's probably because there are open but unlinked files present in
the filesystem, and du will not find them. e.g. large O_TMPFILE
files, or files that applications are using as scratch space. You
may even have zombie processes hanging about holding unlinked files
open.
Has been mentioned on my first post, reboot does not solve problem,
there are no (large, small or any kind of files)
exahusting inodes!
Dave refers to a unix/linux "feature". Files can be deleted, but if
they are in use at the time, the contents are not deleted. Disk shows an
ammount of free space that does not match the total - used space.
However, a reboot clears this situation, and you did say in the original
post you had rebooted the system.
- --
Cheers
Carlos E. R.
(from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlefP00ACgkQja8UbcUWM1xEEQD+P6UaCgpP4L/ZES7wmVBBgLib
Rx78tVXJJKE5+FCQAY8BAI+6boqtqicVZA3PeOYM8PCa9IrRKyHffx3l5ty0LKpI
=h9xF
-----END PGP SIGNATURE-----
|