From: seriv@parkheights.dyndns.org
To: linux-btrfs@vger.kernel.org
Subject: 1 of 2 fetures I like in zfs
Date: Tue, 26 Aug 2008 11:55:35 -0400 (EDT) [thread overview]
Message-ID: <966396367.791219766135858.JavaMail.root@parkheights.dyndns.org> (raw)
In-Reply-To: <744323790.671219733451692.JavaMail.root@parkheights.dyndns.org>
Hi,
I've tried btrfs from stable mercurial repository, and I'd like to thank for one of 2 zfs features I missed in linux.
Now I can make snapshot before doing something risky and revert back to the snapshot if needed. Easily and quickly.
I can mount this snapshot on the mountpoint where the original filesystem was mounted.
One question: can I make this snapshot to have name 'default', replacing what was 'default' and screwed so that I've decided to rollback to the snapshot?
But one of the features I don't see and I don't see any plan to implement it is incremental snapshots. Example: I have btrfs volume on some computer and have created snapshot and have sent it to another computer as a backup. Then, the next day, after some files are changed/deleted/created, and snaphot differ from the active volume by some percent of blocks, I want to have it sent to another computer as incremental backup. Zfs can send only the blocks changed, no need to scan and compare all the files. If btrfs has this feature, then I would consider replacing solaris on many of our systems by linux with btrfs.
--
Sergey Ivanov.
next parent reply other threads:[~2008-08-26 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <744323790.671219733451692.JavaMail.root@parkheights.dyndns.org>
2008-08-26 15:55 ` seriv [this message]
2008-08-26 17:49 ` 1 of 2 fetures I like in zfs Eric Anopolsky
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=966396367.791219766135858.JavaMail.root@parkheights.dyndns.org \
--to=seriv@parkheights.dyndns.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox