From: greg.freemyer@gmail.com (Greg Freemyer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Snapshot in ext4
Date: Thu, 5 Jan 2012 14:17:15 -0500 [thread overview]
Message-ID: <CAGpXXZKGM-2Jkvpc=805c5E4JmanTfB+xgcyQUD6fJ6LTQkeSQ@mail.gmail.com> (raw)
In-Reply-To: <CAJokiOe9XBn+ee3=y2vtuUkt0SC9oJ-uJY1Zb_nFnK8a4k36pA@mail.gmail.com>
I missed this series of questions before:
On Wed, Jan 4, 2012 at 4:43 AM, Swapnil Gaikwad <swapnilgaik72@gmail.com> wrote:
> 1. Where to place snapshot files in filesystem level snapshot?
What does that even mean.
> 2. Is there any issues regarding it?
> 3. It is helpful to allocate new inode for a file od which snapshot is
> taken?
I told you NTFS does the equivalent of allocating a new inode and new
pointer blocks for any files which have both a previous version and a
current verson.
So with a file like a database table that has some common content
between live and previous versions, you end up with data pointer
blocks for each version. But they can point at the same data blocks
if the data blocks are unchanged.
So it clearly is a good way to do things. I don't know how btrfs or
next4 handle it, so I'm not saying it is the best way.
>
> --
> ??? Regards,
>
> Swapnil Gaikwad.
Greg
next prev parent reply other threads:[~2012-01-05 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:43 Snapshot in ext4 Swapnil Gaikwad
2012-01-05 19:17 ` Greg Freemyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-04 9:53 Swapnil Gaikwad
2012-01-05 19:21 ` Greg Freemyer
2012-01-04 9:55 Swapnil Gaikwad
2012-01-05 19:35 ` Greg Freemyer
2012-01-04 9:56 Swapnil Gaikwad
2012-01-05 19:40 ` Greg Freemyer
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='CAGpXXZKGM-2Jkvpc=805c5E4JmanTfB+xgcyQUD6fJ6LTQkeSQ@mail.gmail.com' \
--to=greg.freemyer@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).