© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Thanks @lauwersm and @decui. Our comments seem to have no effect at all. Yesterday was a read-only day again. Just two weeks after the previous one. So now it happens two times a month, which is 2 out of 8 backups. This is just too often, too expensive in labour and really unworkable.
Also, the write latency is extraordinary. Yesterday some data import was busy (over the network) when the backup started. Took more than 3 hours to complete. After backup was finished, I started the import again, just to see the difference. Took just 45 minutes. I would be more than happy to show an engineer our problem.
Maybe someone knows how to soft reboot a machine when in read-only state? This could help reducing the pain. But I really really want to urge getting a final solution. The problem was issued at April 30. My report at the Microsoft forum was at May 8, and that was after 40 days of problems already. So this bugging us for almost 10 months.