-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stevens wrote:
I finally saw first hand the read-only BUG in suse 10.2. I was working on a 110MB PowerPoint presentation on a flash drive (using OpenOffice, of course) and when I went to save my work the system got about 1/3 of the way through, then threw a hissy fit (that's somewhat akin to a wall-eyed fit) and then went read only. It took a reboot and ultimately booting to a linux live cd and running fsck on the root partition before I got the system up and running again.
To test the theory posted here a few days ago that the bug involves high disk usage on different filesystems, I then copied the PP file over to the hard drive, then redid all the work and this time it worked as it should have.
The flash drive is FAT32, the hard drive is ext3.
YMMV.
Fred
In my case finally found the probable underlying cause was a hard drive that was slowly dying (the hard way). Unfortunately, what seems to have been happening was that access to the drive was locking up completely when reallocating faulty blocks but no error reporting was occurring (or to be probably more accurate, being caught). SMART reported nothing until about an hour before or so before I was due to go away for a couple of days (these things to have a lovely sense of timing :-( ).when it reported problems with a single sector. When I got back I found that the underlying damage was fairly extensive (and a lot more than a single sector). (BTW This is a Home/Test server so it could wait on the trip). The damage is such that the validity of some elements of the backed up data are questionable, (before anyone comments I do not think rsync and such tools would have helped a lot in this scenario, raid is a different story.. ). Little working data has been lost. The most problematic damage is that there are signs of some configuration information corruption, which is making a rebuild a little more complex than merely re-installing original configuration files. When I have finished picking through the ruins and getting things working I will to need to look closer at both SMART (and other tools) so that I can monitor for this kind of fault more effectively. Interestingly, from a 'fresh' installation now being offered an option which I was not offered in an upgrade install, which could have made the restoration process easier than it is at the moment. - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGjMJZasN0sSnLmgIRAlrtAJ4nhV80xgAPBNcygZfwcNX+pjyQ0gCgiXy3 GITiODb5KjUCfKOGZiqX7tA= =jx3F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org