From: CRDGW2::CRDGW2::MRGATE::"SMTP::CUNYVM.CUNY.EDU::ST801079%BROWNVM.BITNET" 5-OCT-1989 23:41 To: MRGATE::"ARISIA::EVERHART" Subj: Re: Vddriver and disk defragmenters Message-Id: <8910060107.AA22620@crdgw1.ge.com> Received: from MITVMA.MIT.EDU by mitvma.mit.edu (IBM VM SMTP R1.2.1MX) with BSMTP id 4126; Thu, 05 Oct 89 21:06:30 EDT Received: from BROWNVM.BITNET by MITVMA.MIT.EDU (Mailer R2.03B) with BSMTP id 3026; Thu, 05 Oct 89 21:06:29 EDT Received: by BROWNVM (Mailer R2.03B) id 0669; Thu, 05 Oct 89 21:06:06 EDT Date: Thu, 05 Oct 89 20:54:28 EDT From: "D. Kozlowski" Subject: Re: Vddriver and disk defragmenters To: Glenn Everhart > Wonder if any of the defragmenters can be told of >classes of files that should (must) be excluded from their >machinations? Since there are NO locks on the VD: container Just in case you really meant that question... RAXCO's Rabbit disk defragmenter does allow you to exclude files from being moved (even using wildcards). It also will not move any open files either, which is something I would hope other programs [don't] do as well. Are the container files closed between accesses and, if they are, would moving one do any harm? In any case, I usually ran disk reorganizers during periods of low usage, just to be safe. - d.k. ST801079@BROWNVM.BROWN.EDU or ST801079@BROWNVM.BITNET or ST*)!)&(@???.???