xfs
[Top] [All Lists]

Re: [PATCH] xfstests: btrfs/015 regression test for prealloc with balanc

To: Josef Bacik <jbacik@xxxxxxxxxxxx>
Subject: Re: [PATCH] xfstests: btrfs/015 regression test for prealloc with balance
From: Zach Brown <zab@xxxxxxxxxx>
Date: Fri, 27 Sep 2013 10:55:59 -0700
Cc: xfs@xxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1380292053-8123-1-git-send-email-jbacik@xxxxxxxxxxxx>
References: <1380292053-8123-1-git-send-email-jbacik@xxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
> +nr_csum_no_found=$(dmesg | grep -c "no csum found")
> +nr_csum_failed=$(dmesg | grep -c "csum failed")
> +
> +_check_csum_error()
> +{
> +     new_csum_no_found=$(dmesg | grep -c "no csum found")
> +     new_csum_failed=$(dmesg | grep -c "csum failed")
> +
> +     if [ $nr_csum_no_found -eq $new_csum_no_found -a \
> +          $nr_csum_failed -eq $new_csum_failed ]; then
> +             return 0
> +     fi
> +     return 1
> +}

> +# This sucks but unfortunately it is the only way to be sure something 
> didn't go
> +# wrong.
> +_check_csum_error || _fail "csum detected, please check dmesg"

In the future you could make them trace events and catch them for a
given invocation of a command with perf.

- z

<Prev in Thread] Current Thread [Next in Thread>