On Sun, 2 Dec 2007, Oliver Martin wrote:
[Please CC me on replies as I'm not subscribed]
Hello!
I've been experimenting with software RAID a bit lately, using two
external 500GB drives. One is connected via USB, one via Firewire. It is
set up as a RAID5 with LVM on top so that I can easily
Justin Piszcz schrieb:
It rebuilds the array because 'something' is causing device
resets/timeouts on your USB device:
Dec 1 20:04:49 quassel kernel: usb 4-5.2: reset high speed USB device
using ehci_hcd and address 4
Naturally, when it is reset, the device is disconnected and then
Justin Piszcz schrieb:
Naturally, when it is reset, the device is disconnected and then
re-appears, when MD see's this it rebuilds the array.
Least you can do is to add an internal bitmap to your raid, this will
make rebuilds faster :-/
--
Janek Kozicki
On Sunday December 2, [EMAIL PROTECTED] wrote:
Anyway, the problems are back: To test my theory that everything is
alright with the CPU running within its specs, I removed one of the
drives while copying some large files yesterday. Initially, everything
seemed to work out nicely, and by the
On Mon, 3 Dec 2007, Neil Brown wrote:
On Sunday December 2, [EMAIL PROTECTED] wrote:
Anyway, the problems are back: To test my theory that everything is
alright with the CPU running within its specs, I removed one of the
drives while copying some large files yesterday. Initially, everything
Justin Piszcz wrote:
While we are on the subject of bad blocks, is it possible to do what
3ware raid controllers do without an external card?
They know when a block is bad and they remap it to another part of the
array etc, where as with software raid you never know this is happening
until
Neil Brown schrieb:
This isn't a resync, it is a data check. Dec 2 is the first Sunday
of the month. You probably have a crontab entries that does
echo check /sys/block/mdX/md/sync_action
early on the first Sunday of the month. I know that Debian does this.
It is good to do this
