[opensuse] occupied size, ext4 versus (ntfs)/ext4
Hello, I just hit a curious thing. I use two identical (bough together) external usb 5Tb drives (as archives) Fort whatever reason one was formatted EXR4 and the other kept as NTFS Wrong. The partition is tagged "microsoft", and was fuse mounted, no idea why -it's mounted at boot time or when switched on is not at boot), but now it mounts as ext4 and is ext4, fsck find it clean. I just made a rsync --delete from one to the other, verified they keep the exact same number of files (and size). but The ext4 one have 915 Gb free, the other 687 Gb wtf!! # 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%) ? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 02/12/2016 à 23:04, jdd a écrit :
same size, same occupied size, same journal size, but not same free space (by 4%)
I guess I may have some answer with this (see below). Despite being created within 3 days , the reserved block count is not the same. May be one created with yast and the other with mkfs? don't remember... linux-w4v5:~ # tune2fs -l /dev/sdd1 > sdd1.txt linux-w4v5:~ # tune2fs -l /dev/sdc1 > sdc1.txt linux-w4v5:~ # diff sdd1.txt sdc1.txt (...) < Reserved block count: 61046987 < Free blocks: 246706602 ---
Reserved block count: 1220939 Free blocks: 246706587 27c27 < Filesystem created: Fri Jan 15 08:50:36 2016
Filesystem created: Tue Jan 12 15:04:05 2016 30c30 < Mount count: 80
Mount count: 12 32c32 < Last checked: Fri Jan 15 08:50:36 2016
Last checked: Tue Jan 12 15:04:05 2016 34c34 < Lifetime writes: 1923 GB
Lifetime writes: 3302 GB
thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
Le 03/12/2016 à 11:24, Anton Aylward a écrit :
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
# df -i -Tt ext4 Sys. de fichiers Type Inœuds IUtil. ILibre IUti% Monté sur /dev/sdd1 ext4 152621056 1513942 151107114 1% (...) /dev/sdc1 ext4 152621056 1514041 151107015 1% (...)
File systems have been doing that since V7 days, a fixed pre-allocation of inodes vs data.
as you see, I don't miss inodes. Anyway, the question is why two identical disks have different free space?
ext4FS in constrained situations where I know that (a) the FS isn't going to grow suddenly.
there is only one partition on this 5Tb disk, can't grow :-) thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/03/2016 06:07 AM, jdd wrote:
ext4FS in constrained situations where I know that (a) the FS isn't going to grow suddenly.
there is only one partition on this 5Tb disk, can't grow :-)
That's not what I meant by 'grow'. I mean the number of files. Sorry I wasn't unambiguous. -- 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
participants (2)
-
Anton Aylward -
jdd