Solved

mksysb error - AIX

Posted on 2010-11-22
17
3,809 Views
Last Modified: 2013-11-17
I am trying to take a mksysb image on a tape but this is the error I get

cp: /bosinst.data: The file access permissions do not allow the specified action.

Creating information file (/image.data) for rootvg.The file access permissions do not allow the specified action.
/usr/bin/mkszfile[939]: /image.data: 0403-005 Cannot create the specified file.

0512-008 mksysb: The mkszfile command failed.  Backup canceled.

Open in new window


I have checked the permissions on /bosinst.data and it looks fine.
-rw-r-----    1 root     system         5747 Jan 11 2006  /var/adm/ras/bosinst.data
-rw-r-----    1 root     system         5900 Nov 15 11:13 /bosinst.data

So is there any mksysb setting I have to change to make this work..??

-Steve


0
Comment
Question by:mnis2008
17 Comments
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 34191299
Hi,

did you run the mksysb command as root?

wmp
0
 

Author Comment

by:mnis2008
ID: 34191332
Yes I have run mksysb as root
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 34191403
Is there enough space in /tmp?

If in doubt use the "-X" flag with mksysb. This will increase the space in /tmp as needed.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:mnis2008
ID: 34191469
I have enough space in tmp
/dev/hd3           0.50      0.37   26%      327     1% /tmp

I tried the command again but its giving me the same error
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 34191587
Are you able to create files under "/" ?

Issue e.g. "touch /xyz.test"

What happens?
0
 

Author Comment

by:mnis2008
ID: 34191639
Its not allowing me to create anything under /

touch: 0652-046 Cannot create /xyz.test

0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 34191715
Now, there lies your problem, and it has nothing to do with mksysb!

Sorry, I must ask again: Are you actually root?

If so, you probably have a severe problem! Check "errpt" for filesystem errors!

If there are any entries indicating errors on "/" or "/dev/hd4" I fear you will have to boot from the installation CD/DVD into maintenance mode, import rootvg and start a shell before mounting filesystems, to then run fsck (at least) against /dev/hd4!





0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 34191736
If you're lucky "/" is just full and rootvg has no more space for filesystem expansion. Please check!
0
 

Author Comment

by:mnis2008
ID: 34191906
I have rebooted the server, The server came back fine but I have the same issue. As reboot will automatically run a fsck on the volumes.
0
 
LVL 68

Accepted Solution

by:
woolmilkporc earned 500 total points
ID: 34192021
>> reboot will automatically run a fsck on the volumes. <<

Actually? Will it?

Please note that during reboot only a minimal (called "fast") fsck is performed!

What's in errpt? How full is "/"?

0
 

Author Comment

by:mnis2008
ID: 34192060
Actually / is not that full too its

/dev/hd4           0.25      0.02   92%     3722    42% /

0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 34192141
It's just strange!

What do you see with "mount" ?
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 34192162
Which units do you use with "df"? And What's In Errpt?
0
 
LVL 19

Expert Comment

by:jools
ID: 34196222
root doesnt look all that big to me, as wmp says, what units did you use to display when you ran the df?



0
 
LVL 7

Expert Comment

by:sppalser
ID: 34200172
You also need to make sure that /var filesystem is not getting too tight on space.  Do you get any errors when trying to do a pg or more on text files?  Had a similar condition to what you describe when the / (root), /tmp, and /var filesystems had some corruption.  As above would suggest boot from a previous mksysb tape and go into maintenance mode and access the rootvg before starting a shell and run some fsck's on all the rootvg filesystems.  Be prepared to fix some stuff manully.  The unit I had wound up with missing device file nodes and found incorrect permissions on device nodes due to the filesystem corruption.  

Good Luck
0
 
LVL 62

Expert Comment

by:gheist
ID: 34205239
ls -ld / ? i.e what are permissions on /
0
 

Expert Comment

by:raajuece
ID: 34238774
Hi,

Remove the bosinst.data file and excute the mksysb command..

Cheers-
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In tuning file systems on the Solaris Operating System, changing some parameters of a file system usually destroys the data on it. For instance, changing the cache segment block size in the volume of a T3 requires that you delete the existing volu…
Installing FreeBSD… FreeBSD is a darling of an operating system. The stability and usability make it a clear choice for servers and desktops (for the cunning). Savvy?  The Ports collection makes available every popular FOSS application and packag…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question