Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Also seeing full deadlocks with 3.15.1
Date: Fri, 27 Jun 2014 13:40:05 -0700	[thread overview]
Message-ID: <20140627204005.GB28692@merlins.org> (raw)
In-Reply-To: <20140627185009.GA21428@merlins.org>

On Fri, Jun 27, 2014 at 11:50:09AM -0700, Marc MERLIN wrote:
> My laptop deadlocked some more times (everything works until it needs to
> touch the filesystem, and then it's deadlocked).
> Unfortunately, I can trigger sysrq, but it doesn't get committed to disk and
> netconsole eats half of it because it goes too fast for UDP apparently
> 
> Now, I just captured that on my server with serial console.
> 
> 11005  1-16:11:10 wait_current_trans.isra.15     /usr/bin/zma -m 3
> 14441  1-16:07:44 wait_current_trans.isra.15     /usr/bin/zma -m 1
> 17045  1-23:53:33 wait_current_trans.isra.15     /usr/bin/zma -m 9
> 22261  2-00:40:36 wait_current_trans.isra.15     /usr/bin/zma -m 6
> 22292  2-00:40:36 wait_current_trans.isra.15     /usr/bin/zma -m 8
> 
> 19911    09:29:35 wait_current_trans.isra.15     rm -f -- /mnt/dshelf2/backup/0Notmachines/mysql//mysql.daily.sql.gz.13 /mnt/dshelf2/backup/0Notmachines/mysql//mysql.daily.sql.gz.13.gz
> 22848  1-05:18:35 wait_current_trans.isra.15     rm -f -- mnt/dshelf2/backup/0Notmachines/jen//backup.tar.bz.11 mnt/dshelf2/backup/0Notmachines/jen//backup.tar.bz.11.gz
> 
> Those are 2 different filesystems (one single device mapper disk, the other one is btrfs raid1), so I'm not sure which one of the 2 caused the problem, but I'm perplexed as to why one would than hang the other, unless they both hit the same bug?

Ok, soon after reboot, I'm already seeing this:
  742       37:19 wait_current_trans.isra.15     /usr/bin/zma -m 9
 5494       06:45 wait_current_trans.isra.15     /bin/rm -rf 1/14/06/27/13/10/18
11258    01:48:28 wait_current_trans.isra.15     /usr/bin/zma -m 3
14076       27:01 wait_current_trans.isra.15     /usr/bin/zma -m 1
21615       47:18 wait_current_trans.isra.15     /usr/bin/zma -m 8

on this filesystem:
gargamel:~# btrfs fi df /mnt/btrfs_raid0/
Data, RAID0: total=1.47TiB, used=892.25GiB
Data, single: total=8.00MiB, used=7.95MiB
System, RAID1: total=8.00MiB, used=128.00KiB
System, single: total=4.00MiB, used=0.00
Metadata, RAID1: total=15.00GiB, used=6.09GiB
Metadata, single: total=8.00MiB, used=0.00
unknown, single: total=512.00MiB, used=64.00KiB

If I don't hear anything by the end of today, I'll just delete the
filesystem and start over.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2014-06-27 20:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 18:50 Also seeing full deadlocks with 3.15.1 Marc MERLIN
2014-06-27 20:40 ` Marc MERLIN [this message]
2014-06-27 21:50   ` ronnie sahlberg
2014-06-27 22:33     ` Marc MERLIN
2014-06-27 22:36 ` Josef Bacik
2014-06-27 23:59   ` Marc MERLIN
2014-06-28  0:14     ` Josef Bacik

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=20140627204005.GB28692@merlins.org \
    --to=marc@merlins.org \
    --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