Re: TSM storage problem
2002-07-10 14:29:10
so far ----
Checked cacheing. It's off and has been off since it was installed.
There is only one storage pool which is 41% util.
This was working fine just a few days ago. There was no changes done by
me (The only admin).
The max. mount point = 1 for most clients. I didn't change or set this
so I'm kind of assuming this is the way it's been all along. Since it
worked great before I don't know why it would cause a problem now. What
is the recomended setting for this so as not to cause conflicts w/ anything?
The same error is coming up accross multiple policy domains (2 domains
setup to go to the same storage pool).
I finally decided that I just wanted to get it running as I am doing
some testing so I deleted the data for the largest node. This didn't
help any even though the storage pool is now down to 19% util.
I'm really confused and irritated by this....
sim
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: TSM storage problem, (continued)
- Re: TSM storage problem, David Longo
- Re: TSM storage problem, Gerald Wichmann
- Re: TSM storage problem, Bob Barden
- Re: TSM storage problem, Gerald Wichmann
- Re: TSM storage problem, Gerald Wichmann
- Re: TSM storage problem, Zlatko Krastev
- Re: TSM storage problem, Hooft, Jeroen
- Re: TSM storage problem, David Longo
- Re: TSM storage problem, Simeon Johnston
- Re: TSM storage problem, Gerald Wichmann
- Re: TSM storage problem, Damron, Nancy E.
- Re: TSM storage problem, Sung Y Lee
|
|
|