I've also noted a very interesting and strange thing. I checked a file for which e2fsck did 67445000->67446784 i_size change. debugfs stat comparison between fixed file and file with old size differs in i_size *only* (all blocks are the same), but cmp shows difference in 67382273 (it's constant for any bogus file), that is block 65803 which is the last before triple indirection. How did file change if e2fsck just had changed i_size and both values are greater than 67382273? On Wed, Mar 24, 2010 at 10:27 PM, Evgeniy Ivanov <lolkaantimat@xxxxxxxxx> wrote: > Hello, > > Sorry for bothering list with my ext2 questions. > I got into trouble with my ext2 implementation and filesystem with > 1024 block size. Sometimes when I write files they're written > correctly (md5sum is the same as original, i_size is correct either), > but e2fsck changes i_size to another values (which breaks files). E.g. > 67445000->67446784 or 67445248->67446784. I see that new sizes are > numbers of multiples of 1024. > Strange thing is that I can't reproduce this problem with 2048 and > 4096 block sizes. I thought the problem was in trash in unused part of > last block (actually it is zeroed), but then it would be reproduceable > in fs with another block size. > How does ext2 decide to fix that files sizes? Any suggestions? > > Thanks in advance for any help. > > > -- > Evgeniy Ivanov > -- Evgeniy Ivanov -- 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
