Well I did some
/opt/d-cache/srm/bin/srm-advisory-delete \
-webservice_protocol=httpg -x509_user_proxy=/tmp/x509up_u27529 \
srm://dev01.gridpp.rl.ac.uk:8443/pnfs/gridpp.rl.ac.uk/data/dteam/filler_test20050811162410726768000
type commands on my then full box and space was returned to the pool imediately. Whats more when I did fill this D-Cache a second time I did not notice a hanging process on the transfer of data to D-Cache, so I think this version is fine. THe rpms I used are from the currently latest release of D-Cache
d-cache-client-1.0-100.i386.rpm d-cache-opt-1.5.3-84.i386.rpm
d-cache-client-1.0-100-RH73.i386.rpm pnfs-3.1.10-15.i386.rpm
d-cache-core-1.5.2-83.i386.rpm Release.notes
dCache-installation-instructions.txt
Regards
Owen S
On Thu, 11 Aug 2005 17:48:45 +0100
Owen Synge <[log in to unmask]> wrote:
> [synge@dev01 src]$ sh dcache_filler.sh
> error: the server sent an error response: 425 425 Cannot open port:
> java.lang.Exception: Pool manager error: Best pool <dev01_1> too high :
> 2.00000000002E8
>
> failed to copy file://///opt/bigzero to
> gsiftp://dev01.gridpp.rl.ac.uk:2811//pnfs/gridpp.rl.ac.uk/data/dteam/fi
> ller_test20050811173813669578000
> /opt/d-cache/srm/sbin/url-copy.sh return code = 1
> java.lang.IllegalStateException: Shutdown in progress
> at java.lang.Shutdown.add(Shutdown.java:79)
> at java.lang.Runtime.addShutdownHook(Runtime.java:190)
> at gov.fnal.srm.util.Copier.run(Copier.java:236)
> at java.lang.Thread.run(Thread.java:534)
>
>
> Is this the error you have all found when you copy a file to D-cache,
> also did you find that the last copy using
>
> /opt/d-cache/srm/bin/srmcp \
> -webservice_protocol=httpg \
> -x509_user_proxy=/tmp/x509up_u27529 \
> file:////${SOURCE} \
> srm://$SRM_HOST:8443/pnfs/$SRM_DOMAIN/data/dteam/${FILE}
>
>
> hangs forever? If so I shall replicate this once more to be certain and
> submit a bug before i go on to the next issue.
>
> This is the last revision of D-cache that's publicly released, I shall
> now try deleting files to see if this replicates your issues of over
> filling a D-cache, and hopefully replicate the issue I may have found
> and stated above.
>
> Regards
>
> Owen
|