Eric Sandeen wrote: > As a small experiment... > [snip] > ... this yields 10031 lines of fsck output, and results in about 38% of > the files that were on the filesystem going missing. I have had a similar experience converting from 128 to 256 bytes inodes. After a while, tune2fs -I would simply stop doing IO and using a lot of CPU with a few IO bursts every half-hour or so. This is on a recent/fast x86-64 computer. I had to cancel the thing after leaving it running for over 24 hours. > > I don't have the strong sense that tune2fs -I has been shaken out at > all; should it be shipping as a useable option? Maybe add a --accept-consequences-of-shooting-myself-in-the-foot flag ? Cheers, Jonathan -- 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
