Re: way too high reconstruction speed - bug?

2006-08-11 Thread Tomasz Chmielewski
Paul Clements wrote: Tomasz Chmielewski wrote: [42949428.59] md: md11: raid array is not clean -- starting background reconstruction [42949428.62] raid10: raid set md11 active with 4 out of 4 devices [42949428.63] md: syncing RAID array md11 [42949428.63] md: minimum

Re: Resize on dirty array?

2006-08-11 Thread John Stoffel
Mark == Mark Hahn [EMAIL PROTECTED] writes: RAID is no excuse for backups. Mark I wish people would quit saying this: not only is it not helpful, Mark but it's also wrong. You've got to be kidding, right? A backup is another aspect of data protection. RAID is another form. Both have their

Re: Resize on dirty array?

2006-08-11 Thread David Rees
On 8/10/06, dean gaudet [EMAIL PROTECTED] wrote: - set up smartd to run long self tests once a month. (stagger it every few days so that your disks aren't doing self-tests at the same time) I personally prefer to do a long self-test once a week, a month seems like a lot of time for

Re: Resize on dirty array?

2006-08-11 Thread David Rees
On 8/11/06, dean gaudet [EMAIL PROTECTED] wrote: On Fri, 11 Aug 2006, David Rees wrote: On 8/10/06, dean gaudet [EMAIL PROTECTED] wrote: - set up smartd to run long self tests once a month. (stagger it every few days so that your disks aren't doing self-tests at the same time) I

Re: Resize on dirty array?

2006-08-11 Thread Brad Campbell
David Rees wrote: I personally prefer to do a long self-test once a week, a month seems like a lot of time for something to go wrong. unfortunately i found some drives (seagate 400 pata) had a rather negative effect on performance while doing self-test. Interesting that you noted negative