- 1. ANS1289W - bad areas on disk (score: 1)
- Author: Matthew Large <Matthew.Large AT AVIVA DOT COM>
- Date: Mon, 20 Jun 2005 15:36:02 +0100
- We had an image backup failure over the weekend. The schedule started as it normally does at 08:30am, but it was stopped a few hours later (he had expected it to use two drives), so he updated the sc
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00445.html (15,302 bytes)
- 2. Re: ANS1289W - bad areas on disk (score: 1)
- Author: "Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM>
- Date: Mon, 20 Jun 2005 09:39:59 -0500
- Making an educated WAG here, but I'd say that the drop in communication (rc: -50) between the client and server is more likely the source of your problem, rather than bad disk sectors. Image backups
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00446.html (13,109 bytes)
- 3. Re: ANS1289W - bad areas on disk (score: 1)
- Author: Matthew Large <Matthew.Large AT AVIVA DOT COM>
- Date: Mon, 20 Jun 2005 16:03:17 +0100
- I thought that initially aswell, but the rc-50s are prior to the actual backup. it was rescheduled to run at 10:30, after a false 2 hour start from 8:30 am. Those ANS1289W's appear after the client a
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-06/msg00447.html (20,885 bytes)
This search system is powered by
Namazu