Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #63529

Bug#908216: btrfs blocked for more than 120 seconds

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Wed, Mar 06, 2019 at 07:55:45AM -0600, Russell Mosemann wrote:
>    The four most problematic servers were hanging nearly every day. They each
>    have a dedicated hard drive and are running 4.19.0-0.bpo.2-amd64. I
>    installed btrfs-progs 4.20.1 on each and recreated the file system on the
>    hard drive. There have been no issues since then, but it is too early to
>    tell. There are hardly any references or files on the drives. It might
>    take up to a month to know if there is an issue.
> 

Thanks for reformatting with newer -progs; this eliminates the most
difficult/impossible to reproduce factor.  Which of the five rounds of
tests from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908216#202 have you
started with?

It should be possible to accelerate triggering the bug by using the
network to send additional VM images from each server to the test
subject once a day.  eg: if four servers send VM images to a fifth
server then ideally (optimistically!) the bug would be triggered 80%
faster, and if everything is still all clear after a month then you'd
have at least 220 reflinked historical backups and five sparse copies
of large VM images.

Thank you for your work on making this bug reproducible.  This not
only accelerates its resolution (reproducible case in core
functionality needs to be forwarded upstream), but also provides
valuable data to inform our wiki's upcoming btrfs on buster
(linux-4.19) recommendations.

Cheers,
Nicholas

Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#908216: btrfs blocked for more than 120 seconds "Russell Mosemann" <rmosemann@futurefoam.com> - 2019-02-25 01:40 +0100
  Bug#908216: btrfs blocked for more than 120 seconds Nicholas D Steeves <nsteeves@gmail.com> - 2019-02-25 02:10 +0100
    Bug#908216: btrfs blocked for more than 120 seconds "Russell Mosemann" <rmosemann@futurefoam.com> - 2019-02-25 19:50 +0100
      Bug#908216: btrfs blocked for more than 120 seconds Nicholas D Steeves <nsteeves@gmail.com> - 2019-02-26 05:30 +0100
        Bug#908216: btrfs blocked for more than 120 seconds "Russell Mosemann" <rmosemann@futurefoam.com> - 2019-02-27 13:30 +0100
          Bug#908216: btrfs blocked for more than 120 seconds "Russell Mosemann" <rmosemann@futurefoam.com> - 2019-02-27 17:30 +0100
            Bug#908216: btrfs blocked for more than 120 seconds "Russell Mosemann" <rmosemann@futurefoam.com> - 2019-03-02 13:00 +0100
        Bug#908216: btrfs blocked for more than 120 seconds Nicholas D Steeves <nsteeves@gmail.com> - 2019-03-02 23:10 +0100
          Bug#908216: btrfs blocked for more than 120 seconds "Russell Mosemann" <rmosemann@futurefoam.com> - 2019-03-03 00:20 +0100
            Bug#908216: btrfs blocked for more than 120 seconds Nicholas D Steeves <nsteeves@gmail.com> - 2019-03-03 02:10 +0100
          Bug#908216: btrfs blocked for more than 120 seconds "Russell Mosemann" <rmosemann@futurefoam.com> - 2019-03-06 15:00 +0100
            Bug#908216: btrfs blocked for more than 120 seconds Nicholas D Steeves <nsteeves@gmail.com> - 2019-03-09 01:30 +0100

csiph-web