All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: john@grabjohn.com (John Bradford)
Cc: rddunlap@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Undelete files on ext3 ??
Date: Wed, 8 Jan 2003 23:14:40 +0000 (GMT)	[thread overview]
Message-ID: <200301082314.h08NEe56003842@darkstar.example.net> (raw)
In-Reply-To: <200301082303.h08N3bvI003752@darkstar.example.net> from "John Bradford" at Jan 08, 2003 11:03:37 PM

> > > | > > What I was thinking of was a virtual device that allocated
> > > | > > a new sector whenever an old one was overwritten - kind of
> > > | > > like a journaled filesystem, but without the filesystem,
> > > | > > (I.E. just the journal) :-).
> > > | >
> > > | > $ DIR FOO.TXT;*
> > > | > FOO.TXT;1   FOO.TXT;2   FOO.TXT;2
> > > | >
> > > | > VMS-style file versioning, anybody? ;)
> > > |
> > > | Brilliant!
> > > 
> > > re-read the archives from 6-8 months ago.
> > 
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=101914252421742&w=2
> 
> So basically the idea already already exists:
> 
> http://www.netcraft.com.au/geoffrey/katie/
> 
> Brilliant!  :-)

Although I was originally thinking of doing it at sector level, rather
than at filesystem level.

John.

  reply	other threads:[~2003-01-08 23:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07  3:58 Undelete files on ext3 ?? Max Valdez
2003-01-07  8:59 ` Marco d'Itri
2003-01-07  8:59 ` John Bradford
2003-01-07  9:29   ` Maciej Soltysiak
2003-01-07  9:45     ` Jan Hudec
2003-01-07 17:38       ` Max Valdez
2003-01-07 17:53         ` Andreas Dilger
2003-01-07 17:57         ` John Bradford
2003-01-07 18:56           ` Andreas Dilger
2003-01-07 18:17         ` Richard B. Johnson
2003-01-07 18:41           ` Virtual WORM device John Bradford
2003-01-07 18:53             ` Andreas Dilger
2003-01-07 18:54             ` John Bradford
2003-01-08 18:24             ` Vishal Verma
2003-01-07 18:45           ` Undelete files on ext3 ?? Jesse Pollard
2003-01-07 18:55           ` Andreas Dilger
2003-01-08  5:01             ` Gerhard Mack
2003-01-08  8:00               ` Jan Hudec
2003-01-08 10:57                 ` John Bradford
2003-01-08 21:33                   ` Valdis.Kletnieks
2003-01-08 21:47                     ` John Bradford
2003-01-08 21:51                       ` Randy.Dunlap
2003-01-08 22:06                         ` Valdis.Kletnieks
2003-01-08 23:03                           ` John Bradford
2003-01-08 23:14                             ` John Bradford [this message]
2003-01-09  9:42                     ` Helge Hafting
2003-01-07 20:58           ` Mike Waychison
2003-01-09  8:27           ` Michael Knigge
     [not found]         ` <Pine.LNX.3.95.1030107131613.3523A-100000@chaos.analogic.co m>
2003-01-07 23:51           ` Billy Rose
2003-01-07 11:30     ` John Bradford
2003-01-07 11:45       ` Matti Aarnio
2003-01-07 12:39       ` Alan Cox
2003-01-08 20:00   ` Michael Milligan
2003-01-07  9:16 ` David van Hoose
2003-01-07 19:31 ` oford
2003-01-08 11:57 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-01-07  9:58 Alexander Sandler
2003-01-08 10:03 bart

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=200301082314.h08NEe56003842@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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 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.