I deleted a big extended partition   containing an  ntfs  logical partition with high percentage of occupied space  and  from that extended partition  I made a new, smaller extended part. In it  I created an ext4 logical partition .The newly created ext4 logical partition however comes with 1.75 GB already occupied. I have tried deleting and recreating the partition  but the occupied space just keeps coming back. I did the following to search for clues but no joy.sudo du -h -s /media/hrmount/20K /media/hrmount/andsudo du -h -a /media/hrmount16K /media/hrmount/lost+found20K /media/hrmount/and sudo du -h -a /media/hrmount/lost+found/16K /media/hrmount/lost+found/the commands might seem redundant but I'm just blindly trying to figure this out.I also ran :fsck -V /dev/sdb5fsck from util-linux 2.20.1[/sbin/fsck.ext4 (1) -- /media/hrmount] fsck.ext4 /dev/sdb5 e2fsck 1.42 (29-Nov-2011)/dev/sdb5: clean, 11/6553600 files, 459349/26214400 blocksand the relevant output from df -h/dev/sdb5       100G  1.7G   94G   2% /media/hrmountI am quite sure that I will get rid of that occupied space by formatting the partition but what i want to know is what is causing that occupied space in also what it actually contains. Please help me find more clues to solve this puzzle. Thank you.
What is this data that keeps reappearing after partition delete + new partition creation?
filesystems;disk usage;ext4;gparted
The used space reported by df is reserved space. This reserved space is used by ext filesystems to prevent data fragmentation as well as to allow critical applications such as syslog to continue functioning when the disk is full. You can view information about the reserved space using the tune2fs command:# tune2fs -l /dev/mapper/newvg-root tune2fs 1.42.5 (29-Jul-2012)Filesystem volume name:   <none>Last mounted on:          /mnt/oldrootFilesystem UUID:          d41eefc5-60d6-4e18-98e8-d08d9111fbe0Filesystem magic number:  0xEF53Filesystem revision #:    1 (dynamic)Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isizeFilesystem flags:         signed_directory_hash Default mount options:    (none)Filesystem state:         cleanErrors behavior:          ContinueFilesystem OS type:       LinuxInode count:              3932160Block count:              15728640Reserved block count:     786304Free blocks:              11086596Free inodes:              3312928First block:              0Block size:               4096Fragment size:            4096Reserved GDT blocks:      1020Blocks per group:         32768Fragments per group:      32768Inodes per group:         8192Inode blocks per group:   512Flex block group size:    16Filesystem created:       Tue Feb  8 16:28:29 2011Last mount time:          Mon Dec  9 23:28:11 2013Last write time:          Mon Dec  9 23:48:24 2013Mount count:              19Maximum mount count:      20Last checked:             Tue Sep  3 23:00:06 2013Check interval:           15552000 (6 months)Next check after:         Sun Mar  2 22:00:06 2014Lifetime writes:          375 GBReserved blocks uid:      0 (user root)Reserved blocks gid:      0 (group root)First inode:              11Inode size:               256Required extra isize:     28Desired extra isize:      28Journal inode:            8Default directory hash:   half_md4Directory Hash Seed:      80cf2748-584a-4fe8-ab8c-6abff528c2c2Journal backup:           inode blocksHere you can see that 786304 blocks are reserved and the block size is 4096. This means that 3220701184 bytes or 3GB is reserved. You can adjust the percentage of reserved blocks using the tune2fs commands (but is not recommended):tune2fs -m 1 /dev/sdb5