linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-btrfs@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting
Date: Tue, 19 Jan 2016 16:19:44 -0800	[thread overview]
Message-ID: <20160120001944.GA9884@localhost.localdomain> (raw)
In-Reply-To: <20160120030223.22cc3ae0@natsu>

On Wed, Jan 20, 2016 at 03:02:23AM +0500, Roman Mamedov wrote:
> Hello,
> 
> I'm facing a strange issue:
> 
> Starting with the kernel 4.4.0, a KVM guest stored on a Btrfs filesystem,
> if it's using the "virtio-scsi" disk backend, will hard lock-up instantly,
> as soon as the Btrfs subvolume which contains its backing file is snapshotted.
> 
> There's nothing in dmesg neither on the guest, nor on the host;
> the KVM process can be killed from the host just fine and then restarted,
> so it doesn't seem to be a kernel-side deadlock of any sort.
> 
> KVM disk controller which exhibits the problem:
> 
>  -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd \
> 
> The alternative which works fine:
> 
>  -device ide-hd,drive=hd,bus=ide.0 \
> 
> The disk device line is common to both cases:
> 
>  -drive if=none,id=hd,cache=writeback,aio=threads,format=raw,file=$NAME.img,discard=unmap,detect-zeroes=unmap \
> 
> Also tried aio=native with the problematic variant, no change.
> 
> Both variants work fine and unaffected by snapshotting on kernel 3.18.25.
> 
> Any ideas?

What about 'btrfs fi df' 's output on the directory where $NAME.img is
located?

According to my experience, kvm guest can be 'no response' when no space
on the backend's filesystem, but you said that the alternative way
work, so it doesn't look like a no space issue.

Thanks,

-liubo
> 
> -- 
> With respect,
> Roman



  parent reply	other threads:[~2016-01-20  1:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 22:02 Kernel 4.4.0 KVM guest on Btrfs locks up on snapshotting Roman Mamedov
2016-01-19 22:18 ` Paolo Bonzini
2016-01-19 23:03   ` Roman Mamedov
2016-01-20  8:28     ` Paolo Bonzini
2016-01-20 13:58       ` Roman Mamedov
2016-01-20 17:28         ` Paolo Bonzini
2016-01-20 18:46           ` Roman Mamedov
2016-01-20 20:38             ` Paolo Bonzini
2016-01-20  0:19 ` Liu Bo [this message]
2016-01-20  5:08   ` Roman Mamedov
2016-01-20 11:34     ` Paolo Bonzini
2016-01-20 15:08       ` Roman Mamedov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160120001944.GA9884@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).