Date: Fri, 16 May 2003 11:19:05 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Drew Tomlinson <drew@mykitchentable.net> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Vinum & Firewire? Message-ID: <20030516014905.GB21491@wantadilla.lemis.com> In-Reply-To: <01c401c31b2f$da567d60$6e2a6ba5@tagalong> References: <01c401c31b2f$da567d60$6e2a6ba5@tagalong>
next in thread | previous in thread | raw e-mail | index | archive | help
--N+dhEFW7Y2Uiel/w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thursday, 15 May 2003 at 15:18:03 -0700, Drew Tomlinson wrote: > I have created a large vinum volume consisting of one concatenated plex. > The volume uses 3 drives. Two of the three are IDE drives mounted in the > system case and attached to the IDE controller on the motherboard. A vol= ume > made from these two drives functioned flawlessly for over a year. > > Then the volume finally filled so I added another IDE drive. However I d= id > not have room in the system case so I put the drive in a firewire enclosu= re > and added a firewire card to the system. Everything seems to work fine o= nce > the system is up and running. > > The problem is that upon boot, the firewire drive is not available to vin= um > as indicated in this 'list' command: > > D ftp2 State: referenced Device Avail: 0/0 MB > > Which, of course, leads to a 'corrupt' plex and 'crashed' subdisk: > > P ftp.p0 C State: corrupt Subdisks: 3 Size: 223 = GB > S ftp.p0.s2 State: crashed PO: 149 GB Size: 74 = GB > > I suspect the cause is that the firewire drive is not ready at the time > vinum starts.=20 That's one possibility. > Can anyone confirm or deny this? I haven't used firewire at all, so I can't say. But it would seem that if you stop Vinum and start it when the firewire drive is up, you should be able to confirm this yourself by restarting and seeing what happens. > Is there a way to add a delay in the boot process to allow the > firewire drive extra time? I'm sure there is, but first we should determine whether that's really the problem. > Should I not use vinum with firewire devices? That would be a workaround. It should definitely work. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers --N+dhEFW7Y2Uiel/w Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE+xEORIubykFB6QiMRAm62AJ9BnCsHSbl1igmjtOcOx5a1PO6jNACbBNaE f4OVjyHvBB2mDWBsVrald2M= =aP39 -----END PGP SIGNATURE----- --N+dhEFW7Y2Uiel/w--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030516014905.GB21491>