From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Grantham Subject: Re: Preparation advice? Date: Sun, 28 Nov 2004 18:33:16 -0500 Message-ID: <6d5bedd804112815333c3c38e5@mail.gmail.com> References: <6d5bedd8041128053635740144@mail.gmail.com> <200411281800.iASI0xN00332@www.watkins-home.com> Reply-To: Ewan Grantham Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200411281800.iASI0xN00332@www.watkins-home.com> Sender: linux-raid-owner@vger.kernel.org To: Guy Cc: David Greaves , linux-raid@vger.kernel.org List-Id: linux-raid.ids On Sun, 28 Nov 2004 13:00:54 -0500, Guy wrote: > This is normal (IMO) for a 2.4 kernel. > I think it has been fixed in the 2.6 kernel. But I have never used the > newer kernel, so I can't confirm that. It may have been a newer version of > mdadm, not the kernel, not sure. A rather different definition of normal - but for a computer system I guess I shouldn't be that surprised :-) I'm not overly inclined to move to the 2.6 kernel at the moment as my experience with IEEE1394 under 2.6 has been very mixed. I think it's because it's easier to see what's happening "under the hood" with the 2.4 code. Since I gather you haven't seen any lost data from this, then I'm going to start filling up. Did a couple test captures today without any dropped frames, so I'm feeling a bit more comfortable that this is going to work. Assuming I bought some more drives in the future, would I be better off getting another firewire card or two, or going with USB 2? Thanks again for all the help and advice, Ewan