From owner-freebsd-questions@FreeBSD.ORG Fri Sep 15 22:26:39 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2571716A403 for ; Fri, 15 Sep 2006 22:26:39 +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 C1A5B43D45 for ; Fri, 15 Sep 2006 22:26: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-02.texas.rr.com (8.13.6/8.13.6) with ESMTP id k8FMQbPv018568 for ; Fri, 15 Sep 2006 17:26:37 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by localhost.houston.rr.com (8.13.6/8.13.6/Submit) id k8FMQbJQ020483 for freebsd-questions@freebsd.org; Fri, 15 Sep 2006 17:26:37 -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-questions@freebsd.org Date: Fri, 15 Sep 2006 17:26:36 -0500 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609151726.36974.mldodson@houston.rr.com> X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: devfs and hot unplugging X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mldodson@houston.rr.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 22:26:39 -0000 I was transferring a bunch of data files from compute nodes to a server using dump-restore. I put the disks with the data files into an external firewire device, plugged it in, and did the transfers. This is on 6.1-RELEASE-p6. When I finished the transfers, 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, /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. All the data disks 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? 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