[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EFB7DBC.8070601@gmail.com>
Date: Wed, 28 Dec 2011 22:36:12 +0200
From: Konstantinos Skarlatos <k.skarlatos@...il.com>
To: linux-kernel@...r.kernel.org
CC: Linux Btrfs <linux-btrfs@...r.kernel.org>,
Chris Mason <chris.mason@...cle.com>
Subject: Re: Btrfs: blocked for more than 120 seconds, made worse by 3.2 rc7
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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists