From: Roman Mamedov <rm@romanrm.net>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: Timofey Titovets <nefelim4ag@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs hangs 3.19-10
Date: Thu, 2 Apr 2015 19:13:12 +0500 [thread overview]
Message-ID: <20150402191312.1ee31af3@natsu> (raw)
In-Reply-To: <20150402114608.GG32078@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Thu, 2 Apr 2015 11:46:08 +0000
Hugo Mills <hugo@carfax.org.uk> wrote:
> On Thu, Apr 02, 2015 at 02:38:24PM +0300, Timofey Titovets wrote:
> > I've get it several times, after rebooting or unclean shutdown system.
> >
> > This is very strange bug, because if i reboot, and mount it from live
> > cd, all that okay, and after reboot in system, system successful mount
> > all and working good.
> > i did try to found any previous issues on it, and found nothing.
>
> Try 4.0-rc6, which should have the fix for the problem in it. This
> was introduced in the stable series, and is now fixed in mainline. It
> should also be fixed in the next stable release, I believe.
Yeah I believe I just hit that in 3.14.37, system unbootable (locks up at
"Scanning for Btrfs filesystems"), resulted in a many hour downtime as it was
a remote system w/o IPMI. Fine after a reboot to 3.14.34. Too bad that even
staying on the "stable" series kernel can back-stab you like that from time to
time.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-04-02 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 11:38 Btrfs hangs 3.19-10 Timofey Titovets
2015-04-02 11:46 ` Hugo Mills
2015-04-02 11:47 ` Timofey Titovets
2015-04-02 14:13 ` Roman Mamedov [this message]
2015-04-03 5:14 ` Duncan
2015-04-04 12:55 ` Russell Coker
2015-04-04 13:00 ` Hugo Mills
2015-04-05 3:16 ` Duncan
2015-04-05 3:30 ` Russell Coker
2015-04-05 10:04 ` Hugo Mills
2015-04-06 3:21 ` Duncan
2015-04-06 8:39 ` Russell Coker
2015-04-06 7:40 ` Pavel Volkov
2015-04-06 8:37 ` Russell Coker
2015-04-06 9:20 ` Duncan
2015-04-06 9:29 ` Duncan
2015-04-06 10:13 ` Hugo Mills
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=20150402191312.1ee31af3@natsu \
--to=rm@romanrm.net \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@gmail.com \
/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