All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: kreijack@libero.it
Cc: Mike Fedyk <mfedyk@mikefedyk.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3 V3] btrfs: a new tool to manage a btrfs filesystem
Date: Wed, 24 Feb 2010 18:35:38 -0500	[thread overview]
Message-ID: <20100224233538.GH25641@think> (raw)
In-Reply-To: <201002221947.40793.kreijack@libero.it>

On Mon, Feb 22, 2010 at 07:47:40PM +0100, Goffredo Baroncelli wrote:
> On Monday 22 February 2010, Mike Fedyk wrote:
> > On Sun, Feb 21, 2010 at 8:40 AM, Goffredo Baroncelli <kreijack@gmai=
l.com>=20
> wrote:
> > >       filesystem resize [+/-]<size>[gkm]|max <filesystem>
> >=20
> > -filesystem resize [+/-]<size>[gkm]|max <filesystem>
> > +filesystem resize [+/-]<size>[gkm]|max <dev>
> >=20
> > This command works on devices, not paths.
>=20
> Are you sure ? To me it results (test and code inspection) to work on=
 path.

The ioctl takes a path so that it knows which btrfs filesystem to
change.

>=20
> >=20
> > >              Resize a filesystem identified by <path>.  The <size=
> parame=E2=80=90
> >=20
> > -Resize a filesystem identified by <path>.  The <size> parame=E2=80=
=90
> > +Resize a filesystem identified by <dev>.  The <size> parame=E2=80=90
> >=20
> > >              ter  specifies the new size of the filesystem.  If t=
he prefix
> > >              + or - is present the size is increased or decreased=
  by  the
> > >              quantity  <size>.  If no units are specified, the un=
it of the
> > >              <size> parameter defaults  to  bytes.  Optionally,  =
the  size
> > >              parameter  may  be suffixed by one of the following =
the units
> > >              designators: 'K', 'M', or 'G', kilobytes, megabytes,=
 or giga=E2=80=90
> > >              bytes, respectively.
> > >
> > >              If  'max' is passed, the filesystem will occupy all =
available
> > >              space on the volume(s).
> > >
> > >              The resize command does not manipulate the size of u=
nderlying
> > >              partitions.   If you wish to enlarge/reduce a filesy=
stem, you
> >=20
> > -partitions.   If you wish to enlarge/reduce a filesystem, you
> > +partition.   If you wish to enlarge/reduce a filesystem, you
> ok
>=20
> > >              must make sure you can expand/reduce the size of  th=
e  parti=E2=80=90
> > >              tion also.
> >=20
> > -must make sure you can expand/reduce the size of  the  parti=E2=80=
=90
> > -tion also.
> > +must make sure you can expand the partition before enlarging
> > +the filesystem and shrink the partition after reducing the size
> > +of the filesystem.
> ok
>=20
> > >
> > >
> > >       filesystem show [<uuid>|<label>]
> > >              Show  the  btrfs  filesystem with some additional in=
fo. If no
> > >              UUID or label is passed, btrfs show info  of  all  t=
he  btrfs
> > >              filesystem.
> > >
> > >
> > >       device balance|-b <path>
> >=20
> > -device balance|-b <path>
> > +device balance <path>
>=20
> ok
>=20
> > Mike
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btr=
fs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >=20
>=20
> I will update my repo

Thanks!

-chris

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

  reply	other threads:[~2010-02-24 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201002211740.13074.kreijack@libero.it>
2010-02-22  5:33 ` [PATCH 0/3 V3] btrfs: a new tool to manage a btrfs filesystem Mike Fedyk
2010-02-22 18:47   ` Goffredo Baroncelli
2010-02-24 23:35     ` Chris Mason [this message]
2010-02-25  3:25       ` Mike Fedyk

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=20100224233538.GH25641@think \
    --to=chris.mason@oracle.com \
    --cc=kreijack@libero.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mfedyk@mikefedyk.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.