Sponsored Content
Full Discussion: Unable to extend file system
Operating Systems AIX Unable to extend file system Post 303001500 by dn888 on Saturday 5th of August 2017 05:17:43 AM
Old 08-05-2017
Code:
vios:/home/padmin$ help

If available, you can refer to the Base Document Library
for general assistance.

Some basic Commands are:

    man -k keyword      - lists commands relevant to a keyword
    man command         - prints out the manual pages for a command
    cat                 - concatenates files (and just prints them out)
    vi                  - text editor
    ls                  - lists contents of directory
    mail                - sends and receives mail
    passwd              - changes login password
    sccshelp            - views information on the Source Code Control System
    smit                - system management interface tool
    tset                - sets terminal modes
    who                 - who is on the system
    write               - writes to another user

To find programs about mail, use the command:           man -k mail
and print out the man command documentation via:        man mail
You can log out of the system by typing:                exit

Code:
vios:/home/padmin$ lsvg -p rootvg
0516-304 : Unable to find device id 0002ef4df616f969 in the Device
        Configuration Database.
rootvg:
PV ID             PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
0002ef4df616f969  removed           546         538         110..101..109..109..109
hdisk0            active            546         454         109..89..38..109..109
hdisk3            active            546         469         109..104..38..109..109
vios:/home/padmin$

---------- Post updated at 07:17 PM ---------- Previous update was at 07:13 PM ----------

I have mentioned AIX 5.3 because its the information I got from this host using oslevel command.

I see lsvg -p rootvg command also list the device 0002ef4df616f969 as removed.

To become root , I used the command oem_setup_env

Code:
vios:/home/padmin$ whoami
root
vios:/home/padmin$


Last edited by Scott; 08-05-2017 at 11:58 AM.. Reason: Use code tags, please
 

10 More Discussions You Might Find Interesting

1. AIX

Can not extend a JFS file system

Hi, I am getting an error message when i try to increase the size of a filesystems under AIX 4.3.3: chfs: 0506-932 Can not extend a JFS file system with nbpi = 4096 and frag = 4096 past 134217728 (512 byte blocks). -> Characteristics Journaled File System ... (4 Replies)
Discussion started by: Can
4 Replies

2. UNIX for Advanced & Expert Users

Unable to clean up file system

Hi, Has anyone ever encountered the following scenario: I am working on a SUN server with solaris 10 installed and veritas managing the filesystem. One of the file systems has become full: df -kh /ossrc/dbdumps Filesystem size used avail capacity Mounted on... (6 Replies)
Discussion started by: eeidel
6 Replies

3. HP-UX

Unable To Extend the Size of a Logical Volume File System

Background: # uname -a HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license deedee.rsn.hp.com:/ # bdf /opt Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol6 6553600 6394216 158144 98% /opt /opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies

4. Solaris

Solaris file system unable to use available space

Hi, The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB. The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space. ofcourse the software... (31 Replies)
Discussion started by: iris1
31 Replies

5. Emergency UNIX and Linux Support

Not able to extend ZFS file system

Hi All, I have Solaris-10 configured with two non-global zones. All file-systems are mounted on global zone and data file-systems are mounted on non-global zone as lofs. I have added 4 luns of 100 GB each and still not able to extend a file-system. This is production server, so I can not... (5 Replies)
Discussion started by: solaris_1977
5 Replies

6. Solaris

How to extend an existing file system using SVM in solaris 10

Hi All I want to extend this file system to 120Gb: df -h /xyz Filesystem size used avail capacity Mounted on /dev/md/dsk/d80 98G 35G 62G 37% /xyzand the NetApp admin is going to give me an LUN with 22Gb. This file system is mounted on: metastat d80... (1 Reply)
Discussion started by: fretagi
1 Replies

7. AIX

Unable to extend volume group(VG)

Would some help me on this below I am trying to extend file system on AIX and however unable to extend the file system. 0516-306 extendvg: Unable to find physical volume 20 in the Device Configuration Database. 0516-321 extendvg: Physical volume u01-lv is not configured. 0516-792... (15 Replies)
Discussion started by: murali969
15 Replies

8. AIX

/usr/sbin/extendvg: Unable to extend volume group

Dear Expret, Help me about my issue, I trying add new disk to volume Group but error: step add new disk to volume group. 1. ~Change a Volume Group Add a Physical Volume to a Volume Group Remove a Physical Volume from a Volume Group Reorganize a Volume Group... (6 Replies)
Discussion started by: williamen
6 Replies

