On 12/02/2016 05:04 PM, jdd wrote:
# df -h
/dev/sdc1 4,6T 3,6T 709G 84% /run/media/jdd/intenso5to2 /dev/sdi1 4,6T 3,6T 937G 80% /run/media/jdd/intenso5to
same size, same occupied size, same journal size, but not same free space (by 4%)
'df -i' will tell you the number of inodes - created/used/free That is the number not merely %age. The mkfs.ext4 is affected by /etc/mke2fs.conf one of the reasons I don't like ext4 is that is does this stupid provisioning. File systems have been doing that since V7 days, a fixed pre-allocation of inodes vs data. It doesn't have to be like that. The allocation can be done dynamically "on demand" and is with the other b-tree file systems, ReiserFS, BtrFS, XFS. The ting is that ext4Fs is a b-tree fs for space allocation and is in other ways a damn fine file system. It performs excellent for most use cases. But in this one respect its no better than the V7FS of 1980 vintage. I've been bitten a couple of times by this pre-allocation idiocy and only use ext4FS in constrained situations where I know that (a) the FS isn't going to grow suddenly. The way I have my system partitioned with separate /tmp, separate /usr/share, separate /var, separate /srv I am reasonably confident that my RootFS isn't going to suddenly grow. Oh, well, its actually BtrFS with snapshot turned off :-) I'm not THAT confident! and I do have plenty of free space on it. Shows you how much I trust ext4! Perhaps ext5 will address this problem. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org