From: Gaurav Saxena <grvsaxena419@gmail.com>
To: Wojciech Zygmunt Porczyk <wojciech@porczyk.eu>
Cc: John Stoffel <john@stoffel.org>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Intercepting system calls
Date: Thu, 29 Dec 2011 12:08:33 +0530 [thread overview]
Message-ID: <CAOh0hwP=Pq0Gbd002QGVvULNj60o2RPR3sZz94RVZvM2pstVzQ@mail.gmail.com> (raw)
In-Reply-To: <20111228125631.GB9894@nb24cis>
Hello Wojciech, Thanks for your reply.
On 12/28/11, Wojciech Zygmunt Porczyk <wojciech@porczyk.eu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, Dec 23, 2011 at 10:33:45PM +0530, Gaurav Saxena wrote:
>> I am trying to write an application which would create a backup for
>> the system so that it could be restored as it is. For example I create
>> a backup using my application. I just do nothing at time of backup so
>> it would be fast. Now whenever I see any deletion I would save that
>> file so that I could restore it.
>
> You almost certainly wan't to research LVM(-like) snapshots. They are
> operating in block layer, so you can restore fs "as it was", with COW
> feature they do "nothing" at creation and just save overwritten data
> somewhere else.
Yes I understand what I want to implement is done in LVM snapshots.
But I want to implement this functionality using a different approach.
As LVM are filesystem dependent and cannot work without repartitioning
of the system. Also they make system slow after many snapshots are
created.
>
> See: lvcreate(8), xfs_freeze(8). Maybe btrfs(8) ("btrfs subvolume
> snapshot") but btrfs is not really production-ready, so get lvm2+xfs.
>
> - --
> regards
> WZJP
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.18 (GNU/Linux)
>
> iEYEARECAAYFAk77Ef8ACgkQDgvLOJe6jMmQuACfassIV+vXCTmvMCTUqa81wgFf
> lBcAoLwYdPf59FEJ7sl/lzyHLLo4pG2r
> =Zt0G
> -----END PGP SIGNATURE-----
>
--
Thanks and Regards ,
Gaurav
next prev parent reply other threads:[~2011-12-29 6:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 16:07 Intercepting system calls Gaurav Saxena
2011-12-22 16:42 ` richard -rw- weinberger
2011-12-22 16:59 ` Gaurav Saxena
2011-12-22 17:05 ` richard -rw- weinberger
2011-12-22 17:16 ` Gaurav Saxena
2011-12-22 17:32 ` richard -rw- weinberger
2011-12-22 17:37 ` Gaurav Saxena
2011-12-22 17:52 ` John Stoffel
2011-12-23 2:22 ` Gaurav Saxena
2011-12-23 14:38 ` John Stoffel
2011-12-23 17:03 ` Gaurav Saxena
2011-12-28 12:56 ` Wojciech Zygmunt Porczyk
2011-12-29 6:38 ` Gaurav Saxena [this message]
2011-12-23 14:50 ` Alan Cox
2011-12-23 17:07 ` Gaurav Saxena
2011-12-22 19:03 ` Wakko Warner
2011-12-23 2:25 ` Gaurav Saxena
2011-12-23 9:45 ` Jiri Kosina
2011-12-23 15:10 ` Wakko Warner
2011-12-23 7:25 ` J. R. Okajima
2011-12-23 9:08 ` Gaurav Saxena
2011-12-23 9:16 ` richard -rw- weinberger
2011-12-23 9:22 ` Gaurav Saxena
2011-12-23 9:26 ` richard -rw- weinberger
2011-12-23 9:37 ` Gaurav Saxena
2011-12-23 9:47 ` Jiri Kosina
2011-12-23 9:50 ` Gaurav Saxena
2011-12-23 11:59 ` Gaurav Saxena
2011-12-23 12:29 ` Maxin B John
2011-12-23 12:50 ` Gaurav Saxena
2011-12-23 13:00 ` richard -rw- weinberger
-- strict thread matches above, loose matches on Subject: below --
2010-02-04 19:00 Oleg Kutkov
2010-02-04 19:26 ` Bryan Donlan
[not found] ` <5e9821061002042140le7ba356s48e535c9d8b637ec@mail.gmail.com>
2010-02-05 7:20 ` Bryan Donlan
2004-12-21 4:22 selvakumar nagendran
2004-12-21 4:28 ` Lee Revell
2004-12-21 13:51 ` Steven Rostedt
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='CAOh0hwP=Pq0Gbd002QGVvULNj60o2RPR3sZz94RVZvM2pstVzQ@mail.gmail.com' \
--to=grvsaxena419@gmail.com \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=wojciech@porczyk.eu \
/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).