On Tue, 2014-10-14 at 16:18 +0100, Bob Williams wrote: > When I run scrub on the root (system) partition now, I get > > ERROR: scrub is already running. > To cancel use 'btrfs scrub cancel /'. > To see the status use 'btrfs scrub status [-d] /'. > > but > > # btrfs scrub cancel / > ERROR: scrub cancel failed on /: not running > > This situation (scrub running persistently) survives reboots. > > On the /home partition, everything is OK: > > scrub status for 56884b1d-93ab-4db9-bc93-eff3833e91e1 > scrub started at Tue Oct 14 02:00:01 2014 and finished after > 9972 seconds > total bytes scrubbed: 2.47TiB with 0 errors > > Should I worry about this (apart from the fact that I cannot scrub > /)? > What can I do about it? This usually just means that the local state file used to track scrub history has gotten desynchronized. It's easy enough to fix: Edit the file /var/lib/btrfs/scrub.status.56884b1d-93ab-4db9-bc93- eff3833e91e1 (the last bit of the filename is the filesystem uuid) Look for a line that ends with "finished:0" and change it to say "finished:1" This should allow you to start a new scrub. I'm not sure if this has been improved in newer versions of the btrfs- progs. -- Calvin Walton <calvin.walton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