9. Solaris

Unable to create file system (newfs)

Hi I have the following cenario: I have requested a LUN from the NetApp to create a file system, and the netapp admin provide me with one as you can see below, but after following all the steps, I could not create a file system on the device: # format Searching for disks...done ... (11 Replies)
Discussion started by: fretagi
11 Replies

10. Linux

Unable to extend LV

Hi all. I have a Logical volume that I can't extend, with this error message: server171:root:/root# lvextend -L +1024M -v /dev/aplic_vg/siteminderwa_lv Finding volume group aplic_vg Archiving volume group "aplic_vg" metadata (seqno 75). Extending logical volume siteminderwa_lv to... (0 Replies)
Discussion started by: Gabriander
0 Replies
RMUSER(8)						    BSD System Manager's Manual 						 RMUSER(8)

NAME
rmuser -- remove users from the system SYNOPSIS
rmuser [-yv] [-f file] [username ...] DESCRIPTION
The rmuser utility removes one or more users submitted on the command line or from a file. In removing a user from the system, this utility: 1. Removes the user's crontab(1) entry (if any). 2. Removes any at(1) jobs belonging to the user. 3. Sends a SIGKILL signal to all processes owned by the user. 4. Removes the user from the system's local password file. 5. Removes the user's home directory (if it is owned by the user), including handling of symbolic links in the path to the actual home directory. 6. Removes the incoming mail and POP daemon mail files belonging to the user from /var/mail. 7. Removes all files owned by the user from /tmp, /var/tmp, and /var/tmp/vi.recover. 8. Removes the username from all groups to which it belongs in /etc/group. (If a group becomes empty and the group name is the same as the username, the group is removed; this complements adduser(8)'s per-user unique groups.) 9. Removes all message queues, shared memory segments and semaphores owned by the user. The rmuser utility refuses to remove users whose UID is 0 (typically root), since certain actions (namely, killing all the user's processes, and perhaps removing the user's home directory) would cause damage to a running system. If it is necessary to remove a user whose UID is 0, see vipw(8) for information on directly editing the password file. If rmuser was not invoked with the -y option, it will show the selected user's password file entry and ask for confirmation that the user be removed. It will then ask for confirmation to delete the user's home directory. If the answer is in the affirmative, the home directory and any files and subdirectories under it will be deleted only if they are owned by the user. See pw(8) for more details. As rmuser operates, it informs the user regarding the current activity. If any errors occur, they are posted to standard error and, if it is possible for rmuser to continue, it will. The options are as follows: -f file The rmuser utility will get a list of users to be removed from file, which will contain one user per line. Anything following a hash mark ('#'), including the hash mark itself, is considered a comment and will not be processed. If the file is owned by anyone other than a user with UID 0, or is writable by anyone other than the owner, rmuser will refuse to continue. -y Implicitly answer ``yes'' to any and all prompts. Currently, this includes prompts on whether to remove the specified user and whether to remove the home directory. This option requires that either the -f option be used, or one or more user names be given as command line arguments. -v Enable verbose mode. Normally, the output includes one line per removed user; however, with this option rmuser will be much more chatty about the steps taken. username Identifies one or more users to be removed; if not present, rmuser interactively asks for one or more users to be removed. FILES
/etc/master.passwd /etc/passwd /etc/group /etc/spwd.db /etc/pwd.db SEE ALSO
at(1), chpass(1), crontab(1), finger(1), passwd(1), group(5), passwd(5), adduser(8), pw(8), pwd_mkdb(8), vipw(8) HISTORY
The rmuser utility appeared in FreeBSD 2.2. BUGS
The rmuser utility does not comprehensively search the file system for all files owned by the removed user and remove them; to do so on a system of any size is prohibitively slow and I/O intensive. It is also unable to remove symbolic links that were created by the user in /tmp or /var/tmp, as symbolic links on 4.4BSD file systems do not contain information as to who created them. Also, there may be other files cre- ated in /var/mail other than /var/mail/username and /var/mail/.pop.username that are not owned by the removed user but should be removed. The rmuser utility has no knowledge of YP/NIS, and it operates only on the local password file. BSD
May 10, 2002 BSD
All times are GMT -4. The time now is 10:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy