No more free space! df 99.9%, du 29% usage - missing free space ?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Reserved block count? As in 'tune2fs -l /dev/sda1|grep -i block;' standard five per cent of the partitions size. Can be lowered with 'tune2fs -m n' but read 'man tune2fs' first.
tune2fs -l /dev/sda
tune2fs 1.36 (05-Feb-2005)
tune2fs: Bad magic number in super-block while trying to open /dev/sda
Couldn't find valid filesystem superblock.
Already post, that tune2fs is not compatible with ReiserFS
Wikipedia:
Quote:
Some Unix-style file systems such as ReiserFS omit an inode table, but must store equivalent data in order to provide equivalent capabilities. The data may be called stat data, in reference to the stat system call that provides the data to programs.
Filesystem state: consistency is not checked after last mounting
Reiserfs super block in block 16 on 0x801 of format 3.6 with standard journal
Count of blocks on the device: 7323616
Number of bitmaps: 224
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 425459
Root block: 11270
Filesystem is NOT clean
Tree height: 5
Hash function used to sort names: "r5"
Objectid map size 594, max 972
Journal parameters:
Device [0x0]
Magic [0x292b00bd]
Size 8193 blocks (including 1 for journal header) (first block 18)
Max transaction length 1024 blocks
Max batch size 900 blocks
Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0:
sb_version: 2
inode generation number: 15651833
UUID: 0a9b77a6-ed65-47be-b032-08078232fc12
LABEL:
Set flags in SB:
ATTRIBUTES CLEAN
I'd still like to see if anything changes if you examine the disk from a live CD - without even any files open for read.
"Filesystem is NOT clean" presumably just means it's mounted rw. But fsck it from a live CD anyway.
If you have a spare HDD (and plenty of spare time), doing a deep copy of the entire volume to another identically sized and formatted volume might be instructive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.