> My informal undelete solution is to turn the power off (or hit the
> reset or suspend switch) as soon as I realize I made a stupid
> mistake. This works for me about 70% of the time (5 seconds is a
> _really_ long time after you've wipe out a module you've been working
> on for 18 hours.) though it didn't help the time I miscoded something
> in McAfee's Virus Scan and ended up eating /home/orc on my development
> laptop [thank goodness for the ext2fs editor.]
..this is exactly why I set my update to 30 seconds - so that i have
more time to turn it off.
> This thing needs to have a tool that can manipulate whiteout entries,
> and a daemon that can reap whiteout entries when the disk gets full,
> but those are pretty trivial compared to keeping and having to
> rewrite applications to understand .deleted directories (when talking
> about tweaking filesystem intrinsics, userspace solutions suck on
> monolithic kernels.)
Actually, making use of .deleted directories is pretty trivial, you
have just to play with LD_PRELOAD a bit. I have written it, once, and
project died on non wanting to write cache reaper ;-). This means that
if you promise to provide cache reaper, I can easily write mover to
.deleted directory.
Pavel
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/faq.html