Sponsored Content
Full Discussion: Disks going full??
Operating Systems Solaris Disks going full?? Post 51752 by encrypted on Saturday 29th of May 2004 09:20:30 PM
Old 05-29-2004
Hi

I thinks that's quite true . If I look at the output of that command on my system it shows:

97% usage for /export/home.

But, still I have one doubt . I am able to create a file with root access but not as a normal user. Why is this happening??
Also, is there a way by which I can free these inodes other than deleting files which are important .Can a reboot help me??

Thanks,
encryptedSmilie
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how many disks do I have?

Hi How do I check how many disks do I have in Solaris & HP-UX? Also what does this mean c9t1d5 in /dev/dsk what is c, t, d etc cheers (8 Replies)
Discussion started by: g-e-n-o
8 Replies

2. Solaris

probing disks

I am setting up a Storedge Multipack and upon booting(stop + a) I did a probe-scsi all. Is there any way of viewing this output one page at a time?....it scrolls by too fast and I cannot get all the info. Also it lists the drives here, but after logging in format does not show them. How... (7 Replies)
Discussion started by: finster
7 Replies

3. Solaris

What do you use to wipe your disks?

What are y'all using to wipe your solaris disks? I am being question by IT Security, what I am using to wipe disk. Is anyone using a 3rd party utility? I have used the format utility in solaris previously. But they are looking for something commercial that I can use. Anyone have... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

4. Solaris

Re-using disks

I would like to know if I can move the disks from a V240 chassis into a V440 chassis to use the increased resources (CPU & Memory) to boost performance. I know you can move disks between V210/240 chassis's, but I'm not sure if this would work between 240s & 440s. Any help would be much appreciated. (4 Replies)
Discussion started by: Chains
4 Replies

5. Solaris

Are my disks mirrored ?

# metastat d1: Mirror Submirror 0: d11 State: Okay Submirror 1: d12 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 14582208 blocks (7.0 GB) d11: Submirror of d1 State: Okay Size: 14582208 blocks... (2 Replies)
Discussion started by: Exposure
2 Replies

6. Shell Programming and Scripting

How to extract strings from full path when full path is not fixed

/Path/snowbird9/nrfCompMgrRave1230100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird6/nrfCompMgrRave1220100920.log.gz:09/20/2010 06:14:51 ERROR Error Message. /Path/snowbird14/nrfCompMgrRave920100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.... (0 Replies)
Discussion started by: Shirisha
0 Replies

7. UNIX for Dummies Questions & Answers

No Disks Found RH 5.1

hi guys I am trying to install RedHat 5.1 x64 in a x3650 M3 IBM Server which has a ServeRAID m5014 Controller but I get the message No Disks Found so I cannot install RedHat any idea how to load or install the drivers? thanks a lot guys (3 Replies)
Discussion started by: karlochacon
3 Replies

8. Solaris

Where are my other disks on T5220 ?

Hi, I got a (used) server to install Solaris 11 and wipe out every information on existing disks. There are 6 disks of 300GB and two disks of 146GB. I am not able to figure out, how to find out RAID (if there is any) and break it. Can anybody help me with that ? Below is configuration. I have... (18 Replies)
Discussion started by: solaris_1977
18 Replies

9. AIX

100% Inode full with only 67% FS full.

AIX Version 6.1 and 7.1. I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device. It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
DELUSER(8)                                                    System Manager's Manual                                                   DELUSER(8)

NAME
deluser, delgroup - remove a user or group from the system SYNOPSIS
deluser [options] [--force] [--remove-home] [--remove-all-files] [--backup] [--backup-to DIR] user deluser --group [options] group delgroup [options] [--only-if-empty] group deluser [options] user group COMMON OPTIONS [--quiet] [--system] [--help] [--version] [--conf FILE] DESCRIPTION
deluser and delgroup remove users and groups from the system according to command line options and configuration information in /etc/deluser.conf and /etc/adduser.conf. They are friendlier front ends to the userdel and groupdel programs, removing the home directory as option or even all files on the system owned by the user to be removed, running a custom script, and other features. deluser and del- group can be run in one of three modes: Remove a normal user If called with one non-option argument and without the --group option, deluser will remove a normal user. By default, deluser will remove the user without removing the home directory, the mail spool or any other files on the system owned by the user. Removing the home directory and mail spool can be achieved using the --remove-home option. The --remove-all-files option removes all files on the system owned by the user. Note that if you activate both options --remove-home will have no effect because all files including the home directory and mail spool are already covered by the --remove-all-files option. If you want to backup all files before deleting them you can activate the --backup option which will create a file username.tar(.gz|.bz2) in the directory specified by the --backup-to option (defaulting to the current working directory). Both the remove and backup options can also be activated for default in the configuration file /etc/deluser.conf. See deluser.conf(5) for details. If you want to remove the root account (uid 0), then use the --force parameter; this may prevent to remove the root user by accident. If the file /usr/local/sbin/deluser.local exists, it will be executed after the user account has been removed in order to do any local cleanup. The arguments passed to deluser.local are: username uid gid home-directory Remove a group If deluser is called with the --group option, or delgroup is called, a group will be removed. Warning: The primary group of an existing user cannot be removed. If the option --only-if-empty is given, the group won't be removed if it has any members left. Remove a user from a specific group If called with two non-option arguments, deluser will remove a user from a specific group. OPTIONS
--conf FILE Use FILE instead of the default files /etc/deluser.conf and /etc/adduser.conf --group Remove a group. This is the default action if the program is invoked as delgroup. --help Display brief instructions. --quiet Suppress progress messages. --system Only delete if user/group is a system user/group. This avoids accidentally deleting non-system users/groups. Additionally, if the user does not exist, no error value is returned. This option is mainly for use in Debian package maintainer scripts. --only-if-empty Only remove if no members are left. --backup Backup all files contained in the userhome and the mailspool-file to a file named /$user.tar.bz2 or /$user.tar.gz. --backup-to Place the backup files not in / but in the directory specified by this parameter. This implicitly sets --backup also. --remove-home Remove the home directory of the user and its mailspool. If --backup is specified, the files are deleted after having performed the backup. --remove-all-files Remove all files from the system owned by this user. Note: --remove-home does not have an effect any more. If --backup is specified, the files are deleted after having performed the backup. --version Display version and copyright information. RETURN VALUE
0 The action was successfully executed. 1 The user to delete was not a system account. No action was performed. 2 There is no such user. No action was performed. 3 There is no such group. No action was performed. 4 Internal error. No action was performed. 5 The group to delete is not empty. No action was performed. 6 The user does not belong to the specified group. No action was performed. 7 You cannot remove a user from its primary group. No action was performed. 8 The required perl-package 'perl modules' is not installed. This package is required to perform the requested actions. No action was performed. 9 For removing the root account the parameter "--force" is required. No action was performed. FILES
/etc/deluser.conf Default configuration file for deluser and delgroup /usr/local/sbin/deluser.local Optional custom add-ons. SEE ALSO
adduser(8), deluser.conf(5), groupdel(8), userdel(8) COPYRIGHT
Copyright (C) 2000 Roland Bauerschmidt. Modifications (C) 2004 Marc Haber and Joerg Hoh. This manpage and the deluser program are based on adduser which is: Copyright (C) 1997, 1998, 1999 Guy Maor. Copyright (C) 1995 Ted Hajek, with a great deal borrowed from the original Debian adduser Copyright (C) 1994 Ian Murdock. deluser is free software; see the GNU General Public Licence version 2 or later for copying conditions. There is no warranty. Debian GNU/Linux Version 3.116ubuntu1 DELUSER(8)
All times are GMT -4. The time now is 04:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy