From: Tomasz Chmielewski <tch@virtall.com>
To: bo.li.liu@oracle.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 3.17.0-rc6 system freeze
Date: Mon, 29 Sep 2014 16:18:01 +0200 [thread overview]
Message-ID: <394df3a1d2ee7b374491dd2da1958672@admin.virtall.com> (raw)
In-Reply-To: <20140929141016.GA31870@localhost.localdomain>
On 2014-09-29 16:10 (Mon), Liu Bo wrote:
> Hi Tomasz,
>
> On Mon, Sep 29, 2014 at 02:00:18PM +0200, Tomasz Chmielewski wrote:
>> System froze under 3.17.0-rc6 with btrfs. It had to be hard rebooted.
> How does this happen? A stressful write with compression?
Rsync (with --inplace - can be stressful / lead to fragmentation on
large files which change) + snapshot + remove old snapshot, for several
remote sources (rsync server1, snapshot, remove old snap; rsync server2,
snapshot, remove old snap etc.).
Filesystem is RAID-1 with compress-force=zlib:
/dev/sdc1 on /mnt/lxc2 type btrfs
(rw,noatime,compress-force=zlib,space_cache)
The last operation written to the logfile was snapshot removal.
--
Tomasz Chmielewski
http://www.sslrack.com
prev parent reply other threads:[~2014-09-29 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 12:00 3.17.0-rc6 system freeze Tomasz Chmielewski
2014-09-29 14:10 ` Liu Bo
2014-09-29 14:18 ` Tomasz Chmielewski [this message]
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=394df3a1d2ee7b374491dd2da1958672@admin.virtall.com \
--to=tch@virtall.com \
--cc=bo.li.liu@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).