Skip to main content
15 events
when toggle format what by license comment
Jul 14, 2016 at 8:40 comment added ctrl-alt-delor It is possible to write to a file, then read it (this reads from cache in ram), then before the file is written to disk to crash the machine, and loose the data. To prevent this then you need to use a journalling file-system (that is configured correctly).
Apr 11, 2014 at 12:27 comment added Stephan Ok I'll ask them to check the memory. Somehow I'm not convinced that a crash was the reason, because I could open/modify the files - then a reboot happened and (I guess) after that the content of the files was lost. Any luck with looking at log files?
Apr 9, 2014 at 15:06 comment added psusi Then there you go; it crashed and rebooted before the data hit the disk, so it was lost.
Apr 9, 2014 at 14:47 history edited Stephan CC BY-SA 3.0
added 150 characters in body
Apr 9, 2014 at 14:41 comment added Gilles 'SO- stop being evil' @Stephan If it's a VM then you'd need to test the memory of the host.
Apr 9, 2014 at 14:38 comment added Stephan @Gilles - thank's for the hint, but I can't access Grub (virtual machine)
Apr 9, 2014 at 14:37 comment added Stephan @psusi - it's a virtual machine on our institutes server infrastructure. I saw that it was rebooted but I don't know if it crashed - definitely right after it was written.
Apr 9, 2014 at 14:36 comment added Stephan @BaardKopperud - thanks for the hint, but the file was there the left time I logged into the system, now it's corrupted. I don't know exactly when the problem occurred.
Apr 8, 2014 at 22:59 comment added Gilles 'SO- stop being evil' The file is corrupted. If the system crashed before you saved the file or just as the file was being written, this is to be expected. Otherwise do a memory test (reboot and choose “memory test” at the Grub prompt, let it run for at least one full pass).
Apr 8, 2014 at 14:22 comment added psusi Did you neglect to mention that your system crashed/lost power shortly after you wrote that file?
Apr 8, 2014 at 11:28 history edited slm CC BY-SA 3.0
deleted 48 characters in body; edited tags
Apr 8, 2014 at 10:58 review First posts
Apr 8, 2014 at 11:10
Apr 8, 2014 at 10:54 comment added Baard Kopperud Could perhaps be a partially transferred/downloaded file? I know that at least several BitTorrent-clients creates files of the size it need for the file it's downloading, and then fill it with NUL - and if the download fails, NUL will be all the file contain. Don't think it's much you can do; you may have reserved space for the file, but you obviously haven't actually downloaded/transferred it.
Apr 8, 2014 at 10:50 answer added choroba timeline score: 3
Apr 8, 2014 at 10:41 history asked Stephan CC BY-SA 3.0