Well, I wasn't fast enough on the snapshot...

["Michael B. Trausch" <mbt@zest.trausch.us>]

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

I had sent something and forgot to send it to the list, and then before
I went to re-send it, I thought I'd take a look at an idea that I had.
As best as I can tell, I either didn't yank the filesystem offline
quickly enough, or I must have let some other activity I didn't
anticipate (maybe a journal replay) occur.

Whatever the cause, it would appear that at least the über-important
files that I needed (the history database packs) to make the recovery
possible in the first are more than slightly overwritten with totally
unrelated garbage.  Without them being completely intact, of course,
they are useless, so I did in fact lose a week of work.

Ugh.

All of this said, I remember reading about an undelete mode being
proposed for ext4.  Are there still plans to implement that in ext4 (or
an extension to it) at some point in the future?  It would be kind of
nice to be able to have an assurance that you'd be able to recover
something you _just_ deleted (FSVO "just", of course).  Maybe not quite
freeing up blocks until a certain amount of time has passed or some
other constraint, like space, is hit.  I don't know if that is at all
plausible or not, just my uneducated attempt at an idea---but in any
case, something like that would be kind of nice to have.  I haven't
shot myself in the foot like this in years... but as I recall, last
time I did, I lost more work than this time.

At least I have the current state of the working trees.  Their history
is just gone.  Oh, well.

Thanks for all the comments and ideas!

	--- Mike

-- 
Don't wait until you have a bug to step through your code.
                            --- Steve Maguire

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]