As Marc Merlin recently wrote in his blog [1] scrub can sometimes leave a stale state file behind, making cancel/resume complain. I took a peek at the code and found most of the scrub state file handling fairly straightforward, so before I go off and start hacking, what would a better behaviour look like?
- delete the stale file? - fix the file by setting the "finished" flag? - something else entirely? I currently lean towards fixing (and not printing an error?), but maybe someone else has different ideas about how this should be handled. Any suggestions welcome.. cheers Holger [1] http://marc.merlins.org/perso/btrfs/post_2014-04-26_Btrfs-Tips_- Cancel-A-Btrfs-Scrub-That-Is-Already-Stopped.html -- 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
