search for: scratch_fil

...ves should be on a separate filesystem. To download it, please get e2fsprogs version 1.40-WIP-2007-04-11, which can be found here: http://downloads.sourceforge.net/e2fsprogs/e2fsprogs-1.40-WIP-2007-04-11.tar.gz After you build it, create an /etc/e2fsck.conf file with the following contents: [scratch_files] directory = /var/cache/e2fsck ...and then make sure /var/cache/e2fsck exists by running the command "mkdir /var/cache/e2fsck". My initial tests show that e2fsck does run approximately 25% slower with the scratch_files feature enabled, but it should use a significant smaller a...

...-2.el5.x86_64 which has a 11TB ext4 filesystem. I have problems with running fsck on it and would like to change the filesystem because I do not like the possibility of running long fsck on it, it's a production machine. Also I have some problems with running fsck (not enough RAM, problem with scratch_files option) and if the filesystem will need intervention I will be in a problematic situation. Which other mature and stable filesystem can you recommend for such large storage? Best regards, Rafal Radecki.

...nabled when the file system is initially formatted. It is not backwards compatible with older kernels. Added support for the Multi-Mount Protection (MMP) feature. E2fsck more efficiently uses scratch files for really big file systems. (This is a feature that has to be turned on explicitly; see [scratch_files] in the e2fsck.conf man page.) Fix a bug in e2fsck where if the free blocks and inodes counts are incorrect, e2fsck would fix them without printing an error message. This would cause a "*** FILE SYSTEM WAS MODIFIED ***" message without any explanation of what was fixed. E2fsck will no...

...DIFIED ***** Repeated attempts seem to get farther into repairs, but there's still a large number of repairs reported, which seems scary, and it still runs out of memory on a 128GB-memory server. I don't currently have a filesystem with more than 128GB of free space if I wanted to use the scratch_files option (though if that's really the solution, I'll make a way). The 51.8% seems very suspicious to me. A few weeks ago, I did an online resize2fs, and the original filesystem was about 52% the size of the new one (from 2.7TB to 5.3TB). The resize2fs didn't report any errors, and I...