Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Are you talking about the size of the partition itself or the disk space on the partition?
If disk space, a lot of MB can be used up in /tmp and also in /var/log
Your distro may be doing many other things behind your back as well that take up space...
I suspect it is df that is giving different approximate values, as provided by the RAID controller.
When you create a file it will have a file size (number of bytes in the file), and a space on disk occupied. The amount of space taken will be equal or greater than the size of the file, dependant upon the block size.
For example with a block size of 512 bytes, that amount of space will always be taken up. E.g. for a 600 byte file, it will require two blocks and take up 1024 bytes on the disk.
I suspect that the RAID controller is returning a different number of blocks to take account of the partial used blocks. This would only be noticeable on a filesystem with a large number of small files, which may be the case for a var filesystem.
An alternative theory could be that the RAID controller is returning lower values as it is finding bad blocks on the disk. As this is a hardware RAID any bad block detection will be done outside of the OS, and so may not be reported by fsck. You would need to interrogate the hardware controller to see if there are bad blocks being detected, or it may be that these are logged in the syslog.
The particulary system is running a cyrus pop3/imap server, so yes it is a lot of small files.
The size of the partition it self have been 100% stable on the same size for the last 6 months... only recently thease have changed to the current value.
I will check my syslog and consult my raid controllers documentation for how it handle disk errors
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.