Date: Tue, 19 Sep 2006 09:04:48 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: "M. L. Dodson" <mldodson@houston.rr.com> Cc: freebsd-firewire@FreeBSD.org Subject: Re: devfs and hot unplugging firewire device Message-ID: <20060919160447.GC23915@funkthat.com> In-Reply-To: <200609191005.17015.mldodson@houston.rr.com> References: <200609191005.17015.mldodson@houston.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <options>" 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."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060919160447.GC23915>