From: Phillip Susi <psusi@ubuntu.com>
To: "Marco L. Crociani" <marco.crociani@gmail.com>
Cc: sander@humilis.net, linux-btrfs@vger.kernel.org
Subject: Re: Can't resize second device in RAID1
Date: Tue, 17 Jan 2012 11:22:31 -0500 [thread overview]
Message-ID: <4F15A047.3080006@ubuntu.com> (raw)
In-Reply-To: <CADy=jfV+-sT_9opMeUXxOF4zWxt7PTQOg_+bPL7o5vq66omcsA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I submitted some patches a few weeks ago to fix this so you specify
the device normally instead of looking up the internal devid and
passing it as an undocumented prefix to the size parameter. Hopefully
they can get merged sometime soon.
On 1/14/2012 1:18 PM, Marco L. Crociani wrote:
>>> ./btrfs fi resize max /mnt/RootFS:2 ERROR: can't access to
>>> '/mnt/RootFS:2'
>>
>> btrfs filesystem resize 2:max /mnt/RootFS
>>
>> Sander
>>
>> -- Humilis IT Services and Solutions http://www.humilis.net
>
> Perfect, Thank you! I've written a section on:
> http://btrfs.ipv5.de/index.php?title=UseCases
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPFaBGAAoJEJrBOlT6nu754+0H/jyk5yDLn5T4sYiPNGAFQyG+
SI47GsE3uD5pfQ0vve8YsDSburNbBzHTmsyWdn/YZE+TtocNTsj+Gj3m7bd/Flr8
u/dM/4htyyiAjEXJeRQqlnApFDh0hBeMZSF1qK9odhMd8h2FqOfon7mrafCjPzGY
R9FG1nTqXVmNBmdWQfTiRLnR5ErTBImd8Mo+zt9vbd5naR1Sxc9sUFk1BX4jP0lp
ZK66C7SPMdb7HnVROPR2TEFHweAjPjF1YMcFOkR4/no37jB+g5/+wlF0YuV4hnc0
BgC/5dZcxOP1R+nUNQ1xPZm7My+dlzVJaG9AqQC5IEKW7Lejn9HxJzgtZyTZ8hs=
=QpE2
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-01-17 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADy=jfVZjRAE049OiD6VkoKkpzZh9e_=V62AvuVwxyHZyfuU1w@mail.gmail.com>
2012-01-13 23:12 ` Can't resize second device in RAID1 Marco L. Crociani
2012-01-13 23:17 ` Hugo Mills
2012-01-13 23:32 ` Marco L. Crociani
2012-01-14 14:42 ` Sander
2012-01-14 18:18 ` Marco L. Crociani
2012-01-17 16:22 ` Phillip Susi [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=4F15A047.3080006@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marco.crociani@gmail.com \
--cc=sander@humilis.net \
/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).