From: Gerhard Kulzer <gerhard@kulzer.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs: failed to load free space cache for block group on rsync´ing to space_cache BTRFS with subvolume
Date: Thu, 23 Jun 2011 20:42:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20110623T223707-409@post.gmane.org> (raw)
In-Reply-To: 201106231937.12848.Martin@lichtvoll.de
Martin Steigerwald <Martin <at> lichtvoll.de> writes:
>=20
> Hi!
>=20
> Short summary: I suspect that rsync=C2=B4ing files to a newly created=
BTRFS=20
> partition with a subvolume *and* enabled space_cache triggers the err=
or=20
> mentioned in the subject line of this mail. I reported this also as:
>=20
> Bug 38112 - btrfs: failed to load free space cache for block group o=
n=20
> rsync=C2=B4ing to space_cache BTRFS with subvolume
>=20
> https://bugzilla.kernel.org/show_bug.cgi?id=3D38112
>=20
Same happens to me when I use Ubuntu kernel 3.0.1, after a short time l=
ike 20
seconds into the desktop I get the same error message. This happens on =
a btrfs
system that is already 2 years old and never had that problem (mount=3D=
ssd,
compress=3Dlzo,noatime, space_cache).
When I boot with 2.6.38-10 I never get this error. So I assume that the=
problem
is with the newer code of 3.0.1
Gerhard
--
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-06-23 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 17:37 btrfs: failed to load free space cache for block group on rsync´ing to space_cache BTRFS with subvolume Martin Steigerwald
2011-06-23 20:05 ` Josef Bacik
2011-06-24 12:46 ` Martin Steigerwald
2011-06-24 13:04 ` Josef Bacik
2011-06-23 20:42 ` Gerhard Kulzer [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=loom.20110623T223707-409@post.gmane.org \
--to=gerhard@kulzer.net \
--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).