On Wed, Apr 09, 2008 at 11:15:24AM +0200, supersud501 wrote: > > ah ok, so i know what's up - seems i've to wait until fixing it. just > wanted to do it, because syslog said "maximum mount time reached, running > is recommended". so no need to hurry ;) That patch which I just sent out passes the regression test suite, but it hasn't been extensively tested for actual *huge* files. (Specifically, files with the EXT4_HUGE_FILE_FL because they are larger than 2TB and so i_blocks had to be specified in units of filesystem blocksize, instead of units of 512 bytes.) If you could apply the patch I just sent out and then run "e2fsck -nf /dev/sdXXX" and let me know you get, that would be much appreciated. In answer to question of how to determine if you actually *have* any large files, the simplest thing to do is to use debugfs to temporarily remove huge_file feature: debugfs -w /dev/sdXXX <------- disable the huge_file feature debugfs: features ^huge_file debugfs: quit e2fsck -nf /dev/sdXXX debugfs -w /dev/sdXXX <------- re-enable the huge_file feature debugfs: features huge_file debugfs: quit If you see error messages about i_blocks values being wrong (with the huge_file feature disabled), then the inodes that are referenced are the ones that have the huge_file flag set. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
