linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Deadlock on 3.18.5
Date: Thu, 5 Feb 2015 04:03:09 +0000 (UTC)	[thread overview]
Message-ID: <pan$749cc$d161b717$4f6b3401$e3f1a958@cox.net> (raw)
In-Reply-To: 2BFED81A-1A34-4A4B-800A-A4B6286B74C7@jue.yt

Juergen Fitschen posted on Thu, 05 Feb 2015 00:05:33 +0100 as excerpted:

> I just got a deadlock on Linux 3.18.5. [...]
> I am using a freshly installed Ubuntu 14.04 in a virtual machine. The
> block device used for btrfs is a LVM volume offered by the KVM
> hypervisor.
> Unfortunately I was using an old version of my user space tools (Version
> 3.12-1), so it might be related to that?

I know little to nothing about the complexities of btrfs in a VM so won't 
attempt an answer there.  But about userspace specifically I can say 
this...

For normal operation, btrfs userspace doesn't matter so much.  It's the 
kernel that's vital as userspace mostly simply tells the kernel what to 
do at a relatively high level (mount/umount/snapshot/delete-snapshot/etc) 
and the kernel code handles pretty much everything at the more critical 
lower levels.  OTOH, if there are problems and you are trying to fix them 
using userspace tools such as btrfs check, restore, etc, /that/ is when 
the /userspace/ version needs to be current, as it's then userspace doing 
the low-level stuff as well.

Since it was during normal operations that this deadlock occurred, it's 
almost certainly a kernel problem (unless the problem is ultimately 
traced to a bug in the original mkfs.btrfs that created the filesystem, 
or the like), and that was current, so it's it's a current problem. =:^(

Hopefully a dev or other regular with more VM experience will be along to 
help you further, but I could deal with this much, so I did. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-02-05  4:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 23:05 Deadlock on 3.18.5 Juergen Fitschen
2015-02-05  4:03 ` Duncan [this message]
2015-02-05 11:04 ` Juergen Fitschen
2015-02-05 12:47   ` Austin S Hemmelgarn
2015-02-05 15:24     ` Juergen Fitschen
2015-02-05 16:48       ` Austin S Hemmelgarn

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='pan$749cc$d161b717$4f6b3401$e3f1a958@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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).