Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs hang with 4.11.1 kernel
Date: Wed, 17 May 2017 10:02:54 +0000 (UTC)	[thread overview]
Message-ID: <pan$3a41f$57dd0028$589ab08b$36c731eb@cox.net> (raw)
In-Reply-To: 400eaec1e8e4ae2539d4dd8623d43edd@admin.virtall.com

Tomasz Chmielewski posted on Wed, 17 May 2017 17:44:02 +0900 as excerpted:

> After upgrading to 4.11.1 and running for ~12 hours, btrfs filesystem
> hanged - most processes on a server accessing the filesystem went into
> "D" state and blocked.
> 
> The server would not reboot and had to be power cycled.
> 
> 
> Previously, it was running 4.10.7 for around 1.5 month without any
> issues.
> 
> The server has ~10 subvolumes and 5-10 snapshots, >220 GB free (about
> 50% free), runs in RAID-1 mode on SSD disks.
> 
> 
> Is it anything known with 4.11.x?

I've not had any issues with 4.11 myself (in fact, unlike 4.10, 4.11 was 
a rather uneventful kernel development cycle here), and haven't seen any 
4.11-specific btrfs problems reported here either.

Tho Chris Murphy and Hugo may know more, as they do the IRC channel as 
well, which I don't.

So if it's a 4.11 issue, you're one of the first reports, if not /the/ 
first report, of it. =:^\

Which means it's /probably/ not 4.11 specific.  But as I said, I don't do 
IRC, so if there's anything reported only there, I'd not know of it.

(Not being a dev the trace doesn't mean that much to me.)

-- 
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:[~2017-05-17 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  8:44 btrfs hang with 4.11.1 kernel Tomasz Chmielewski
2017-05-17 10:02 ` Duncan [this message]
2017-05-19 19:34 ` Liu Bo

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$3a41f$57dd0028$589ab08b$36c731eb@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