From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: Btrfs: blocked for more than 120 seconds, made worse by 3.2 rc7
Date: Wed, 28 Dec 2011 22:36:12 +0200 [thread overview]
Message-ID: <4EFB7DBC.8070601@gmail.com> (raw)
In-Reply-To: <4EFB6D4F.6070002@gmail.com>
Well now machine2 has just crashed too...
http://pastebin.com/gvfUm0az
On =CE=A4=CE=B5=CF=84=CE=AC=CF=81=CF=84=CE=B7, 28 =CE=94=CE=B5=CE=BA=CE=
=AD=CE=BC=CE=B2=CF=81=CE=B9=CE=BF=CF=82 2011 9:26:07 =CE=BC=CE=BC, Kons=
tantinos Skarlatos wrote:
> Hello all:
> I have two machines with btrfs, that give me the "blocked for more=20
> than 120 seconds" message. After that I cannot write anything to disk=
,=20
> i am unable to unmount the btrfs filesystem and i can only reboot wit=
h=20
> sysrq-trigger.
>
> It always happens when i write many files with rsync over network.=20
> When i used 3.2rc6 it happened randomly on both machines after=20
> 50-500gb of writes. with rc7 it happens after much less writes,=20
> probably 10gb or so, but only on machine 1 for the time being. machin=
e=20
> 2 has not crashed yet after 200gb of writes and I am still testing th=
at.
>
> machine 1: btrfs on a 6tb sparse file, mounted as loop, on a xfs=20
> filesystem that lies on a 10TB md raid5. mount options=20
> compress=3Dzlib,compress-force
>
> machine 2: btrfs over md raid 5 (4x2TB)=3D5.5TB filesystem. mount=20
> options compress=3Dzlib,compress-force
>
> pastebins:
>
> machine1:
> 3.2rc7 http://pastebin.com/u583G7jK
> 3.2rc6 http://pastebin.com/L12TDaXa
>
> machine2:
> 3.2rc6 http://pastebin.com/khD0wGXx
> 3.2rc7 (not crashed yet)
WARNING: multiple messages have this Message-ID (diff)
From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: Btrfs: blocked for more than 120 seconds, made worse by 3.2 rc7
Date: Wed, 28 Dec 2011 22:36:12 +0200 [thread overview]
Message-ID: <4EFB7DBC.8070601@gmail.com> (raw)
In-Reply-To: <4EFB6D4F.6070002@gmail.com>
Well now machine2 has just crashed too...
http://pastebin.com/gvfUm0az
On Τετάρτη, 28 Δεκέμβριος 2011 9:26:07 μμ, Konstantinos Skarlatos wrote:
> Hello all:
> I have two machines with btrfs, that give me the "blocked for more
> than 120 seconds" message. After that I cannot write anything to disk,
> i am unable to unmount the btrfs filesystem and i can only reboot with
> sysrq-trigger.
>
> It always happens when i write many files with rsync over network.
> When i used 3.2rc6 it happened randomly on both machines after
> 50-500gb of writes. with rc7 it happens after much less writes,
> probably 10gb or so, but only on machine 1 for the time being. machine
> 2 has not crashed yet after 200gb of writes and I am still testing that.
>
> machine 1: btrfs on a 6tb sparse file, mounted as loop, on a xfs
> filesystem that lies on a 10TB md raid5. mount options
> compress=zlib,compress-force
>
> machine 2: btrfs over md raid 5 (4x2TB)=5.5TB filesystem. mount
> options compress=zlib,compress-force
>
> pastebins:
>
> machine1:
> 3.2rc7 http://pastebin.com/u583G7jK
> 3.2rc6 http://pastebin.com/L12TDaXa
>
> machine2:
> 3.2rc6 http://pastebin.com/khD0wGXx
> 3.2rc7 (not crashed yet)
next prev parent reply other threads:[~2011-12-28 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 19:26 Btrfs: blocked for more than 120 seconds, made worse by 3.2 rc7 Konstantinos Skarlatos
2011-12-28 20:36 ` Konstantinos Skarlatos [this message]
2011-12-28 20:36 ` Konstantinos Skarlatos
2011-12-28 21:48 ` Dave Chinner
2011-12-28 21:58 ` Konstantinos Skarlatos
2011-12-28 21:58 ` Konstantinos Skarlatos
2011-12-28 21:58 ` Konstantinos Skarlatos
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=4EFB7DBC.8070601@gmail.com \
--to=k.skarlatos@gmail.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 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.