Marc MERLIN posted on Sun, 23 Feb 2014 22:17:14 -0800 as excerpted: > Mmmh, this bug might be part of the problem: > gargamel:/mnt# btrfs scrub start btrfs_pool2 > ERROR: scrub is already running.
> gargamel:/mnt# btrfs scrub cancel btrfs_pool2 > ERROR: scrub cancel failed on btrfs_pool2: not running > gargamel:/mnt# btrfs scrub status [snip output] > Note that it says running for 5 seconds, but it started 4H ago. This is a known issue. I believe there's a fix coming (a cancel that blows away the tracking file if it finds it and no actual running scrub is the most obvious fix), but meanwhile, see the /var/lib/btrfs/scrub.status.* files. That's where scrub state is stored, and manually blowing away the appropriate file should clear btrfs' memory of the aborted scrub, so you can scrub start properly. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
