Cannot drop two chunks that got added from a storage pool

I have two dbspaces that at one time have had automatic storage added to them and I need that space to go away as it is empty and is impeding moving out of my raw spaces with mirroring.....Informix won't mirror these spaces or drop them. onspaces -d space -p /opt/informix/disk_links/t_l29_pool1 -o 0 -yChunk not dropped. ISAM error: No such chunkThe other one is a different offset in the same file. I cannot drop it from HQ or AGS either....those give an ISAM 22 error. oncheck -pe spaceChunk Pathname Pagesize(k) Size(p) Used(p) Free(p) 20 /opt/informix/disk_links/t_l20_space 2 1024000 868803 155197 Description Offset(p) Size(p) Partnum Ext Num ------------------------------------------------------------- -------- -------- ---------- -------- RESERVED PAGES 0 2 CHUNK FREELIST PAGE 2 1 achdbs1:'informix'.TBLSpace 3 50 0x01400001 1 tba:'informix'.table1 53 512 0x01400002 1 tba:'informix'.table2 565 372656 0x01400003 1 .... .... Chunk Pathname Pagesize(k) Size(p) Used(p) Free(p) 36 /opt/informix/disk_links/t_l29_pool1 2 102400 3 102397 Description Offset(p) Size(p) Partnum Ext Num ------------------------------------------------------------- -------- -------- ---------- -------- RESERVED PAGES 0 2 CHUNK FREELIST PAGE 2 1 FREE 3 102397 Anyone ever encountered something similar? I do see "CHUNK FREELIST PAGE" in there rather than just "FREE", but I don't know if that makes a difference. I need these two spaces to go away. This is 14.10.FC7 Update --- I got one of them to drop with: execute function admin( 'drop chunk to storagepool', 'space', '/opt/informix/disk_links/t_l29_pool1', '716800' )Which AGS magically output when I told it to drop it and return it to the storage pool. The other space won't drop. AGS gives errors with both drop options....ISAM 22 with drop, ISAM 191 with drop and return to storage pool ------------------------------ Jared Heath ------------------------------

Can you show affected dbspaces and chunks from onstat -d? Suspecting incorrect offset (-o <#kB>) specified, hence "No such chunk". ------------------------------ Andreas Legner ------------------------------

Informix HQ doesn't need me to give it the offset to drop a chunk. Here is the log from it: it doesn't matter what offset I give this when attempting command line drops. I've tried every offset onstat -d has in relation to the storage pool, including zero. Nothing gets past error 22 or error 191 (if I choose drop without storage pool return) Digging further, I loaded this into another test server, and tried to drop the entire dbspace. That works and I guess is my workaround for this since I need to do this repeatedly across a lot of servers, but I'd rather not have the extra hour of unloading/loading (times 20). ------------------------------ Jared Heath ------------------------------