Date: Thu, 1 May 2003 10:21:04 -0700 (PDT) From: Nate Lawson <nate@root.org> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: freebsd-scsi@freebsd.org Subject: Re: Invalidating/reattaching a volume (was: relocation info) Message-ID: <Pine.BSF.4.21.0305011016050.85777-100000@root.org> In-Reply-To: <200305011359.h41DxPJJ023503@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 1 May 2003, Joerg Wunsch wrote: > "Kenneth D. Merry" <ken@kdm.org> wrote: > > You can try 'camcontrol reassign'. joerg sent me patches last Fall > > to implement it, and I've been planning on turning it into a scan > > and reassign tool. > > Mea culpa, i always intented to commit them, but apparently completely > forgot about the item. I'll make another stab on committing it (but > first have to see whether all's still OK with it in -current). I'd also like to see your camcontrol detach patches and a path for vinum to lose and then reattach a volume. Whether the latter should happen at the CAM layer or the vinum layer is up for discussion. I personally believe you should be able to tell vinum to close its reference to the drive that went away and then re-open it when the drive reappears. This could even be done automatically through GEOM. (See Gordon Tetlow's work on adding volume labels to GEOM). Comments? -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0305011016050.85777-100000>