AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
That's always good news So check your / for any 'big' files that are unneeded and delete them to free up space. After that you should check if you can boot normally without errors and login correctly. If any errors are shown, please post them and we'll take it from there.
All right I have the files displaying at the / level. Took me a moment there.
I do see about three files that seem a bit large based on what they are but I'm not sure if they are the guilty parties or not.
I have a
inst.log at 19343
inst_brisque_sys.log at 61178
smit.log at 80738
Those last two in particular seem uncommonly portly for log files.
OOPS! missed your post above there. Thanks for the AIX sheet.
Hi,
Those are log files so you should be safe setting them to zero, don't delete them though. Normally if everything is set up correctly they would be recreated but since you didn't install nor configure the system it's better to just delete the contents like this:
Ok I will give that a go here in a few minutes. The echo command will reset them to zero correct?
I don't know if I will be back this morning to update the thread. I've been doing a fair bit of multitasking while troubleshooting this problem (hence the occasional lag in posting a response) and I've just had another job come up that will probably keep me occupied the rest of my shift. I'll update this thread tomorrow and hopefully I'll see you then with good news!!
Ok I will give that a go here in a few minutes. The echo command will reset them to zero correct?
I don't know if I will be back this morning to update the thread. I've been doing a fair bit of multitasking while troubleshooting this problem (hence the occasional lag in posting a response) and I've just had another job come up that will probably keep me occupied the rest of my shift. I'll update this thread tomorrow and hopefully I'll see you then with good news!!
Thanks again for your assistance.
Hello,
The echo command will delete the contents of the file(s) hence reducing the size. Good luck with your multitasking I'm changing jobs this week, doing two jobs so I know what you're going through.
You're welcome, that's what LinuxQuestions is all about, helping out each other.
The easy way out is to allocate more space to your / partition if you have the space. You can check for available space in the volume group (vg) with a few commands.
lsfs /dev/hd4
Code:
$ lsfs /dev/hd4
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs2 524288 -- yes no
List details of the logical volume (lv)
lslv hd4
Code:
$ lslv hd4
LOGICAL VOLUME: hd4 VOLUME GROUP: rootvg
LV IDENTIFIER: 00c29b8000004c00000001153d3d6581.4 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs2 WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 256 megabyte(s)
COPIES: 2 SCHED POLICY: parallel
LPs: 1 PPs: 2
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: center UPPER BOUND: 32
MOUNT POINT: / LABEL: /
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
In my case the volume group is called rootvg, you will have to get the name of your vg from your output.
lsvg rootvg
Code:
$ lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00c29b8000004c00000001153d3d6581
VG STATE: active PP SIZE: 256 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1092 (279552 megabytes)
MAX LVs: 256 FREE PPs: 490 (125440 megabytes)
LVs: 15 USED PPs: 602 (154112 megabytes)
OPEN LVs: 14 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
In my case, I have 490 free PPs which is about 125 gigs, you should see similar output and if you have free space, it can be allocated to the lv.
Eric just wanted you to know that everything is running fine this side of the pond. Thanks again!
crabboy thanks for the information in your post as well. I will definitely file that away and may implement those changes during the next maintenance interval.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
So check your / for any 'big' files that are unneeded and delete them to free up space. After that you should check if you can boot normally without errors and login correctly. If any errors are shown, please post them and we'll take it from there.
