Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
I can't understand the output. Whereas ls shows no more than 4MB in /SDA6, df tells me I am using 74MB. mount's output is as follows:
Code:
root@server:~# mount
/dev/sda2 on / type ext2 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /xp type fuseblk (rw,allow_other,blksize=4096)
gvfs-fuse-daemon on /home/semoi/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=semoi)
/dev/sda6 on /SDA6 type ext2 (rw)
root@server:~#
By default, blocks are assigned to the "resize inode" (inode 7) so that the block descriptor table can grow in the future. These blocks are considered "used" by df, but will not show up as assigned to any file. You can verify that usage by running "debugfs /dev/sda6" and typing "stat <7>" at the "debugfs: " prompt, e.g.:
The e2fsck is necessary because tune2fs just clears the feature's bit in the super block. The actual work is done by e2fsck. Note that once you have turned off this feature, you cannot turn it back on again without re-making the filesystem.
By default, blocks are assigned to the "resize inode" (inode 7) so that the block descriptor table can grow in the future. These blocks are considered "used" by df, but will not show up as assigned to any file. You can verify that usage by running "debugfs /dev/sda6" and typing "stat <7>" at the "debugfs: " prompt, e.g.:
The e2fsck is necessary because tune2fs just clears the feature's bit in the super block. The actual work is done by e2fsck. Note that once you have turned off this feature, you cannot turn it back on again without re-making the filesystem.
I understand. The first quantity is 4.2GB and the second one only 0.2GB. I'll see what the data I get are. Thank you.
Oops. Looking at it again, I'm not sure just what to make of that "Size" value, and the "Blockcount" value appears to be in 512-byte sectors. I should have looked at the numbers more closely.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.