On Tue, Jul 28, 2015 at 03:53:58PM +0800, Zhaolei wrote: > From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx> > > Anthony Plack <anthony@xxxxxxxxx> reported a output bug in maillist: > title: btrfs-progs SCRUB reporting aborted but still running - minor > > btrfs scrub status report it was aborted but still runs to completion. > # btrfs scrub status /mnt/data > scrub status for f591ac13-1a69-476d-bd30-346f87a491da > scrub started at Mon Apr 27 06:48:44 2015 and was aborted after 1089 seconds > total bytes scrubbed: 1.02TiB with 0 errors > # > # btrfs scrub status /mnt/data > scrub status for f591ac13-1a69-476d-bd30-346f87a491da > scrub started at Mon Apr 27 06:48:44 2015 and was aborted after 1664 seconds > total bytes scrubbed: 1.53TiB with 0 errors > # > ... > > Reason: > When scrub multi-device simultaneously, if some device canceled, > and some device is still running, cancel state have higher priority to > be outputed in global report. > So we can see "scrub aborted" in status line, with running-time keeps > increased. > > Fix: > We can increase running state's priority in output, if there is > some device in scrub state, we output running state instead of > cancelled state. > > Reported-by: Anthony Plack <anthony@xxxxxxxxx> > Signed-off-by: Zhao Lei <zhaolei@xxxxxxxxxxxxxx> Applied, thanks. -- 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
