Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*on\s+which\s+vol\s+clients\s+data\s+is\s+stored\s+\?\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*on\s+which\s+vol\s+clients\s+data\s+is\s+stored\s+\?\?\s*$/: 3 ]

Total 3 documents matching your query.

1. on which vol clients data is stored ?? (score: 1): Author: Matti Harvala <Matti.Harvala AT NMP.NOKIA DOT COM>; Date: Fri, 26 Sep 1997 15:12:41 +0300; Hello ! Does anyone know if there is a server command(s) that could tell you where (vol name) the clients data is stored ?? Matti Harvala System Manager (Salo IT/Computing Services) Nokia Mobile Phon; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-09/msg00727.html (10,871 bytes)
2. Re: on which vol clients data is stored ?? (score: 1): Author: Christo Heuer <christoh AT ABSA.CO DOT ZA>; Date: Fri, 26 Sep 1997 15:23:02 +0200; Hi Matti, The 'UNDOCUMENTED' command: show volumeusage xxxxxx (where xxxxxx is your node name) will do the trick. Just be carefull - this has brought some peoples servers to a grinding halt. Never do; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-09/msg00730.html (11,285 bytes)
3. Re: on which vol clients data is stored ?? (score: 1): Author: Lylace Blake <lylace AT CSE.UCSC DOT EDU>; Date: Fri, 26 Sep 1997 09:56:24 -0700; FYI -- Running this command from the server console for a Solaris server caused segmentation violation and crash of the server. Caveat -- I'm running the try-n-buy installation, so am not well versed; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-09/msg00747.html (11,886 bytes)

Current List: 1 - 3
Page: [1]