From owner-freebsd-firewire@FreeBSD.ORG Mon Sep 18 11:08:08 2006 Return-Path: X-Original-To: freebsd-firewire@FreeBSD.org Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D133D16A4E2 for ; Mon, 18 Sep 2006 11:08:08 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8396F43D55 for ; Mon, 18 Sep 2006 11:08:08 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8IB88t3040945 for ; Mon, 18 Sep 2006 11:08:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8IB87LD040941 for freebsd-firewire@FreeBSD.org; Mon, 18 Sep 2006 11:08:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Sep 2006 11:08:07 GMT Message-Id: <200609181108.k8IB87LD040941@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 11:08:08 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w o kern/85434 firewire [fwip] fwip (IP over firewire) doesn't work with polli 2 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/95077 firewire [firewire] fatal trap 19 at fwohci_pci_init 1 problem total. From owner-freebsd-firewire@FreeBSD.ORG Tue Sep 19 15:14:07 2006 Return-Path: X-Original-To: freebsd-firewire@FreeBSD.org Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2667E16A558 for ; Tue, 19 Sep 2006 15:14:07 +0000 (UTC) (envelope-from mldodson@houston.rr.com) Received: from ms-smtp-01.texas.rr.com (ms-smtp-01.texas.rr.com [24.93.47.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C4F743FB3 for ; Tue, 19 Sep 2006 15:05:19 +0000 (GMT) (envelope-from mldodson@houston.rr.com) Received: from localhost.houston.rr.com (cpe-24-167-77-130.houston.res.rr.com [24.167.77.130]) by ms-smtp-01.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8JF5HQc010721 for ; Tue, 19 Sep 2006 10:05:18 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.6/8.13.6/Submit) id k8JF5HMB053435 for freebsd-firewire@FreeBSD.org; Tue, 19 Sep 2006 10:05:17 -0500 (CDT) (envelope-from mldodson@houston.rr.com) X-Authentication-Warning: localhost.houston.rr.com: bdodson set sender to mldodson@houston.rr.com using -f From: "M. L. Dodson" To: freebsd-firewire@FreeBSD.org Date: Tue, 19 Sep 2006 10:05:16 -0500 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609191005.17015.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Subject: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 15:14:07 -0000 I posted this to questions@ last week but got no response, so thought I would try this list since the specific instance involved firewire. I suspect this is a behaviour that might be modulated by some devfs rules, but I can't figure them out, and there does not appear to be a list that focuses on devfs. In any case: I was transferring a bunch of data files from compute node disks to a server using dump-restore. This before I put the disks in storage for a few months. I put the disks with the data files into an external firewire device, plugged it in, and did the transfers. All the dump/restores worked (eventually), but I had to reboot the server between every disk's dump/restore combination (see below). This is on 6.1-RELEASE-p6. When I finished a dump/restore, I just pulled the cable (the firewire disk partitions were not mounted). When I plugged in the next drive, devfs created devices with names like /dev/da0s1aa, /dev/da0s1ab, /dev/da0s1ac, etc., in addition to the regular /dev/da0s1a, etc (which were left over from the first disk, they were not destroyed when I pulled the cable). When I tried to fsck the firewire disk partitions after this behaviour, /dev/da0s1a and /dev/da0s1g worked fine (as did the dump/restore from /dev/da0s1g). The other partitions, /dev/da0s1d, e, and f, failed, saying the superblock could not be found. Only a reboot gave a system with all /dev/da0s1* reflecting the actual firewire disk partitions after a hot plugin. All the data disks that were dumped were of the same kind and had identical partitioning schemes. My question: Should I be doing something to signal devfs I'm going to unplug a device so it won't get confused when I plug in another similar, but not the same, device? camcontrol commands like "camcontrol eject " and "camcontrol rescan all" seemed to not have the results I expected. What's going on here? Bud Dodson -- M. L. Dodson Email: mldodson-at-houston-dot-rr-dot-com Phone: eight_three_two-56_three-386_one From owner-freebsd-firewire@FreeBSD.ORG Tue Sep 19 16:04:52 2006 Return-Path: X-Original-To: freebsd-firewire@FreeBSD.org Delivered-To: freebsd-firewire@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 992E116A416 for ; Tue, 19 Sep 2006 16:04:52 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id A237843D46 for ; Tue, 19 Sep 2006 16:04:48 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (b1e258cip5bm11yf@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k8JG4mgC036216; Tue, 19 Sep 2006 09:04:48 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k8JG4mio036215; Tue, 19 Sep 2006 09:04:48 -0700 (PDT) (envelope-from jmg) Date: Tue, 19 Sep 2006 09:04:48 -0700 From: John-Mark Gurney To: "M. L. Dodson" Message-ID: <20060919160447.GC23915@funkthat.com> Mail-Followup-To: "M. L. Dodson" , freebsd-firewire@FreeBSD.org References: <200609191005.17015.mldodson@houston.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609191005.17015.mldodson@houston.rr.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-firewire@FreeBSD.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 16:04:52 -0000 M. L. Dodson wrote this message on Tue, Sep 19, 2006 at 10:05 -0500: > When I finished a dump/restore, I just pulled the cable (the > firewire disk partitions were not mounted). When I plugged in the The problem is that the old devices still are open for writing.. If you were to umount -f the old fs, most likely, the devices would wither away, and things would be back to normal... I hope you were fsync'ing the files before you unmounted the disk to ensure that the file was completely written to disk, otherwise you could end up w/ the an incomplete file... > My question: Should I be doing something to signal devfs I'm going > to unplug a device so it won't get confused when I plug in another > similar, but not the same, device? camcontrol commands like > "camcontrol eject " and "camcontrol rescan all" seemed to > not have the results I expected. What's going on here? umount the file system... I unplug firewire drives that don't have mounted filesystems, and haven't had an issue with it... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-firewire@FreeBSD.ORG Tue Sep 19 16:25:40 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9708A16A417 for ; Tue, 19 Sep 2006 16:25:40 +0000 (UTC) (envelope-from mldodson@houston.rr.com) Received: from ms-smtp-03.texas.rr.com (ms-smtp-03.texas.rr.com [24.93.47.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE1F843D77 for ; Tue, 19 Sep 2006 16:25:37 +0000 (GMT) (envelope-from mldodson@houston.rr.com) Received: from localhost.houston.rr.com (cpe-24-167-77-130.houston.res.rr.com [24.167.77.130]) by ms-smtp-03.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8JGPZF1007128; Tue, 19 Sep 2006 11:25:36 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.6/8.13.6/Submit) id k8JGPZuP071466; Tue, 19 Sep 2006 11:25:35 -0500 (CDT) (envelope-from mldodson@houston.rr.com) X-Authentication-Warning: localhost.houston.rr.com: bdodson set sender to mldodson@houston.rr.com using -f From: "M. L. Dodson" To: John-Mark Gurney Date: Tue, 19 Sep 2006 11:25:34 -0500 User-Agent: KMail/1.9.4 References: <200609191005.17015.mldodson@houston.rr.com> <20060919160447.GC23915@funkthat.com> In-Reply-To: <20060919160447.GC23915@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609191125.35128.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 16:25:40 -0000 On Tuesday 19 September 2006 11:04, John-Mark Gurney wrote: > M. L. Dodson wrote this message on Tue, Sep 19, 2006 at 10:05 -0500: > > When I finished a dump/restore, I just pulled the cable (the > > firewire disk partitions were not mounted). When I plugged in the > > The problem is that the old devices still are open for writing.. If > you were to umount -f the old fs, most likely, the devices would > wither away, and things would be back to normal... > Hmmm... I just looked at the umount man page. I guess the behaviour you describe can be implied by it, but it is certainly not obvious (at least to me). So, if I understand you, if instead of "umount /mnt", I do "umount -f /mnt", the behaviour will be as I expected: the device will be completely unmounted and the device will disappear when I pull the cable? > I hope you were fsync'ing the files before you unmounted the disk > to ensure that the file was completely written to disk, otherwise > you could end up w/ the an incomplete file... > Actually, my sequence was: fsck the /dev/da0s1* (excluding b and c), and that was where I noticed the problem (on the second firewire disk in the sequence of 7 disks dumped), then dump the g partition to a file on the server's main disk. Then I did a restore -if in the directory I wanted the stuff to go into. I did it this way so I could exclude some unimportant stuff that was in the /home directory on the firewire disk (corresponding to /dev/da0s1g). The only time I mounted the disk was to rsync between the firewire /home (/dev/da0s1g) and the restored data directory to check for errors. (This data cost weeks of computation for many of the files, so better to take a little time to wear belt AND suspenders). The firewire disk was only ever read from, not written to except for the fsck. Your answer implies to me that if I had never mounted the device it would have gone away when I pulled the cable. Right? > > My question: Should I be doing something to signal devfs I'm going > > to unplug a device so it won't get confused when I plug in another > > similar, but not the same, device? camcontrol commands like > > "camcontrol eject " and "camcontrol rescan all" seemed to > > not have the results I expected. What's going on here? > > umount the file system... I unplug firewire drives that don't have > mounted filesystems, and haven't had an issue with it... OK, that is certainly what I get from your first couple of paragraphs. Thanks for the explanation! Bud Dodson -- M. L. Dodson Email: mldodson-at-houston-dot-rr-dot-com Phone: eight_three_two-56_three-386_one From owner-freebsd-firewire@FreeBSD.ORG Tue Sep 19 17:19:53 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAE2016A403 for ; Tue, 19 Sep 2006 17:19:52 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B38043D45 for ; Tue, 19 Sep 2006 17:19:52 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (mldr2q0s2cejucfw@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k8JHJpU2037645; Tue, 19 Sep 2006 10:19:51 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k8JHJpGk037644; Tue, 19 Sep 2006 10:19:51 -0700 (PDT) (envelope-from jmg) Date: Tue, 19 Sep 2006 10:19:50 -0700 From: John-Mark Gurney To: "M. L. Dodson" Message-ID: <20060919171950.GD23915@funkthat.com> Mail-Followup-To: "M. L. Dodson" , freebsd-firewire@freebsd.org References: <200609191005.17015.mldodson@houston.rr.com> <20060919160447.GC23915@funkthat.com> <200609191125.35128.mldodson@houston.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609191125.35128.mldodson@houston.rr.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 17:19:53 -0000 M. L. Dodson wrote this message on Tue, Sep 19, 2006 at 11:25 -0500: > On Tuesday 19 September 2006 11:04, John-Mark Gurney wrote: > > M. L. Dodson wrote this message on Tue, Sep 19, 2006 at 10:05 -0500: > > > When I finished a dump/restore, I just pulled the cable (the > > > firewire disk partitions were not mounted). When I plugged in the > > > > The problem is that the old devices still are open for writing.. If > > you were to umount -f the old fs, most likely, the devices would > > wither away, and things would be back to normal... > > Hmmm... I just looked at the umount man page. I guess the > behaviour you describe can be implied by it, but it is certainly > not obvious (at least to me). So, if I understand you, if instead > of "umount /mnt", I do "umount -f /mnt", the behaviour will be as > I expected: the device will be completely unmounted and the device > will disappear when I pull the cable? The -f is only necessary if you've already removed the drive... You should be able to do a normal umount /mnt before you pull the drive and then everything will just work... > > I hope you were fsync'ing the files before you unmounted the disk > > to ensure that the file was completely written to disk, otherwise > > you could end up w/ the an incomplete file... > > Actually, my sequence was: fsck the /dev/da0s1* (excluding b and > c), and that was where I noticed the problem (on the second > firewire disk in the sequence of 7 disks dumped), then dump the g > partition to a file on the server's main disk. Then I did a > restore -if in the directory I wanted the stuff > to go into. I did it this way so I could exclude some unimportant > stuff that was in the /home directory on the firewire disk > (corresponding to /dev/da0s1g). The only time I mounted the disk > was to rsync between the firewire /home (/dev/da0s1g) and the > restored data directory to check for errors. (This data cost > weeks of computation for many of the files, so better to take a > little time to wear belt AND suspenders). The firewire disk was > only ever read from, not written to except for the fsck. Your > answer implies to me that if I had never mounted the device it > would have gone away when I pulled the cable. Right? Correct... > > > My question: Should I be doing something to signal devfs I'm going > > > to unplug a device so it won't get confused when I plug in another > > > similar, but not the same, device? camcontrol commands like > > > "camcontrol eject " and "camcontrol rescan all" seemed to > > > not have the results I expected. What's going on here? > > > > umount the file system... I unplug firewire drives that don't have > > mounted filesystems, and haven't had an issue with it... > > OK, that is certainly what I get from your first couple of > paragraphs. Thanks for the explanation! np... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-firewire@FreeBSD.ORG Tue Sep 19 17:51:39 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AF3A16A40F for ; Tue, 19 Sep 2006 17:51:39 +0000 (UTC) (envelope-from mldodson@houston.rr.com) Received: from ms-smtp-01.texas.rr.com (ms-smtp-01.texas.rr.com [24.93.47.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98F3643D73 for ; Tue, 19 Sep 2006 17:51:38 +0000 (GMT) (envelope-from mldodson@houston.rr.com) Received: from localhost.houston.rr.com (cpe-24-167-77-130.houston.res.rr.com [24.167.77.130]) by ms-smtp-01.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8JHpaHo023669; Tue, 19 Sep 2006 12:51:37 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.8/8.13.6/Submit) id k8JHpZDx001002; Tue, 19 Sep 2006 12:51:35 -0500 (CDT) (envelope-from mldodson@houston.rr.com) X-Authentication-Warning: localhost.houston.rr.com: bdodson set sender to mldodson@houston.rr.com using -f From: "M. L. Dodson" To: John-Mark Gurney Date: Tue, 19 Sep 2006 12:51:35 -0500 User-Agent: KMail/1.9.4 References: <200609191005.17015.mldodson@houston.rr.com> <200609191125.35128.mldodson@houston.rr.com> <20060919171950.GD23915@funkthat.com> In-Reply-To: <20060919171950.GD23915@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609191251.35787.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2006 17:51:39 -0000 On Tuesday 19 September 2006 12:19, John-Mark Gurney wrote: > M. L. Dodson wrote this message on Tue, Sep 19, 2006 at 11:25 -0500: > > On Tuesday 19 September 2006 11:04, John-Mark Gurney wrote: > > > M. L. Dodson wrote this message on Tue, Sep 19, 2006 at 10:05 -0500: > > > > When I finished a dump/restore, I just pulled the cable (the > > > > firewire disk partitions were not mounted). When I plugged in the > > > > > > The problem is that the old devices still are open for writing.. If > > > you were to umount -f the old fs, most likely, the devices would > > > wither away, and things would be back to normal... > > > > Hmmm... I just looked at the umount man page. I guess the > > behaviour you describe can be implied by it, but it is certainly > > not obvious (at least to me). So, if I understand you, if instead > > of "umount /mnt", I do "umount -f /mnt", the behaviour will be as > > I expected: the device will be completely unmounted and the device > > will disappear when I pull the cable? > > The -f is only necessary if you've already removed the drive... You > should be able to do a normal umount /mnt before you pull the drive > and then everything will just work... > Then something is still not right. I always did a umount before I pulled the cable. Never did I pull the cable on a mounted drive (if I had, I would have expected a kernel panic). So I'm still confused. It is true that the device (when mounted for the rsync tests) was mounted r/w, and that was a mistake on my part. But if I'm following this dialog correctly, I should not have had devices such as /dev/da0s1a, b, c, d, e, f, and g survive more than a short interval after pulling the cable. But they did, and when I plugged another disk in I got /dev/da0s1a, /dev/da0s1aa, /dev/da0s1ab, /dev/da0s1ac, /dev/da0s1ad, /dev/da0s1ae, /dev/da0s1af, /dev/da0s1ag, /dev/da0s1b, /dev/da0s1c, /dev/da0s1d, /dev/da0s1e, /dev/da0s1f, and /dev/da0s1g. I did not try to fsck /dev/da0s1a? (that would have been just too funky), but fsck /dev/da0s1a and fsck /dev/da0s1g worked; devices /dev/da0s1d, /dev/da0s1e, and /dev/da0s1f failed fsck with the error message that the superblock could not found. Does this tell you anything new? > > > I hope you were fsync'ing the files before you unmounted the disk > > > to ensure that the file was completely written to disk, otherwise > > > you could end up w/ the an incomplete file... > > > > Actually, my sequence was: fsck the /dev/da0s1* (excluding b and > > c), and that was where I noticed the problem (on the second > > firewire disk in the sequence of 7 disks dumped), then dump the g > > partition to a file on the server's main disk. Then I did a > > restore -if in the directory I wanted the stuff > > to go into. I did it this way so I could exclude some unimportant > > stuff that was in the /home directory on the firewire disk > > (corresponding to /dev/da0s1g). The only time I mounted the disk > > was to rsync between the firewire /home (/dev/da0s1g) and the > > restored data directory to check for errors. (This data cost > > weeks of computation for many of the files, so better to take a > > little time to wear belt AND suspenders). The firewire disk was > > only ever read from, not written to except for the fsck. Your > > answer implies to me that if I had never mounted the device it > > would have gone away when I pulled the cable. Right? > > Correct... > > > > > My question: Should I be doing something to signal devfs I'm going > > > > to unplug a device so it won't get confused when I plug in another > > > > similar, but not the same, device? camcontrol commands like > > > > "camcontrol eject " and "camcontrol rescan all" seemed to > > > > not have the results I expected. What's going on here? > > > > > > umount the file system... I unplug firewire drives that don't have > > > mounted filesystems, and haven't had an issue with it... > > > > OK, that is certainly what I get from your first couple of > > paragraphs. Thanks for the explanation! > > np... -- M. L. Dodson Email: mldodson-at-houston-dot-rr-dot-com Phone: eight_three_two-56_three-386_one From owner-freebsd-firewire@FreeBSD.ORG Wed Sep 20 06:20:48 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD7F516A415 for ; Wed, 20 Sep 2006 06:20:48 +0000 (UTC) (envelope-from aloptooke@classifiedtoday.com) Received: from classifiedtoday.com (cmo116.neoplus.adsl.tpnet.pl [83.31.142.116]) by mx1.FreeBSD.org (Postfix) with SMTP id 810C043D70 for ; Wed, 20 Sep 2006 06:20:42 +0000 (GMT) (envelope-from aloptooke@classifiedtoday.com) Received: from 83.31.142.116 by classifiedtoday.com Date: Wed, 20 Sep 2006 08:20:40 +0100 From: "levey cassie" X-Sender: aloptooke@classifiedtoday.com To: Message-Id: <1793088070.FSlYOQYR-54579-173030496@classifiedtoday.com> MIME-Version: 1.0 Content-Type: text/plain Subject: You reap what you sow. X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 06:20:48 -0000 HOT ALERT - THIS ONE IS STILL CLIMBING THE CHARTS ALERT -- BREAKING MARKET NEWS REPORT ---- WBRS.PK Company Name: WILD BRUSH ENERGY Lookup: WBRS.PK Current Price: .05 Expected: STEADILY CLIMB FOR THE TOP Breaking News: Wild Brush Acquires Additional Powder River Oil & Gas Lease Wild Brush Energy (PINKSHEETS: WBRS) announces the purchase of an additional Powder River Basin Federal Oil & Gas Lease in the State of Wyoming. The lease is located on the eastern side of the Basin in Weston County. This is the fifth lease the Company now controls in the region. Wild Brush maintains its expansion strategy through acquisition of low risk, high probability oil and gas properties in proven regions such as Powder River basin. Wild Brush will continue to concentrate on the Powder River Basin area, due to the number of lease acre ages it currently controls. The Powder River Basin claims a high probability rate of discoveries and proven production as demonstrated by such companies as Chevron and Western Gas. There are presently over 12,000 gas wells, in addition to nearly 400 new wells monthly, producing over 330 billion cubic feet annually, in an area with an estimated 32 trillion cubic feet of natural gas. About WBRS.PK Wild Brush Energy is a diversified energy company whose primary goal is to identify and develop Oil & Coalbed Methane sites within the State of Wyoming. In addition, Wild Brush Energy continues to evaluate clean air alternative energy producing technologies such as Wind Power. Wild Brush trades in the U.S. under the symbol "WBRS." WATCH THIS STOCK GO HIGHER AND HIGHER -------------------------------------------------------------------------------- The stock climbed to $2.20 See the results for your self ----------------------- The scum of the earth. We hung them out to dry. Your in hot water. There is always next year. Strong as an ox. Weed out. We hung them out to dry. To gild refined gold, to paint the lily. Put off the scent. Sweet as apple pie. Spring forward fall back. A rolling stone gathers no moss. Schools out for summer. Till the cows come home. Strong as an ox. Timing is everything. To gild refined gold, to paint the lily. A place in the sun. The sharper is the berry, the sweeter is the wine. A stick in the mud. This is for the birds. Which came first, the chicken or the egg. Water it down. Watch and wait. Still waters run deep. Weed it out. Plain as water. Rain, rain go away; come again some other day. The sharper is the berry, the sweeter is the wine. Sweating blood. That's water under the bridge. Sick as a dog. Season of mists and mellow fruitfulness. Stop and smell the roses. Sow dry and set wet. Raking in the dough. Walking on water. Rise and shine. Run to seed. Root it out. Speak softly and carry a big stick. From owner-freebsd-firewire@FreeBSD.ORG Wed Sep 20 19:14:57 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13D0316A407 for ; Wed, 20 Sep 2006 19:14:57 +0000 (UTC) (envelope-from mldodson@houston.rr.com) Received: from ms-smtp-02.texas.rr.com (ms-smtp-02.texas.rr.com [24.93.47.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id A632C43D5A for ; Wed, 20 Sep 2006 19:14:36 +0000 (GMT) (envelope-from mldodson@houston.rr.com) Received: from localhost.houston.rr.com (cpe-24-167-77-130.houston.res.rr.com [24.167.77.130]) by ms-smtp-02.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8KJENQP021447; Wed, 20 Sep 2006 14:14:23 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.8/8.13.6/Submit) id k8KJEMAe005243; Wed, 20 Sep 2006 14:14:22 -0500 (CDT) (envelope-from mldodson@houston.rr.com) X-Authentication-Warning: localhost.houston.rr.com: bdodson set sender to mldodson@houston.rr.com using -f From: "M. L. Dodson" To: John-Mark Gurney Date: Wed, 20 Sep 2006 14:14:22 -0500 User-Agent: KMail/1.9.4 References: <200609191005.17015.mldodson@houston.rr.com> <200609191125.35128.mldodson@houston.rr.com> <20060919171950.GD23915@funkthat.com> In-Reply-To: <20060919171950.GD23915@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609201414.22322.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 19:14:57 -0000 More experimental results on firewire disks and hot unplugging: Transcripts of two sessions can be retrieved from http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt To summarize, on two different machines (histidine and serine) using two different brands of firewire PCI cards, but both using Texas Instruments chips, plugging and unplugging an external firewire device (Ultra ATA Seagate Barracuda 7200.7, 120GB disks in a combo USB 2.0/Firewire device) in no case gave funky /dev/da0s1a? devices, if the devices were never mounted (see earlier postings in this thread). In addition plugging and unplugging never destroyed the /dev/da0s1a - /dev/da0s1g nodes created the first time the device was plugged in. The nodes always persisted for at least 10 minutes past the hot unplug time. This may be the expected behaviour, but I had thought that the nodes in /dev for unplugged devices were deleted after some timeout. I guess I was wrong. However, after a lot of plugging/unplugging actions (see the serine transcript), an attempt to mount one of the partitions caused the machine to become mostly unresponsive: It responded to the keyboard with the echo, but the contents of the input buffer did not seem to get further. Attempts to ssh into the machine were unsuccessful (unresponsive). Attempts to log on as root at the physical console did not succeed (it went into catatonia after typing the password and pressing return). So something is not right with devfs and at least these firewire cards and device, with multiple hot plug/unplug events. My hypothesis is that the /dev/da0s1a? devices only appear if you hot unplug one disk, then immediately plug in another disk (in the same combo ATA->firewire adapter?). Mounting a partition may also be necessary for their subsequent creation. Multiple plugging/unplugging events cause the lockups when a subsequent attempt to mount one of the partitions is tried. Any ideas to clue me in? Who should I talk to about firewire drivers and devfs on -STABLE/-RELEASE? Bud Dodson -- M. L. Dodson Email: mldodson-at-houston-dot-rr-dot-com Phone: eight_three_two-56_three-386_one From owner-freebsd-firewire@FreeBSD.ORG Wed Sep 20 19:42:49 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F37C316A407 for ; Wed, 20 Sep 2006 19:42:48 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28BB343D79 for ; Wed, 20 Sep 2006 19:42:37 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (g9kxl09yob37lqyk@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k8KJgbsO066282; Wed, 20 Sep 2006 12:42:37 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k8KJgbhH066281; Wed, 20 Sep 2006 12:42:37 -0700 (PDT) (envelope-from jmg) Date: Wed, 20 Sep 2006 12:42:37 -0700 From: John-Mark Gurney To: "M. L. Dodson" Message-ID: <20060920194236.GJ23915@funkthat.com> Mail-Followup-To: "M. L. Dodson" , freebsd-firewire@freebsd.org References: <200609191005.17015.mldodson@houston.rr.com> <200609191125.35128.mldodson@houston.rr.com> <20060919171950.GD23915@funkthat.com> <200609201414.22322.mldodson@houston.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609201414.22322.mldodson@houston.rr.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 19:42:49 -0000 M. L. Dodson wrote this message on Wed, Sep 20, 2006 at 14:14 -0500: > More experimental results on firewire disks and hot unplugging: > > Transcripts of two sessions can be retrieved from > http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and > http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt doh, I think I know what your problem is... you need to do three or so fwcontrol -r's before the device will disappear... This is necessary, since each plug causes a rescan, and you don't want devices disappearing when you add your cd drive... It looks like adding a timeout would be a good thing to the device orphan... If the device has been orphaned for more than a minute, drop it, or three or so resets... Instead of fwcontrol -r, you can plug/unplug another device, and a couple times will cause the device to fall off the bus.. Are you putting a different drive into the same enclosure? If you are, then the disk 'reappears', and apparently geom tastes w/ some of the old info.. if you do: true > /dev/da4 it will force a retaste and the bogus entries should go away... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-firewire@FreeBSD.ORG Wed Sep 20 20:04:46 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A382416A553 for ; Wed, 20 Sep 2006 20:04:45 +0000 (UTC) (envelope-from mldodson@houston.rr.com) Received: from ms-smtp-05.texas.rr.com (ms-smtp-05.texas.rr.com [24.93.47.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 153B243D6A for ; Wed, 20 Sep 2006 20:03:29 +0000 (GMT) (envelope-from mldodson@houston.rr.com) Received: from localhost.houston.rr.com (cpe-24-167-77-130.houston.res.rr.com [24.167.77.130]) by ms-smtp-05.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8KK3BBL012038; Wed, 20 Sep 2006 15:03:15 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.8/8.13.6/Submit) id k8KK3BcC005391; Wed, 20 Sep 2006 15:03:11 -0500 (CDT) (envelope-from mldodson@houston.rr.com) X-Authentication-Warning: localhost.houston.rr.com: bdodson set sender to mldodson@houston.rr.com using -f From: "M. L. Dodson" To: John-Mark Gurney Date: Wed, 20 Sep 2006 15:03:10 -0500 User-Agent: KMail/1.9.4 References: <200609191005.17015.mldodson@houston.rr.com> <200609201414.22322.mldodson@houston.rr.com> <20060920194236.GJ23915@funkthat.com> In-Reply-To: <20060920194236.GJ23915@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609201503.10994.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 20:04:46 -0000 On Wednesday 20 September 2006 14:42, John-Mark Gurney wrote: > M. L. Dodson wrote this message on Wed, Sep 20, 2006 at 14:14 -0500: > > More experimental results on firewire disks and hot unplugging: > > > > Transcripts of two sessions can be retrieved from > > http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and > > http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt > > doh, I think I know what your problem is... you need to do three > or so fwcontrol -r's before the device will disappear... This is > necessary, since each plug causes a rescan, and you don't want devices > disappearing when you add your cd drive... It looks like adding a > timeout would be a good thing to the device orphan... If the device > has been orphaned for more than a minute, drop it, or three or so > resets... > > Instead of fwcontrol -r, you can plug/unplug another device, and a > couple times will cause the device to fall off the bus.. OK, that all seems reasonable (at my level of understanding). I thought it was automatic, but it seems not so. Sort of like your last statement on device orphan (not a driver guru, sorry.) > > Are you putting a different drive into the same enclosure? If you > are, then the disk 'reappears', and apparently geom tastes w/ some > of the old info.. if you do: true > /dev/da4 it will force a retaste > and the bogus entries should go away... Yes this is exactly the situation. I physically replace the drive in the adapter (I don't even put it in the nice aluminum case). So the adapter is the same, but the drive is not. So, assuming the driver actually gets to the info for the actual drive, it will be different, but also alike. I suspected that was causing the driver confusion. I assume retaste is geom jargon for querying the device info? Thanks for all your help. I'll try all that. Bud Dodson -- M. L. Dodson Email: mldodson-at-houston-dot-rr-dot-com Phone: eight_three_two-56_three-386_one From owner-freebsd-firewire@FreeBSD.ORG Wed Sep 20 20:16:39 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 656AA16A416 for ; Wed, 20 Sep 2006 20:16:39 +0000 (UTC) (envelope-from mldodson@houston.rr.com) Received: from ms-smtp-01.texas.rr.com (ms-smtp-01.texas.rr.com [24.93.47.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0359E43D79 for ; Wed, 20 Sep 2006 20:16:28 +0000 (GMT) (envelope-from mldodson@houston.rr.com) Received: from localhost.houston.rr.com (cpe-24-167-77-130.houston.res.rr.com [24.167.77.130]) by ms-smtp-01.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8KKGQJL008453; Wed, 20 Sep 2006 15:16:27 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.8/8.13.6/Submit) id k8KKGQtw005556; Wed, 20 Sep 2006 15:16:26 -0500 (CDT) (envelope-from mldodson@houston.rr.com) X-Authentication-Warning: localhost.houston.rr.com: bdodson set sender to mldodson@houston.rr.com using -f From: "M. L. Dodson" To: John-Mark Gurney Date: Wed, 20 Sep 2006 15:16:26 -0500 User-Agent: KMail/1.9.4 References: <200609191005.17015.mldodson@houston.rr.com> <200609201414.22322.mldodson@houston.rr.com> <20060920194236.GJ23915@funkthat.com> In-Reply-To: <20060920194236.GJ23915@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609201516.26497.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 20:16:39 -0000 On Wednesday 20 September 2006 14:42, John-Mark Gurney wrote: > M. L. Dodson wrote this message on Wed, Sep 20, 2006 at 14:14 -0500: > > More experimental results on firewire disks and hot unplugging: > > > > Transcripts of two sessions can be retrieved from > > http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and > > http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt > > doh, I think I know what your problem is... you need to do three > or so fwcontrol -r's before the device will disappear... This is > necessary, since each plug causes a rescan, and you don't want devices > disappearing when you add your cd drive... It looks like adding a > timeout would be a good thing to the device orphan... If the device > has been orphaned for more than a minute, drop it, or three or so > resets... > That worked. Thanks again! Bud Dodson -- M. L. Dodson Email: mldodson-at-houston-dot-rr-dot-com Phone: eight_three_two-56_three-386_one From owner-freebsd-firewire@FreeBSD.ORG Thu Sep 21 02:57:01 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D80F816A403 for ; Thu, 21 Sep 2006 02:57:01 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0533443D46 for ; Thu, 21 Sep 2006 02:57:00 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.24] (andersonbox4.centtech.com [192.168.42.24]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k8L2uwFv087570; Wed, 20 Sep 2006 21:56:58 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4511FF85.1000102@centtech.com> Date: Wed, 20 Sep 2006 21:57:09 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: John-Mark Gurney References: <200609191005.17015.mldodson@houston.rr.com> <200609201414.22322.mldodson@houston.rr.com> <20060920194236.GJ23915@funkthat.com> <200609201516.26497.mldodson@houston.rr.com> In-Reply-To: <200609201516.26497.mldodson@houston.rr.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1914/Wed Sep 20 14:24:45 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-firewire@freebsd.org, mldodson@houston.rr.com Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 02:57:01 -0000 On 09/20/06 15:16, M. L. Dodson wrote: > On Wednesday 20 September 2006 14:42, John-Mark Gurney wrote: >> M. L. Dodson wrote this message on Wed, Sep 20, 2006 at 14:14 -0500: >>> More experimental results on firewire disks and hot unplugging: >>> >>> Transcripts of two sessions can be retrieved from >>> http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and >>> http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt >> doh, I think I know what your problem is... you need to do three >> or so fwcontrol -r's before the device will disappear... This is >> necessary, since each plug causes a rescan, and you don't want devices >> disappearing when you add your cd drive... It looks like adding a >> timeout would be a good thing to the device orphan... If the device >> has been orphaned for more than a minute, drop it, or three or so >> resets... >> > > That worked. Thanks again! > Bud Dodson > It's too bad firewire doesn't act more like USB storage in this case - you can yank and plug in the same or similar storage using the same adapter many many times without issue - I've done this many times. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-firewire@FreeBSD.ORG Thu Sep 21 04:03:59 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1414B16A403 for ; Thu, 21 Sep 2006 04:03:59 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75C2643D46 for ; Thu, 21 Sep 2006 04:03:58 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (z783mxgihtz0fu34@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k8L43uOx074916; Wed, 20 Sep 2006 21:03:56 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k8L43tuI074915; Wed, 20 Sep 2006 21:03:55 -0700 (PDT) (envelope-from jmg) Date: Wed, 20 Sep 2006 21:03:55 -0700 From: John-Mark Gurney To: Eric Anderson Message-ID: <20060921040355.GM23915@funkthat.com> Mail-Followup-To: Eric Anderson , mldodson@houston.rr.com, freebsd-firewire@freebsd.org References: <200609191005.17015.mldodson@houston.rr.com> <200609201414.22322.mldodson@houston.rr.com> <20060920194236.GJ23915@funkthat.com> <200609201516.26497.mldodson@houston.rr.com> <4511FF85.1000102@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4511FF85.1000102@centtech.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-firewire@freebsd.org, mldodson@houston.rr.com Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 04:03:59 -0000 Eric Anderson wrote this message on Wed, Sep 20, 2006 at 21:57 -0500: > On 09/20/06 15:16, M. L. Dodson wrote: > >On Wednesday 20 September 2006 14:42, John-Mark Gurney wrote: > >>M. L. Dodson wrote this message on Wed, Sep 20, 2006 at 14:14 -0500: > >>>More experimental results on firewire disks and hot unplugging: > >>> > >>>Transcripts of two sessions can be retrieved from > >>>http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and > >>>http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt > >>doh, I think I know what your problem is... you need to do three > >>or so fwcontrol -r's before the device will disappear... This is > >>necessary, since each plug causes a rescan, and you don't want devices > >>disappearing when you add your cd drive... It looks like adding a > >>timeout would be a good thing to the device orphan... If the device > >>has been orphaned for more than a minute, drop it, or three or so > >>resets... > > > >That worked. Thanks again! > > It's too bad firewire doesn't act more like USB storage in this case - > you can yank and plug in the same or similar storage using the same > adapter many many times without issue - I've done this many times. USB is a tree w/ hubs... If you have a chain of devices, and need to pull one in the middle, you'd loose the end devices if firewire behaved this way... /me notes that each have their advantages and disadvantages. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-firewire@FreeBSD.ORG Thu Sep 21 12:58:46 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 497F016A403 for ; Thu, 21 Sep 2006 12:58:46 +0000 (UTC) (envelope-from mldodson@houston.rr.com) Received: from ms-smtp-02.texas.rr.com (ms-smtp-02.texas.rr.com [24.93.47.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2CC443D53 for ; Thu, 21 Sep 2006 12:58:45 +0000 (GMT) (envelope-from mldodson@houston.rr.com) Received: from localhost.houston.rr.com (cpe-24-167-77-130.houston.res.rr.com [24.167.77.130]) by ms-smtp-02.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8LCwghd023934; Thu, 21 Sep 2006 07:58:43 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.8/8.13.6/Submit) id k8LCwaMZ008381; Thu, 21 Sep 2006 07:58:36 -0500 (CDT) (envelope-from mldodson@houston.rr.com) X-Authentication-Warning: localhost.houston.rr.com: bdodson set sender to mldodson@houston.rr.com using -f From: "M. L. Dodson" To: John-Mark Gurney Date: Thu, 21 Sep 2006 07:58:36 -0500 User-Agent: KMail/1.9.4 References: <200609191005.17015.mldodson@houston.rr.com> <4511FF85.1000102@centtech.com> <20060921040355.GM23915@funkthat.com> In-Reply-To: <20060921040355.GM23915@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609210758.36433.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 12:58:46 -0000 On Wednesday 20 September 2006 23:03, John-Mark Gurney wrote: > Eric Anderson wrote this message on Wed, Sep 20, 2006 at 21:57 -0500: > > On 09/20/06 15:16, M. L. Dodson wrote: > > >On Wednesday 20 September 2006 14:42, John-Mark Gurney wrote: > > >>M. L. Dodson wrote this message on Wed, Sep 20, 2006 at 14:14 -0500: > > >>>More experimental results on firewire disks and hot unplugging: > > >>> > > >>>Transcripts of two sessions can be retrieved from > > >>>http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and > > >>>http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt > > >> > > >>doh, I think I know what your problem is... you need to do three > > >>or so fwcontrol -r's before the device will disappear... This is > > >>necessary, since each plug causes a rescan, and you don't want > > >> devices disappearing when you add your cd drive... It looks like > > >> adding a timeout would be a good thing to the device orphan... If > > >> the device has been orphaned for more than a minute, drop it, or > > >> three or so resets... > > > > > >That worked. Thanks again! > > > > It's too bad firewire doesn't act more like USB storage in this case - > > you can yank and plug in the same or similar storage using the same > > adapter many many times without issue - I've done this many times. > And that is the behaviour I expected. I did not appreciate the differences between a chain and a tree. I'm a scientist, but not a computer scientist. I have been somewhat verbose in these emails to document my experiences for the archives. Thanks to you all. > USB is a tree w/ hubs... If you have a chain of devices, and need to > pull one in the middle, you'd loose the end devices if firewire > behaved this way... > > /me notes that each have their advantages and disadvantages. -- M. L. Dodson Email: mldodson-at-houston-dot-rr-dot-com Phone: eight_three_two-56_three-386_one From owner-freebsd-firewire@FreeBSD.ORG Thu Sep 21 15:58:34 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C98BC16A40F for ; Thu, 21 Sep 2006 15:58:34 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id B969343D5A for ; Thu, 21 Sep 2006 15:58:30 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (tdivkekbqqk4zxlh@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k8LFwSuE087444; Thu, 21 Sep 2006 08:58:28 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k8LFwN7c087443; Thu, 21 Sep 2006 08:58:23 -0700 (PDT) (envelope-from jmg) Date: Thu, 21 Sep 2006 08:58:23 -0700 From: John-Mark Gurney To: "M. L. Dodson" Message-ID: <20060921155823.GO23915@funkthat.com> Mail-Followup-To: "M. L. Dodson" , Eric Anderson , freebsd-firewire@freebsd.org References: <200609191005.17015.mldodson@houston.rr.com> <4511FF85.1000102@centtech.com> <20060921040355.GM23915@funkthat.com> <200609210758.36433.mldodson@houston.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609210758.36433.mldodson@houston.rr.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-firewire@freebsd.org Subject: Re: devfs and hot unplugging firewire device X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2006 15:58:34 -0000 M. L. Dodson wrote this message on Thu, Sep 21, 2006 at 07:58 -0500: > On Wednesday 20 September 2006 23:03, John-Mark Gurney wrote: > > Eric Anderson wrote this message on Wed, Sep 20, 2006 at 21:57 -0500: > > > On 09/20/06 15:16, M. L. Dodson wrote: > > > >On Wednesday 20 September 2006 14:42, John-Mark Gurney wrote: > > > >>M. L. Dodson wrote this message on Wed, Sep 20, 2006 at 14:14 -0500: > > > >>>More experimental results on firewire disks and hot unplugging: > > > >>> > > > >>>Transcripts of two sessions can be retrieved from > > > >>>http://siegfried.utmb.edu/bdodson/firewire.on.histidine.txt and > > > >>>http://siegfried.utmb.edu/bdodson/firewire.on.serine.txt > > > >> > > > >>doh, I think I know what your problem is... you need to do three > > > >>or so fwcontrol -r's before the device will disappear... This is > > > >>necessary, since each plug causes a rescan, and you don't want > > > >> devices disappearing when you add your cd drive... It looks like > > > >> adding a timeout would be a good thing to the device orphan... If > > > >> the device has been orphaned for more than a minute, drop it, or > > > >> three or so resets... > > > > > > > >That worked. Thanks again! > > > > > > It's too bad firewire doesn't act more like USB storage in this case - > > > you can yank and plug in the same or similar storage using the same > > > adapter many many times without issue - I've done this many times. > > > > And that is the behaviour I expected. I did not appreciate the > differences between a chain and a tree. I'm a scientist, but not > a computer scientist. I have been somewhat verbose in these > emails to document my experiences for the archives. Thanks to you > all. sbp(4) documents this behavior too, for the archives... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-firewire@FreeBSD.ORG Sat Sep 23 09:16:14 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADFA416A9FF for ; Sat, 23 Sep 2006 09:16:14 +0000 (UTC) (envelope-from qsecivzoi@est.it) Received: from est.it (cjm79.neoplus.adsl.tpnet.pl [83.31.62.79]) by mx1.FreeBSD.org (Postfix) with SMTP id 0A0C243D5A for ; Sat, 23 Sep 2006 09:16:12 +0000 (GMT) (envelope-from qsecivzoi@est.it) Date: Sat, 23 Sep 2006 11:16:12 +0100 From: "Nissie felicio" To: Cc: Message-Id: <5036661803.ujjoCGgVIhj-5007841-3035144@est.it> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Subject: No Guesswork Investing X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Sep 2006 09:16:14 -0000 Company- A L L I A N C E E N T E R P R I S E Symbol - A E T R (Pink Sheets) C u r r e n t P r i c e: $ 0.48 Estimated Target - $ 2.00 + S T R O N G B U Y AE TR is undergoing a massive promotion and NOW is the time to get in. Add this Gem to your Watch list. Watch it Start a run monday About A L L I A N C E E N T E R P R I S E (.TaeCorp.) TaeCorp's vision is to be the recognized leader in providing Aerial Detection Systems including global de-mining, clearing a path to a safer planet for all humankind. TaeCorp's mission is to reclaim lands around the globe embedded with landmines that victimize countries and their stakeholders. N E W S TaeCorp Appoints TAM Oilfield Services as Representative in Sudan The A L L I A N C E E N T E R P R I S E Corporation ("TaeCorp") (AETR - News) is pleased to announce that it has appointed TAM Oilfield Services ("TAM"), of Khartoum, the capital of Sudan, as its representative to introduce and establish business relationships with oil and related companies interested in TaeCorp's unique landmine detection, location, mapping and removal systems and services. TAM Oilfield Services, established in 2001 under the laws and regulations of the Sudan government, has forged strong relationships with the leading petroleum companies that operate in the Sudan. "TAM's experience in the petroleum field, both with government and operating companies, will allow TaeCorp to 0ffer its services more efficiently and effectively and we are very pleased to have TAM join our team," says Ralph Proceviat, CFO of TaeCorp. Read more A C T N O W on this great news and get in before the move starts. Season of mists and mellow fruitfulness. Under the weather. Weed it out. Stuck in a rut. Wait and see. Walking on cloud nine. Season of mists and mellow fruitfulness. Seed money. When it rains it pours. The squeaky wheel gets the grease. The scythe ran into a stone. Strong as an ox. Timing is everything. Stubborn as a mule. Too little too late. Waking up with the chickens. Shit end of the stick.