Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LTO3\s+tape\s+capacity\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*LTO3\s+tape\s+capacity\s*$/: 5 ]

Total 5 documents matching your query.

1. LTO3 tape capacity (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Sun, 25 Sep 2005 09:45:51 -0500; TSM 5.3.1 on win2K server. We have a new LTO3 library, Overland Neo 4100 with 2 HP LTO3 drives. TSM is handling the tape drivers, version is 5.3.1.something. I've got an odd capacity issue with LTO3; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-09/msg00593.html (14,008 bytes)
2. Re: LTO3 tape capacity (score: 1): Author: Dmitri Pasyutin <pasyutin AT FREE DOT FR>; Date: Sun, 25 Sep 2005 19:04:18 +0200; You didn't post the output of 'q devc LTOCLASS2 f=d' - the value of FORMAT should be 'ULTRIUM3C' if you want to use compression. The "estimated capacity" gives an idea about the tape's capacity, but; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-09/msg00594.html (11,477 bytes)
3. Re: LTO3 tape capacity (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Sun, 25 Sep 2005 12:49:45 -0500; On Sunday 25 September 2005 16:45, Alexander Lazarevich wrote: tsm: ITG-TSM>q vol stgpool=lto3pool Volume Name Storage Device Estimated Pool Name Class Name Capacity Pct -- -- -- -- -- ITG001L3 LTO3; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-09/msg00595.html (14,147 bytes)
4. Re: LTO3 tape capacity (score: 1): Author: Andrew Raibeck <storman AT US.IBM DOT COM>; Date: Sun, 25 Sep 2005 20:10:39 +0100; Do you have client compression turned on? That would explain what you are seeing. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-09/msg00596.html (10,926 bytes)
5. Re: LTO3 tape capacity (score: 1): Author: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>; Date: Sun, 25 Sep 2005 15:44:30 -0500; Ah, yes, that's it. I knew that too, just forgot. We turn on client compress on some linux servers because we have a lot of sparse files and CPU to spare, whereas our network is saturated. Thanks for; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2005-09/msg00597.html (11,460 bytes)

Current List: 1 - 5
Page: [1]