From: Li Zefan <lizf@cn.fujitsu.com>
To: Roman Kapusta <roman.kapusta@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel bug
Date: Mon, 26 Sep 2011 08:50:11 +0800 [thread overview]
Message-ID: <4E7FCC43.9080505@cn.fujitsu.com> (raw)
In-Reply-To: <CABVOS0-ELuCKZ5PGvMuZ=RO+V81LPPKXTwDPVEBGtZ=sWKOWvw@mail.gmail.com>
Roman Kapusta wrote:
> Segfault and kernel bug after reflinking several files (20-30 files)
> each of size around 1GB through following command:
>
> cp -r --reflink sorce_dir .
> Segmentation fault
>
> I'm on Fedora 15, kernel 3.0.4
This has been fixed in Linux 3.1-rc7.
next prev parent reply other threads:[~2011-09-26 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 19:26 kernel bug Roman Kapusta
2011-09-24 19:45 ` Roman Kapusta
2011-09-26 0:50 ` Li Zefan [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-23 18:12 kernel BUG Dipl.-Ing. Michael Niederle
2010-12-23 19:43 ` Chris Ball
2010-12-23 20:55 ` Michael Niederle
2010-12-24 0:19 ` Chris Ball
2010-12-24 0:32 ` Michael Niederle
2010-12-24 0:51 ` Chris Ball
2010-12-25 9:50 ` Michael Niederle
2010-12-25 11:46 ` Christian Thaeter
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=4E7FCC43.9080505@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=roman.kapusta@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