Crash - Corrupt File, Months of Work Lost

Miscellaneous Topics
#21

Future: Make daily backups. Keep three stages of backups. Test the backups, they can become currupt, too. Yes, I’m doing this, since I lost a HD to to a hardware error. It happens.

Present: The key question is, are there still sectors on your HD containing the original, or recent file data, or were those overwritten? Restore Software onyl will try to restore the last version of the file, but there might be stray sectors with older versions. Unless you have some think like secure delete or such running. I’d say, if there are really months of work lost (and will need months to recreate), try this:

Create full image of the hard disk (e.g. with linux command dd (Disk Dump) and then search this image for fragments of the code which you can remember. If you are lucky, there is still something there. This will take less than some months, but it’s tedious.

Problem: this image will require a HD larger than the original one to be kept and searched.

#22

Yeah I can see that. but that implies a lot of skill, knowledge and experience with a version control system. I had so many conflicts and many times destroyed the whole repository that I just got burned too much to trust such a system. I do backup old versions of my code as zip files with time stamps. I wouldnt use branches because while someone skilled sees them as incredible useful, I only see them as adding a lot of risk.

So basically: If you are really good with those systems, I would agree.

#23

Are you sure the filesystem doesn’t have a previous version of the file?

If the file has been on your harddrive for more than 24 hours, there should be a backup.

#24

Scroll up a few posts. Slyth found and recovered the file.

#25

It’s a shame - VC is one of those funny things maybe you have to see in action (nothing fancy even, just basic usage) to understand the productivity improvement. It helps to be shown by work colleagues the basics of how to do it though - I think it’s common for people to not get over that initial hump just working alone, and stick to big zip-ups. Definitely worth it once you “get it” though - I don’t know if I could work without a repository now, it’d be like not having a debugger or something.

Maybe put it down as something to try again later if this latest scare hasn’t forced you into it :smiley:

#26

Yeah fortunately I did find an exe and decompile it to get the base code. Unfortunately the variable names are crap but right now I’m trying to use the PDB to get them back as well. I now have everything backed up in the cloud and an external drive.

#27
  1. “Implies a lot of skill” - No. The basics are simple as shit and already infinitely imporoves your workflow.
  2. “Those systems” - No, we’re not talking about 10 year old centralized SVN tomfoolery here.
  3. “I had so many conflicts and many times destroyed the whole repository that I just got burned too much to trust such a system.” - Tea, Rocket launchers and barbie dolls makes as much sense as what you just said.

Nobody cares what anyone uses personally - but please don’t spread misinformation based on almost a decade old prejudiced experiences.

Throwing around tarballs was viable and even preferred well over half a decade ago but times have changed. And for the better, too. Sweet silky smooth baby jesus they have.

#28

Lol i do same in past xD

and now i think that i can make from all this zips git rep ^^

Its only looks like that, in Git technical you need 3 command main command:
Commit, pull, push + (some times git clone and git new rep)
That’s all)
I Use for win Tortoise git

Commits for local server ,so if you want: you even don’t need register something in internet simple local backup.

Yes if you fears corrupt files, zips with data better then Local corrupt rep.
But you can same zip copy of local rep)
And in one click make copy in internet

So with git you can faster find file history then using zip.

#29

It does take some effort to learn, respectively to master a tool like Git. As Linux originated tool it is a Geek tool. But you can start small with the basics and still benefit. Especially light weight branches are very nice, as my current use case shows:
One game character needs some AI tweaking, but I do not know if it can be achieved satisfactory. So, I created a new branch just for tweaking the Assassin character of Biodrone Battle. Still, I can work towards the game release uninfluenced by that. If I get it done, the AI changes will be merged into the main branch easily, if not, the branch gets deleted.

#30

I use Git at work. 2 years professional experience with it. I WOULD explain more in detail if you hadn’t been so angry at someone talking about their opinion.
I didn’t spread any misinformation, as I obviously stated “I got burned using it” as in MY experience and not gospel. I said “I dont use…” not “you shouldn’t”.
Also SVN sadly still seems to be industry standard, doesnt matter how old it is. Change takes time.

@Icecore:
Yeah a lot of the advantages 65K brought up do require branching. Which is where you can easily fuck up. Granted I always used command line since all the tools on mac cost money or confused me.

#31

I am backing up most of the stuff I use at bitbucket, free private repos. For public repositories I use github :slight_smile: