Odd subject line isn't it? 
In my Documents subdirectory it produces a weird looking file name with 0 bytes content. Try to open it and you get "file by that nome does not exist". "rm" doesn't work in the console, either. Selecting "delete" from the right mouse option panel "deletes" it, and everything else in the Documents subdirectory. The errant file magically re-appears in the directory above Documents, which is my home directory.
I chose the recovery mode and fsck was run, but it didn't fix the problem. So, if I delete it from my home directory I suspect that it will jump to the root directory.
Anyone ever hear of this?
EDIT:
In Googling I've found that there are cases of data loss with EXT4. It seems that EXT4 uses "dataallocation" to delay committing data to the HD in order to improve speed. EXT3 doesn't have a data loss problem because it flushes the buffers to the HD every 5 seconds, which adds to the overhead. Some folks have written scripts interecpt "halt" or "reboot" and sync the HD before halt or reboot is executed.
I booted a Karmic LiveCD and from it executed e2fsck.ext4 -f -E fragcheck /dev/sda5. It reported several misdirected pointers. When I rebooted the bad file was still there.
So, I created a second account for me with my rights and then tried "rm" on the ifile in my original account. The file disappeared and everything remains in the root of my home account. I rebooted and the bad file didn't return and everything else did.
Weird.
In my Documents subdirectory it produces a weird looking file name with 0 bytes content. Try to open it and you get "file by that nome does not exist". "rm" doesn't work in the console, either. Selecting "delete" from the right mouse option panel "deletes" it, and everything else in the Documents subdirectory. The errant file magically re-appears in the directory above Documents, which is my home directory.
I chose the recovery mode and fsck was run, but it didn't fix the problem. So, if I delete it from my home directory I suspect that it will jump to the root directory.
Anyone ever hear of this?
EDIT:
In Googling I've found that there are cases of data loss with EXT4. It seems that EXT4 uses "dataallocation" to delay committing data to the HD in order to improve speed. EXT3 doesn't have a data loss problem because it flushes the buffers to the HD every 5 seconds, which adds to the overhead. Some folks have written scripts interecpt "halt" or "reboot" and sync the HD before halt or reboot is executed.
I booted a Karmic LiveCD and from it executed e2fsck.ext4 -f -E fragcheck /dev/sda5. It reported several misdirected pointers. When I rebooted the bad file was still there.
So, I created a second account for me with my rights and then tried "rm" on the ifile in my original account. The file disappeared and everything remains in the root of my home account. I rebooted and the bad file didn't return and everything else did.
Weird.