Firewire under WB3.0 (*was* Re: [WBEL-users] Backups?)

Kirby Bohling kbohling@birddog.com
Wed, 23 Jun 2004 15:03:12 -0500


On Mon, Jun 21, 2004 at 04:50:44PM -0500, John Morris wrote:
> On Sun, 20 Jun 2004, Paul wrote:
> 
> > I have a similar setup & situation (2x80GB Mirrored)... currently we
> > 
> > The tape drive cost $900 and the tapes are $65 each ... using hard
> > drives as back would end up costing the same.  The only thing I can
> > think off as a drawback is hot swapping the hard drives some IDE cards
> > support it.
> > 
> > Anybody tried firewire hard drives??
> 

<snip>

> 
> One warning with firewire though.  RH doesn't like Firewire, doesn't
> support it and didn't consider it a problem when FC2 shipped without
> Firewire support.  You can make it work with WBEL3 but it is a fair bit of
> trouble and considering the upstream situation there are no promises it
> will remain working, especially come WBEL4.  I'm speaking as someone with
> seven firewire drives in rotation as backup media and pondering options
> for the future.

John,

	I've just upgraded a RH9.0 machine to WBEL 3.0.  Unfortunately,
I didn't consider that Firewire could be a problem.  I had firewire
support under 9.0 running like a top.  Pretty much out of the box,
firewire worked just fine on 9.0.  It worked mostly fine with a bit
of tweaking on an 8.0 and a 7.2 machine.

	Any clues what I need to do to get it working on WBEL3.0?  I've
go the modules loading on boot, but it fails to add the drive to
/proc/partitions.  It doesn't auto add and remove the drives like it
does under RH9.  It also appears to have plenty of errors in dmesg
of this variety:

ieee1394: sbp2: aborting sbp2 command
Read (10) 00 06 02 4e 07 00 00 f8 00

	Any clues on what I'm doing wrong.  I load the same three
modules:

ohci1394
ieee1394
sbp2

I had to download and install rescan-scsi-bus.sh, and I run that
manually to add and remove drives.  I've compared /etc/hotplug from
the RH9 backups and the current install, they appear the same.  I've
got 3 drives in rotation, and I've got a CompUSA instore brand card
with a VIA 1394 chipset.

Do I just need to fiddle with the ieee1394.agent script and add the
appropriate rescan-scsi-bus.sh to the add and remove cases?

	Thanks,
		Kirby


	Thanks,
		Kirby