Hi there,

Today I open Skrooge and I saw an empty windows. Then I tried to open the file and ... simply it isn't there.

I know I've not deleted it, but it just disappeared.

Few days agoy I had a trouble with a crazy log file (.xerrors) that filled the entire disk, so when I close some tools they complained about full disk and couldn't save the data. I don't remember if Skrooge was oen of them, but ... I could undertand that wasn't able to save new data, but deleting the old file?

Could it be posible?

Thanks

Hi,
I will analyze Skrooge source code to try to understand.
I never heard/see something like this.

Nevertheless, you should have a backup file automatically created by Skrooge before each save.
By default, this file is in the same directory with extension .old.

Regards.

I have configures Skrooge to save a backup automatically, but the .old file isn't there either

Last manual backup I have is eight month old. Of course it is my fault, but I still can't understand how it could happen!

I don't understand too.

Maybe you still have the working copy.
The working copy is name .<name of you file>.wk !

No, I have not the working copy. I've assumed that I will have to rebuild my last eight months

Anyway, thinking forward, the test I think you should do to verify if there is a problem is:

1. Open Skrooge with a file
2. With Skrooge running, fill the whole disk with anything (in my case was a defunc proccess writing to .xsession-errors)
3. With the disk completely full ... close Skrooge.

And then, check if the files are still there ...

Sounds like you need to do some housekeeping. ncdu is a good tool to find space hoggers. Once you've done that go for a

sudo updatedb

followed by a

locate name_of_scrooge_file

All the best!

You've probably already done this, but being a fellow human subject to the failings of mortal flesh, I humbly suggest double checking that the skrooge file(s) really isn't there. All that silly stuff like "looking in the wrong directory" or "somehow I moved all these to the wrong place". No offense, of course, I just know our species has a tendency to sometimes unintentionally overlook the obvious.

If it's really gone, you still might be able to save your bacon with photorec. PhotoRec doesn't have .skg as a recognized file pattern, but you can add your own: http://www.cgsecurity.org/wiki/Add_your_own_extension_to_PhotoRec. It looks like the magic value of a skrooge is "SKROOGE_DECRYPTED-SQLite" at offset 0. Then you could try to find your file even if it's been truly deleted and possibly save a ton of work. Might be worth a shot . . .

toad wrote:Sounds like you need to do some housekeeping. ncdu is a good tool to find space hoggers. Once you've done that go for a

sudo updatedb

followed by a

locate name_of_scrooge_file

rbruce wrote:You've probably already done this, but being a fellow human subject to the failings of mortal flesh, I humbly suggest double checking that the skrooge file(s) really isn't there. All that silly stuff like "looking in the wrong directory" or "somehow I moved all these to the wrong place". No offense, of course, I just know our species has a tendency to sometimes unintentionally overlook the obvious.

Thanks for the suggestion but, of course, I've look for the files even under the carpets, and no, the files aren't there.

rbruce wrote:If it's really gone, you still might be able to save your bacon with photorec. PhotoRec doesn't have .skg as a recognized file pattern, but you can add your own: http://www.cgsecurity.org/wiki/Add_your ... o_PhotoRec. It looks like the magic value of a skrooge is "SKROOGE_DECRYPTED-SQLite" at offset 0. Then you could try to find your file even if it's been truly deleted and possibly save a ton of work. Might be worth a shot . . .

I tried with extundelete, not the same that PhotoRec, but with similar idea, but the problem is that I'm afraid that files were lost because a log file filled the whole disk, so any trace of a deleted or corrupted file was completely overwritten

Of course, yesterday I made a little script to save on the cloud a copy of my Skrooge file, weekly. This shouldn't happen to me again.

Anyway, thanks for the ideas.

JesusM wrote:I tried with extundelete, not the same that PhotoRec, but with similar idea, but the problem is that I'm afraid that files were lost because a log file filled the whole disk, so any trace of a deleted or corrupted file was completely overwritten

Sorry, that's sad to hear. Who needs secure wiping utilities when we've got runaway logs?

Hi,

I reproduce the issue.
In fact skrooge did something like this:
1-Remove the target file
2-Copy the working copy in target file
And when Skrooge is closed:
3-Remove the working copy

So, in case the step (2) fails, you have an interactive error but the previous file has been removed.

I did a correction based like this:
1-Rename the target file in the target file+"~"
2-Copy the working copy in target file
3-In case of failure: Rename the target file+"~" in target file

Sorry for this bug causing the deletion of your file.
Thank you for still using Skrooge.

The point is to find the bug and fix it.

Thanks for your work.

smankowski wrote:Hi,

I reproduce the issue.
In fact skrooge did something like this:
1-Remove the target file
2-Copy the working copy in target file
And when Skrooge is closed:
3-Remove the working copy

So, in case the step (2) fails, you have an interactive error but the previous file has been removed.

I did a correction based like this:
1-Rename the target file in the target file+"~"
2-Copy the working copy in target file
3-In case of failure: Rename the target file+"~" in target file

Sorry for this bug causing the deletion of your file.
Thank you for still using Skrooge.

When you can ... a tar file with sources would be apreciate for those who don't know how to use git

Hi,

The tar file is here:
http://download.kde.org/unstable/skroog ... 93.tar.bz2

Regards.