From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Filesystem locks up, also with older kernel on any action after booting into 4.7-rc4 once
Date: Sat, 2 Jul 2016 21:40:27 +0200 [thread overview]
Message-ID: <0d0631a5-cd8a-9a1f-2ce5-0810bc9bf441@mendix.com> (raw)
In-Reply-To: <CAJCQCtQGOynjitChtzk4kxzut4_qFOXGNR8xvoOA9Q7tcUvQ7w@mail.gmail.com>
On 07/02/2016 09:18 PM, Chris Murphy wrote:
> On Sat, Jul 2, 2016 at 11:34 AM, Hans van Kranenburg
> <hans.van.kranenburg@mendix.com> wrote:
>> On 07/02/2016 07:14 PM, Hans van Kranenburg wrote:
>>>
>>> I just rebooted a VM into a 4.7 kernel. The joy didn't last long. After
>>> 177 seconds the btrfs data partition (root is on ext4) locked up. Worse,
>>> it keeps locking up on any action performed even when rebooting it with
>>> older kernels again. D: The filesystem initially mounts fine, but then
>>> locks up again immediately.
>>>
>>> Linux stacheldraht 4.7.0-rc4-amd64 #1 SMP Debian 4.7~rc4-1~exp1
>>> (2016-06-20) x86_64 GNU/Linux
>>>
>>> ps output shows [btrfs-transaction] in D state:
>>>
>>> root 1108 0.0 0.0 0 0 ? D 17:42 0:00 \_
>>> [btrfs-transacti]
>>>
>>> From dmesg:
>>>
>>> [blah blah blah]
>>>
>>> So, something happened inside the fs that makes it lock up every time I
>>> try to do anything with it...
>>
>>
>> I force-rebooted the poor thing again, and mounted the filesystem ro. It
>> mounts without any complaint. I can see all files now, I can do sub list
>> etc...
>>
>> So I think I'm going to copy some data to a new filesystem on a new block
>> device just in case. The thing has to move to new storage anyway it's about
>> 100 subvolumes with about 150GB of data, so that's a nice excercise with
>> send/receive.
>
> Two things might be interesting:
> 1. btrfs check (without repair) to add to the above and see whether it
> finds any problems.
> 2. For send, to try -e option, if you have related subvolume
> snapshots. See if this bug is really a bug or user error or maybe it's
> fixed.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=111221
The directory structure is dirvish with my btrfs patches.
These are the subvols:
2016050802/tree
2016051502/tree
So they're all named tree. I cannot just send them all to some location.
And I cannot rename them, because the fs is mounted ro...
--
Hans van Kranenburg - System / Network Engineer
T +31 (0)10 2760434 | hans.van.kranenburg@mendix.com | www.mendix.com
next prev parent reply other threads:[~2016-07-02 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 17:14 Filesystem locks up, also with older kernel on any action after booting into 4.7-rc4 once Hans van Kranenburg
2016-07-02 17:34 ` Hans van Kranenburg
2016-07-02 19:18 ` Chris Murphy
2016-07-02 19:40 ` Hans van Kranenburg [this message]
2016-07-02 22:37 ` Hans van Kranenburg
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=0d0631a5-cd8a-9a1f-2ce5-0810bc9bf441@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.