From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: "not enough space" with "data raid0"
Date: 17 Mar 2012 13:18:00 +0100 [thread overview]
Message-ID: <C52q4Ocy1uB@helmut.hullen.de> (raw)
In-Reply-To: <201203172313.19705.chris@csamuel.org>
Hallo, Chris,
Du meintest am 17.03.12:
>> Where is the problem, how can I use the full space?
> Which kernel was this with Helmut?
Kernel 3.2.9 (self made)
btrfs-progs-20111030
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2012-03-17 12:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 12:01 "not enough space" with "data raid0" Helmut Hullen
2012-03-17 12:13 ` Chris Samuel
2012-03-17 12:18 ` Helmut Hullen [this message]
2012-03-17 12:19 ` Hugo Mills
2012-03-28 18:38 ` Phillip Susi
2012-03-28 22:11 ` Alex
2012-03-29 1:07 ` Duncan
2012-03-17 12:19 ` Alex
2012-03-17 12:25 ` Hugo Mills
2012-03-17 13:36 ` Alex
2012-03-17 14:00 ` Hugo Mills
2012-03-17 14:24 ` Helmut Hullen
2012-03-17 14:43 ` Hugo Mills
2012-03-17 15:17 ` Alex
2012-03-19 15:14 ` Alex
2012-03-19 17:58 ` Hugo Mills
2012-03-19 21:45 ` Alex Plumbley-Jones
2012-03-17 13:46 ` Helmut Hullen
2012-03-17 14:04 ` Hugo Mills
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=C52q4Ocy1uB@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).