>>> 2. AFAIK, "autodefrag" detects small random writes into files and >>> queues them up for an automatic defrag process, so the filesystem will >>> defragment itself while it's used. >>> >>> If the system reboot/crash/remount-ro, will the autodefrag process >>> continue after resume? >>> > For reboot, autodefrag will be waited to finish during umounting btrfs. > > For crash and remount-ro, it won't resume since it is not that necessary and > we're all > COWed so that the data is ok. > > And autodefrag will only take effect when taking the 'autodefrag' mount > option. > > thanks, > liubo > >
Can the loophole be fixed by tuning the autodefrag algorithm? e.g. also queue up small extents detected during read operation for the autodefrag process. Is there any io niceness control for autodefrag process too? it will be nice if the idle class is used. Actually, i try to write shell script to defrag entire FS monthy. but i soon find out it is hard to keep track of progress across reboot and avoid redefragging defragged file For me, autodefrag is a killer feature. :) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
