Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Get ipcshm buf_wait semop errno=43 on Restore
Answered: green (solid confidence) — Restore failed because the target file systems were too small; the asker confirmed it was a disk space problem and fixed it by enlarging the VM disks.
Sh To restored an ontape level-0 archive of a demo 14.10 database to a second server and it aborted with ipcshm semop errno=43 and write failed, file system is full. Paul Watson suggested checking the file system, inodes and lsof. Sh To later found it was a genuine disk space shortage despite matching VM sizes and solved it by enlarging the destination VM disks.
💣 This thread may describe something risky to do carelessly
Message 4 suggests oninit -i, which re-initialises the instance and makes existing databases inaccessible; acceptable only on a blank test target.
oninit -i
Advisory only — not a substitute for testing in a non-production environment first.
Sh To — source: IBM Community (ConnectedCommunity.org) Informix forum
Hello,
(Testing/learning purpose.)
Briefly,
I have one server IDS 14.10 with demodb database
And another server with identical disk definition and IDS 14.10 installed.
I made an
ontape -s -L 0on the first server
Got an archive of 39MB
I copied the archive file to the second server, I changed the name of the archive and tried to restore it on the second one with
ontape -pAnd I get in online log:
…
09:08:30 Dataskip is now OFF for all dbspaces
09:08:30 Restartable Restore has been ENABLED
09:08:30 Recovery Mode
09:08:32 Physical Restore of rootdbs, dblog started.
09:08:35 Aborting physical restore of ROOT DBSpace
09:08:35 Aborted by client.
09:08:35 IBM Informix Dynamic Server Stopped.And in the shell:
…
Continue restore? (y/n)y
Do you want to back up the logs? (y/n)n
10:23:05 ipcshm buf_wait semop errno=43
Physical restore failed - /rootdbs_fs/rootdbs: write failed, file system is full.
What am i doing wrong ?
Thanks
Samuel
------------------------------
Sh To
------------------------------
#Informix
↪ replying to Sh To
Paul Watson — source: IBM Community (ConnectedCommunity.org) Informix forum
Looks like the file system is full
Cheers
Paul
Paul Watson
Oninit LLC
+1-913-387-7529
www.oninit.com
Oninit® is a registered trademark of Oninit LLC
↪ replying to Paul Watson
Sh To — source: IBM Community (ConnectedCommunity.org) Informix forum
It look likes but it s not
It s a new install server with same dbspaces size as the primary server and some gigas free on the root filesystem
Really strange !
OK, maybe i ll reinstall the server...
Thanks
------------------------------
Sh To
------------------------------
↪ replying to Sh To
Paul Watson — source: IBM Community (ConnectedCommunity.org) Informix forum
On the target server does Oninit -i work - basically can you get a base engine to run?
Long shot but check the inodes - df -h will not show a FS out of inodes.
If you have lsof see if there are any orphaned processes holding on to space in the FS
Cheers
Paul
Paul Watson
Oninit LLC
+1-913-387-7529
www.oninit.com
Oninit® is a registered trademark of Oninit LLC
↪ replying to Paul Watson
Sh To — source: IBM Community (ConnectedCommunity.org) Informix forum
Hi
Yes, the oninit -i worked
ids-hdr:/IDS/informix$oninit -i
This action will initialize IBM Informix Dynamic Server;
any existing IBM Informix Dynamic Server databases will NOT be accessible -
Do you wish to continue (y/n)? y
ids-hdr:/IDS/informix$onstat -
IBM Informix Dynamic Server Version 14.10.FC4W1 -- On-Line -- Up 00:00:17 -- 165416 Kbytes
ids-hdr:/IDS/informix$And after the install i shut down the server and try to restore and now i have system full on /dblog_fs/dblog (instead of roodbs)
online.log
15:23:11 Dataskip is now OFF for all dbspaces
15:23:11 Restartable Restore has been ENABLED
15:23:11 Recovery Mode
15:23:13 Physical Restore of rootdbs, dblog started.
15:23:22 Checkpoint Completed: duration was 0 seconds.
15:23:22 Mon Jun 21 - loguniq 44, logpos 0xbbf018, timestamp: 0x4109d0 Interval: 1234
15:23:22 Maximum server connections 0
15:23:22 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 0
15:23:29 Aborting physical restore of ROOT DBSpace
15:23:29 /dblog_fs/dblog: write failed, file system is full.
15:23:29 IBM Informix Dynamic Server Stopped.
Shell
Do you want to back up the logs? (y/n)n
15:23:29 ipcshm buf_wait semop errno=43
Physical restore failed - buc_fe.c : Archive API processing failed at line 684 for msgtype
Program over.
15:23:29 ipcshm alert_server semop failed errno=22
15:23:29 ipcshm buf_wait semop errno=22
ids-hdr:/IDS/informix$
Interesting
------------------------------
Sh To
------------------------------
↪ replying to Sh To
Hrvoje Zokovic — source: IBM Community (ConnectedCommunity.org) Informix forum
Could you provide more info - e.g.
OS on both servers; df on both servers; ipcs on both servers; ls -l
/dblog_fs on both servers
Hrvoje
------------------------------
Hrvoje Zokovic
------------------------------
↪ replying to Hrvoje Zokovic
Sh To — source: IBM Community (ConnectedCommunity.org) Informix forum
Hello
This problem is solved.
I was really a problem of disk space, even if the two virtual machines (source and destination) were configure the same way.
One machine was Centos 7 and the second one Rocky Linux 8
I apparently did something wrong and i don't know what.
It s not so important because it was only for testing.
I increased the size of the destination VM (virtualbox) disks and it worked.
Thanks a lot
Samuel
------------------------------
Sh To
------------------------------
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.