Re: <No Subject Supplied>

In article <5mh5fi$mkg@cssun.mathcs.emory.edu>, Andrew Cilia <acilia@mail.ptl.com.mt> writes >At 15:56 27/05/97 -0500, you wrote: > >To answer your first question, there should be no problem >if you add extra space to a volume on which an Informix >chunk resides. For the second question, you can create a >chunk in the extra space with an offset yet I doubt if this >is the best solution. > Agreed - I normally keep offsets low, if a disk fails and the replacement is smaller then the offset+size I used then you are stuck and cannot restore. I ALWAYS use low offsets and links to devices... > >Andrew Cilia - Philip Toledo Limited - Malta > >}Last week while I was away a dbspace filled. The unix system >}administrator tried to solve the problem by expanding the logical volume >}size. When that didn't work he waited for me to return. Upon my return >}we added an additional chunk to the dbspace and we are back in business. >} >}My questions are: will the extra space in the logical volume cause a >}problem and what is the best way to recover this space that informix >}doesn't know exists? >} Shrink the logical volume and create a new one in the freed space. Then add that new logical volume as another (empty) dbspace. When you need to use the space then a) note the filename,offset and size of the empty chunk. b) drop the empty dbspace/chunk c) use values from a) to create a new chunk in whatever dbspace has filled up. I prefer to claim any free space for myself but I'm cruel like that!! >}TIA >} >} >}Mark Stannard >}Ameritech >} > -- David Williams