On Fri, Jul 10, 2015 at 09:36:45AM -0400, Austin S Hemmelgarn wrote:
> > Technically it's not really a bit. The snapshot relation is determined
> > by the parent uuid value of a subvolume.
> I'm actually kind of curious, is the parent UUID actually used for
> anything outside of send/receive?
AFA
On 2015-07-09 14:33, David Sterba wrote:
On Thu, Jul 09, 2015 at 08:48:00AM -0400, Austin S Hemmelgarn wrote:
On 2015-07-09 08:41, Sander wrote:
Austin S Hemmelgarn wrote (ao):
What's wrong with "btrfs subvolume snapshot"?
Well, personally I would say the fact that once something is tagged a
On Wed, Jul 08, 2015 at 09:20:46PM -0400, james harvey wrote:
> Would (I think):
> * btrfs subvolume create
> * cp -ax --reflink=always /* /
>
> Particularly useful to avoid "Invalid cross-device link" when using cp
> -ax, when source and dest are seen as different devices.
>
> Such as if there
On Thu, Jul 09, 2015 at 08:48:00AM -0400, Austin S Hemmelgarn wrote:
> On 2015-07-09 08:41, Sander wrote:
> > Austin S Hemmelgarn wrote (ao):
> >>> What's wrong with "btrfs subvolume snapshot"?
> >>
> >> Well, personally I would say the fact that once something is tagged as
> >> a snapshot, you can
On Thu, 09 Jul 2015 08:48:00 -0400
Austin S Hemmelgarn wrote:
> On 2015-07-09 08:41, Sander wrote:
> > Austin S Hemmelgarn wrote (ao):
> >>> What's wrong with "btrfs subvolume snapshot"?
> >>
> >> Well, personally I would say the fact that once something is tagged as
> >> a snapshot, you can't ch
Hugo Mills posted on Thu, 09 Jul 2015 13:54:48 + as excerpted:
> On Thu, Jul 09, 2015 at 01:43:53PM +, Duncan wrote:
>> I could have sworn btrfs property -t subvolume can get/set that
>> snapshot bit. I know I saw the discussion and I think patch for it go
>> by, but again, as I don't use
On Thu, Jul 09, 2015 at 01:43:53PM +, Duncan wrote:
> I could have sworn btrfs property -t subvolume can get/set that snapshot
> bit. I know I saw the discussion and I think patch for it go by, but
> again, as I don't use them, I haven't tracked closely enough to see if it
> ever got in.
Austin S Hemmelgarn posted on Thu, 09 Jul 2015 08:48:00 -0400 as
excerpted:
> On 2015-07-09 08:41, Sander wrote:
>> Austin S Hemmelgarn wrote (ao):
What's wrong with "btrfs subvolume snapshot"?
>>>
>>> Well, personally I would say the fact that once something is tagged as
>>> a snapshot, you
Austin S Hemmelgarn wrote (ao):
> On 2015-07-09 08:41, Sander wrote:
> >Austin S Hemmelgarn wrote (ao):
> >>>What's wrong with "btrfs subvolume snapshot"?
> >>
> >>Well, personally I would say the fact that once something is tagged as
> >>a snapshot, you can't change it to a regular subvolume witho
On 2015-07-09 08:41, Sander wrote:
Austin S Hemmelgarn wrote (ao):
What's wrong with "btrfs subvolume snapshot"?
Well, personally I would say the fact that once something is tagged as
a snapshot, you can't change it to a regular subvolume without doing a
non-incremental send/receive.
A snaps
Austin S Hemmelgarn wrote (ao):
> >What's wrong with "btrfs subvolume snapshot"?
>
> Well, personally I would say the fact that once something is tagged as
> a snapshot, you can't change it to a regular subvolume without doing a
> non-incremental send/receive.
A snapshot is a subvolume. There is n
On 2015-07-09 02:22, Fajar A. Nugraha wrote:
On Thu, Jul 9, 2015 at 8:20 AM, james harvey wrote:
Request for new btrfs subvolume subcommand:
clone or fork [-i []
Create a subvolume in , which is a clone or fork of source.
If is not given, subvolume will be created in the
current di
On Thu, Jul 9, 2015 at 8:20 AM, james harvey wrote:
> Request for new btrfs subvolume subcommand:
>
> clone or fork [-i []
>Create a subvolume in , which is a clone or fork of source.
>If is not given, subvolume will be created in the
> current directory.
>Options
>-i
>
Request for new btrfs subvolume subcommand:
clone or fork [-i []
Create a subvolume in , which is a clone or fork of source.
If is not given, subvolume will be created in the
current directory.
Options
-i
Add the newly created subvolume to a qgroup. This option can be
given
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
15 matches
Mail list logo
