From: Imran Geriskovan <imran.geriskovan@gmail.com>
To: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs on whole disk (no partitions)
Date: Wed, 18 Jun 2014 23:19:28 +0200 [thread overview]
Message-ID: <CAK5rZE7Gx2H1Fg=bNBqwNV1iDFnLNxu9B+odGUAeEeR2eO8bEQ@mail.gmail.com> (raw)
In-Reply-To: <CAPLrYESSX+D5tnY_qWcz0B+xUyyT1Ut-ALM=b9TfehACUq82GA@mail.gmail.com>
On 6/18/14, Daniel Cegiełka <daniel.cegielka@gmail.com> wrote:
> I created btrfs directly to disk using such a scheme (no partitions):
> cd /mnt
> btrfs subvolume create __active
> btrfs subvolume create __active/rootvol
> Everything works fine. Is such a solution is recommended? In my
> opinion, the creation of the partitions seems to be completely
> unnecessary if you can use btrfs.
Partitionless and subvolumeless desktop setup (everything is in
default subvolume) is operational here since kernel 3.10 (now 3.14).
No issues.
Regards, Imran
next prev parent reply other threads:[~2014-06-18 21:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 19:29 btrfs on whole disk (no partitions) Daniel Cegiełka
2014-06-18 20:10 ` Chris Murphy
2014-06-19 11:15 ` Austin S Hemmelgarn
2014-06-18 21:19 ` Imran Geriskovan [this message]
2014-06-19 0:07 ` Russell Coker
2014-06-19 8:58 ` Imran Geriskovan
2014-06-19 9:11 ` Imran Geriskovan
2014-06-21 19:19 ` Daniel Cegiełka
2014-06-22 1:36 ` Chris Murphy
2014-06-21 19:12 ` Daniel Cegiełka
2014-06-22 1:34 ` Chris Murphy
2014-06-22 7:49 ` Imran Geriskovan
2014-06-22 13:44 ` George Mitchell
2014-06-22 14:11 ` Roman Mamedov
2014-06-22 14:41 ` George Mitchell
2014-06-22 14:46 ` George Mitchell
2014-06-22 18:56 ` Chris Murphy
2014-06-22 18:47 ` Chris Murphy
2014-06-23 2:10 ` Duncan
2014-06-23 12:24 ` Martin K. Petersen
2014-06-24 5:37 ` Duncan
2014-06-25 13:01 ` Imran Geriskovan
2014-06-25 16:01 ` Duncan
2014-06-26 18:26 ` Imran Geriskovan
2014-06-26 18:41 ` Chris Murphy
2014-06-26 20:46 ` Imran Geriskovan
2014-06-22 18:31 ` Chris Murphy
2014-06-23 11:34 ` Martin K. Petersen
2014-06-19 1:01 ` George Mitchell
2014-06-19 4:52 ` Russell Coker
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='CAK5rZE7Gx2H1Fg=bNBqwNV1iDFnLNxu9B+odGUAeEeR2eO8bEQ@mail.gmail.com' \
--to=imran.geriskovan@gmail.com \
--cc=daniel.cegielka@gmail.com \
--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 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.