From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert fails
Date: 31 Oct 2010 20:26:00 +0100 [thread overview]
Message-ID: <BZurfT2T1uB@helmut.hullen.de> (raw)
In-Reply-To: BZurHFYT1uB@helmut.hullen.de
Hallo,
I wrote am 31.10.10 zum Thema btrfs-convert fails:
> I've tried to convert a 12 GByte ext2 partition (nearly full, 280
> MByte free) with btrfs-convert.
> After about 15 minutes (700-MHz-CPU) the system tells
> ...
> creating ext2fs image file
> cleaning up system chunk
> btrfs-convert: extent-tree.c:2529: btrfs_reserve_extent: Assertion
> `!(ret)' failed
> Abgebrochen
Next try: about 11 GByte data, about 690 MByte free: same crash.
> "syslogd" tells
> Oct 31 17:43:16 ElNath kernel: ------------[ cut here ]------------
> Oct 31 17:43:17 ElNath kernel: kernel BUG at fs/btrfs/volumes.c:2831!
> Oct 31 17:43:17 ElNath kernel: invalid opcode: 0000 [#1]
> Oct 31 17:43:17 ElNath kernel: last sysfs file:
> /sys/devices/pci0000:00/0000:00:04.0/0000:08:02.0/0000:09:00.0/class
[etc.]
These syslogd messages come when I try to mount the incompletely
converted partition.
And then the system needs to be restarted ... mounting doesn't work,
"halt" or "reboot" doesn't work.
------------------------------------------------
Another experiment: when the partition (about 11.7 GByte) is filled with
about 9 GByte data, converting works fine.
How much free space needs "btrfs-convert"?
Does it need xx GByte, or does it need yy percent?
Depends this free space on the number of files? I have filled my testing
partition with *.iso images, 2 to 4 files.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2010-10-31 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 15:55 btrfs-convert fails Helmut Hullen
2010-10-31 19:26 ` Helmut Hullen [this message]
2010-11-01 2:06 ` Yan, Zheng
2010-11-01 8:02 ` Helmut Hullen
2010-11-01 9:49 ` Felix Blanke
2010-11-01 11:55 ` Helmut Hullen
2010-11-01 12:20 ` cwillu
2010-11-02 0:43 ` Chris Samuel
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=BZurfT2T1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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).