From: Roman Mamedov <rm@romanrm.net>
To: Bernd Lentes <bernd.lentes@helmholtz-muenchen.de>
Cc: "remi@georgianit.com" <remi@georgianit.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: rollback to a snapshot
Date: Thu, 8 Jun 2023 01:48:02 +0500 [thread overview]
Message-ID: <20230608014802.1dce81a0@nvm> (raw)
In-Reply-To: <PR3PR04MB7340C53376C738E6DDEA39B2D653A@PR3PR04MB7340.eurprd04.prod.outlook.com>
On Wed, 7 Jun 2023 20:14:27 +0000
Bernd Lentes <bernd.lentes@helmholtz-muenchen.de> wrote:
> I didn't know "--reflink". The help says:
> " When --reflink[=always] is specified, perform a lightweight copy, where the
> data blocks are copied only when modified. If this is not possible the copy
> fails, or if --reflink=auto is specified, fall back to a standard copy.
> Use --reflink=never to ensure a standard copy is performed.".
>
> Is that independent from the fs ? That seems to be a kind of a snapshot.
> Am i right ?
Not all filesystems support reflinks.
Btrfs and XFS support it, but for XFS this has to be enabled at FS creation
time (IIRC recent mkfs enables it by default). Ext4, ReiserFS and JFS do not.
For XFS it is a way to have the best of the both worlds: have a filesystem
that is well regarded for performance, but also gain a degree of the CoW
ability that Btrfs is liked for, e.g. allowing instant snapshots of VM images,
including running ones with a point-in-time full image consistency --
unthinkable with traditional copying.
--
With respect,
Roman
next prev parent reply other threads:[~2023-06-07 20:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 20:58 rollback to a snapshot Bernd Lentes
2023-06-06 23:20 ` Eldon
2023-06-07 4:36 ` Andrei Borzenkov
2023-06-07 10:38 ` Bernd Lentes
2023-06-07 11:51 ` Andrei Borzenkov
2023-06-07 20:08 ` Phillip Susi
2023-06-07 20:51 ` Bernd Lentes
2023-06-07 22:18 ` Nicholas D Steeves
2023-06-08 19:39 ` Bernd Lentes
2023-06-08 20:09 ` Bernd Lentes
2023-06-13 16:01 ` Bernd Lentes
2023-06-07 10:45 ` Bernd Lentes
2023-06-07 16:35 ` Andrei Borzenkov
2023-06-07 19:37 ` Bernd Lentes
2023-06-07 19:46 ` remi
2023-06-07 20:07 ` Bernd Lentes
2023-06-07 20:14 ` Bernd Lentes
2023-06-07 20:48 ` Roman Mamedov [this message]
2023-06-07 21:00 ` Bernd Lentes
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=20230608014802.1dce81a0@nvm \
--to=rm@romanrm.net \
--cc=bernd.lentes@helmholtz-muenchen.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=remi@georgianit.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.