topic Re: Why Importing Metadata gives I/O subsystem error in Administration and Deployment

Why Importing Metadata gives I/O subsystem error

vaishnavpranam — Tue, 14 Nov 2017 04:08:10 GMT

Hello,

I am getting below error while i perform a metadata import -

INFO - ******** Importing Metadata ********

ERROR - Error importing metadata. Reason: The level container cannot be opened in the Foundation repository. The I/O subsystem error is ' ERROR: lock is not available for'.

INFO - The import process has finished with errors.

Also performed metadata repository analyse which was successful, but still log showed an I/O error.

Thanks in Advance !!

Re: Why Importing Metadata gives I/O subsystem error

nhvdwalt — Tue, 14 Nov 2017 05:00:50 GMT

Is there enough disk space or the Metadata repositories ?

Can you maybe restart the metadata server to ensure nothing else is doing something ?

Re: Why Importing Metadata gives I/O subsystem error

vaishnavpranam — Tue, 14 Nov 2017 05:35:41 GMT

Yes there is enough space on Metadata Repositories.
/apps/sas/SAS94/Config_MDS1/Lev1/SASMeta/MetadataServer/MetadataRepositories
[root@ME01 MetadataRepositories]#
[root@ME01 MetadataRepositories]# du -sh Foundation/
40M Foundation/

Re: Why Importing Metadata gives I/O subsystem error

nhvdwalt — Tue, 14 Nov 2017 06:37:11 GMT

That just shows that the respository is 40mb. How much disk space do you
have left on the disk where SAS is installed ?

Use the df -h command

Re: Why Importing Metadata gives I/O subsystem error

vaishnavpranam — Tue, 14 Nov 2017 06:52:30 GMT

Size Used Avail Use% Mounted on
56T 52T 2.7T 96% /apps

2.7 Terabytes is available

Re: Why Importing Metadata gives I/O subsystem error

nhvdwalt — Tue, 14 Nov 2017 07:17:11 GMT

Just out of curiosity, what do you mount it to, to have a 56TB mountpoint ?
That’s huge...

Anyhow...have you restarted the metadata server ?

Re: Why Importing Metadata gives I/O subsystem error

vaishnavpranam — Tue, 14 Nov 2017 07:35:03 GMT

This is a grid configuration so its a shared FileServer thats holding lot of stuff.

I restarted the metadata server and then tried to import the spk package but it failed again.

However the error this time was different.
The I/O error has disappeared and the new error is as below-

ERROR - Error importing metadata. Reason: The container table has no columns defined.

Re: Why Importing Metadata gives I/O subsystem error

vaishnavpranam — Tue, 14 Nov 2017 11:05:53 GMT

After running metadata files repair wizard,
Resolved Now