treacl
October 3rd, 2010, 04:47 AM
I'm having a major, recurring problem with OO 3.2.0 on Ubuntu 10.04.1, which I installed about a month ago.
Because of some driver incompatibilities with my laptop (a ThinkPad X201), the OS occasionally freezes. Three times in a month, this has been followed by a failed OpenOffice document recovery that has resulted in the last "saved" version of the file being wiped out. When I say wiped out, I mean a file that showed as 35k before the freeze now shows as 0 bytes, or 1536 bytes, or some other very small number.
My guess is that this is caused because the OS is holding the data in cache for far too long, and thus the data are lost when the OS freezes. I am wondering specifically whether this has to do with the file system and/or the way I have it configured.
My last Ubuntu system never had this problem: It was version 8.04, using ext3 in an encrypted lvm. The explicit fstab options for the main lvm were relatime,errors=remount-ro. (I understand that this also implies data=ordered.)
My current system is version 10.04, using an ext2 boot partition and a main ext4 file system in an encrypted lvm. The explicit fstab options for the main partition are data=ordered,barrier=1,noatime,errors=remount-ro.
Can anyone suggest what I should do to troubleshoot the cause and/or make this more reliable?
Because of some driver incompatibilities with my laptop (a ThinkPad X201), the OS occasionally freezes. Three times in a month, this has been followed by a failed OpenOffice document recovery that has resulted in the last "saved" version of the file being wiped out. When I say wiped out, I mean a file that showed as 35k before the freeze now shows as 0 bytes, or 1536 bytes, or some other very small number.
My guess is that this is caused because the OS is holding the data in cache for far too long, and thus the data are lost when the OS freezes. I am wondering specifically whether this has to do with the file system and/or the way I have it configured.
My last Ubuntu system never had this problem: It was version 8.04, using ext3 in an encrypted lvm. The explicit fstab options for the main lvm were relatime,errors=remount-ro. (I understand that this also implies data=ordered.)
My current system is version 10.04, using an ext2 boot partition and a main ext4 file system in an encrypted lvm. The explicit fstab options for the main partition are data=ordered,barrier=1,noatime,errors=remount-ro.
Can anyone suggest what I should do to troubleshoot the cause and/or make this more reliable?