Btrfs devel - Feb 2013 - Does btrfs adapt to size changes of underlying block device(s)?

Hello,

I''ve got a quick question: Does btrfs adapt to size changes of the
underlying block device(s)?

My specific situation is as follows: I''ve got a luks-volume on which I
want to put btrfs. If this luks-volume grows in the future (i.e. by
''cryptsetup resize''), will btrfs automatically (and reliably)
"see" this
and be able to use the additional space?

Of course, one can always put an lvm-layer in between, but I would really
like to avoid this.

And as we''re at it: What about shrinking of the underlying
block-device?


Thanks for your help,

Simon

--
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

On Mon, Feb 04, 2013 at 01:37:21PM +0100, Simon Campese
wrote:
> Hello,
> 
> I''ve got a quick question: Does btrfs adapt to size changes of the
> underlying block device(s)?
> 
> My specific situation is as follows: I''ve got a luks-volume on
which I
> want to put btrfs. If this luks-volume grows in the future (i.e. by
> ''cryptsetup resize''), will btrfs automatically (and
reliably) "see" this
> and be able to use the additional space?
  Not automatically, you need to invoke btrfs command for that. But 
shrinking and growing works online and is reliable.

   btrfs filesystem resize [devid:][+/-]<newsize>[gkm]|[devid:]max
<path>

-- 
Tomasz Torcz                 Morality must always be based on practicality.
xmpp: zdzichubg@chrome.pl                -- Baron Vladimir Harkonnen

--
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