From: Li Zefan <lizf@cn.fujitsu.com>
To: Nik Markovic <nmarkovi.navteq@gmail.com>
Cc: miaox@cn.fujitsu.com, linux-btrfs@vger.kernel.org
Subject: Re: Consistent crash with cp reflink on large files
Date: Tue, 13 Dec 2011 09:28:56 +0800 [thread overview]
Message-ID: <4EE6AA58.702@cn.fujitsu.com> (raw)
In-Reply-To: <CAB3q874C0h1+W7t+8q-QNK7Kb2ujTrtHpD0WZkFaxjYbC9qJfg@mail.gmail.com>
Nik Markovic wrote:
> Li Zefan wrote:
>>
>> Nik Markovic wrote:
>>> Hi All,
>>>
>>> I have been encountering consistent btrfs filesystem crashes when
>>> using cp =96reflink=3Dalways on a large file and modifying it. I be=
lieve
>>> that the test file needs to be fairly large as I was not able to
>>> reproduce with smaller files. The filesystem size is 45GB and file
>>> size is 10GB.
>>>
>>
>> It should be fixed in 3.1 by this commit:
>>
>> commit b6f3409b2197e8fcedb43e6600e37b7cfbe0715b
>> Author: Sage Weil <sage@newdream.net>
>> Date: Tue Sep 20 14:48:51 2011 -0400
>>
>> Btrfs: reserve sufficient space for ioctl clone
>>
>> Fix a crash/BUG_ON in the clone ioctl due to insufficient reserva=
tion. We
>> need to reserve space for:
>>
>> - adjusting the old extent (possibly splitting it)
>> - adding the new extent
>> - updating the inode
> Thanks Li,
>=20
> You are probably right. I upgraded to 3.2-rc5 today and was not able
> to reproduce with 100k iterations.
> Do you think that applying the same patch to 3.0 should fix this issu=
e in 3.0?
>=20
yes, it should be fine.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-12-13 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 20:15 Consistent crash with cp reflink on large files Nik Markovic
2011-12-13 0:44 ` Li Zefan
2011-12-13 1:22 ` Nik Markovic
2011-12-13 1:28 ` Li Zefan [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=4EE6AA58.702@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=nmarkovi.navteq@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 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.