Sponsored Content
Full Discussion: Disks going full??
Operating Systems Solaris Disks going full?? Post 51761 by pressy on Sunday 30th of May 2004 06:57:52 PM
Old 05-30-2004
..........

hi,

#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??

there is a default minfree on the filesystem.

#Also, is there a way by which I can free
#these inodes other than deleting files
#which are important
i don't see another way then to create a new fs. the inode table is created while the filesytem is created. next time you have to increase the default inode numbers....

newfs -i nbpi

The number of bytes per inode. This specifies the density of inodes in the file system.
The default for nbpi is as follows:.

Disk size Density

-1GB 2048
-2GB 4096
-3GB 6144
3GB- 8192

If fewer inodes are desired, a larger number should be used; to create more inodes, a smaller number should be given. The default is 2048.

#Can a reboot help me??
no, thats not windows *hehe*

greetings pressy
 

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
newfs(1M)                                                 System Administration Commands                                                 newfs(1M)

NAME
newfs - construct a UFS file system SYNOPSIS
newfs [-NTv] [mkfs-options] raw-device DESCRIPTION
newfs is a "friendly" front-end to the mkfs(1M) program for making UFS file systems on disk partitions. newfs calculates the appropriate parameters to use and calls mkfs. If run interactively (that is, standard input is a tty), newfs prompts for confirmation before making the file system. If the -N option is not specified and the inodes of the device are not randomized, newfs calls fsirand(1M). You must be super-user or have appropriate write privileges to use this command, except when creating a UFS file system on a diskette. See EXAMPLES. Creating a Multiterabyte UFS File System Keep the following limitations in mind when creating a multiterabyte UFS file system: o nbpi is set to 1 Mbyte unless you specifically set it higher. You cannot set nbpi lower than 1 Mbyte on a multiterabyte UFS file sys- tem. o fragsize is set equal to bsize. OPTIONS
The following options are supported: -N Print out the file system parameters that would be used to create the file system without actually creating the file sys- tem. fsirand(1M) is not called here. -T Set the parameters of the file system to allow eventual growth to over a terabyte in total file system size. This option sets fragsize to be the same as bsize, and sets nbpi to 1 Mbyte, unless the -i option is used to make it even larger. If you use the -f or -i options to specify a fragsize or nbpi that is incompatible with this option, the user-supplied value of fragsize or nbpi is ignored. -v Verbose. newfs prints out its actions, including the parameters passed to mkfs. mkfs-options Options that override the default parameters are: -a apc The number of alternate sectors per cylinder to reserve for bad block replacement for SCSI devices only. The default is 0. This option is not applicable for disks with EFI labels and is ignored. -b bsize The logical block size of the file system in bytes, either 4096 or 8192. The default is 8192. The sun4u architecture does not support the 4096 block size. -c cgsize The number of cylinders per cylinder group, ranging from 16 to 256. The default is calculated by dividing the number of sectors in the file system by the number of sectors in a gigabyte. Then, the result is mul- tiplied by 32. The default value is always between 16 and 256. mkfs can override this value. See mkfs_ufs(1M) for details. This option is not applicable for disks with EFI labels and is ignored. -C maxcontig The maximum number of logical blocks, belonging to one file, that are allocated contiguously. The default is calculated as follows: maxcontig = disk drive maximum transfer size / disk block size If the disk drive's maximum transfer size cannot be determined, the default value for maxcontig is calcu- lated from kernel parameters as follows: If maxphys is less than ufs_maxmaxphys, which is typically 1 Mbyte, then maxcontig is set to maxphys. Oth- erwise, maxcontig is set to ufs_maxmaxphys. You can set maxcontig to any positive integer value. The actual value will be the lesser of what has been specified and what the hardware supports. You can subsequently change this parameter by using tunefs(1M). -d gap Rotational delay. This option is obsolete in the Solaris 10 release. The value is always set to 0, regard- less of the input value. -f fragsize The smallest amount of disk space in bytes that can be allocated to a file. fragsize must be a power of 2 divisor of bsize, where: bsize / fragsize is 1, 2, 4, or 8. This means that if the logical block size is 4096, legal values for fragsize are 512, 1024, 2048, and 4096. When the logical block size is 8192, legal values are 1024, 2048, 4096, and 8192. The default value is 1024. For file systems greater than 1 terabyte or for file systems created with the -T option, fragsize is forced to match block size (bsize). -i nbpi The number of bytes per inode, which specifies the density of inodes in the file system. The number is divided into the total size of the file system to determine the number of inodes to create. This value should reflect the expected average size of files in the file system. If fewer inodes are desired, a larger number should be used. To create more inodes, a smaller number should be given. The default for nbpi is as follows: Disk size Density Less than 1GB 2048 Less than 2GB 4096 Less than 3GB 6144 3GB to 1 Tbyte 8192 Greater than 1 Tbyte or created with -T 1048576 The number of inodes can increase if the file system is expanded with the growfs command. -m free The minimum percentage of free space to maintain in the file system, between 0% and 99%, inclusively. This space is off-limits to users. Once the file system is filled to this threshold, only the super-user can continue writing to the file system. The default is ((64 Mbytes/partition size) * 100), rounded down to the nearest integer and limited between 1% and 10%, inclusively. This parameter can be subsequently changed using the tunefs(1M) command. -n nrpos The number of different rotational positions in which to divide a cylinder group. The default is 8. This option is not applicable for disks with EFI labels and is ignored. -o space|time The file system can either be instructed to try to minimize the time spent allocating blocks, or to try to minimize the space fragmentation on the disk. The default is time. This parameter can subsequently be changed with the tunefs(1M) command. -r rpm The rotational speed of the disk in revolutions per minute. The default is driver- or device-specific. Note that you specify rpm for newfs and rps for mkfs. This option is not applicable for disks with EFI labels and is ignored. -s size The size of the file system in sectors. The default is to use the entire partition. -t ntrack The number of tracks per cylinder on the disk. The default is taken from the disk label. This option is not applicable for disks with EFI labels and is ignored. OPERANDS
The following operands are supported: raw-device The name of a raw special device residing in the /dev directory (for example, /dev/rdsk/c0t0d0s6) on which to create the file system. USAGE
See largefile(5) for the description of the behavior of newfs when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes). EXAMPLES
Example 1: Displaying the Parameters for the Raw Special Device The following example verbosely displays the parameters for the raw special device, c0t0d0s6. It does not actually create a new file sys- tem: example# newfs -Nv /dev/rdsk/c0t0d0s6 mkfs -F ufs -o N /dev/rdsk/c0t0d0s6 1112940 54 15 8192 1024 16 10 60 2048 t 0 -1 8 /dev/rdsk/c0t0d0s6: 1112940 sectors in 1374 cylinders of 15 tracks, 54 sectors 569.8MB in 86 cyl groups (16 c/g, 6.64MB/g, 3072 i/g) super-block backups (for fsck -b #) at: 32, 13056, 26080, 39104, 52128, 65152, 78176, 91200, 104224, ... Example 2: Creating a UFS File System The following example creates a UFS file system on a diskette that is managed by Volume Manager. example% newfs /vol/dev/aliases/floppy0 newfs: construct a new file system /vol/dev/aliases/floppy0: (y/n)? y /vol/dev/aliases/floppy0: 2880 sectors in 80 cylinders of 2 tracks, 18 sectors 1.4MB in 5 cyl groups (16 c/g, 0.28MB/g, 128 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 640, 1184, 1792, 2336, ... Example 3: Creating a UFS File System That Will Eventually Be Grown to a Multiterabyte UFS File System The following example creates a UFS file system that will eventually be grown to a multiterabyte UFS file system. This command creates a 800-Gbyte file system on the volume, /dev/md/rdsk/d99. # newfs -T /dev/md/rdsk/d99 newfs: construct a new file system /dev/md/rdsk/d99: (y/n)? y /dev/md/rdsk/d99: 1677754368 sectors in 45512 cylinders of 144 tracks, 256 sectors 819216.0MB in 1821 cyl groups (25 c/g, 450.00MB/g, 448 i/g) ... Then, if you increase the volume size for this file system, you can use the growfs command to expand the file system. The file system is grown to 1.2 terabytes in this example: # growfs -v /dev/md/rdsk/d99 /usr/lib/fs/ufs/mkfs -G /dev/md/rdsk/d99 2516631552 /dev/md/rdsk/d99: 2516631552 sectors in 68268 cylinders of 144 tracks, 256 sectors 1228824.0MB in 2731 cyl groups (25 c/g, 450.00MB/g, 448 i/g)... EXIT STATUS
The following exit values are returned: 0 The operation was successful. 1, 10 Usage error or internal error. A message is output to STDERR explaining the error. Other exit values may be returned by mkfs(1M), which is called by newfs. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
fsck(1M), fsck_ufs(1M), fsirand(1M), mkfs(1M), mkfs_ufs(1M), tunefs(1M), attributes(5), largefile(5), ufs(7FS) DIAGNOSTICS
newfs: No such file or directory The device specified does not exist, or a disk partition was not specified. special: cannot open You must write access to the device to use this command. SunOS 5.10 6 Nov 2003 newfs(1M)
All times are GMT -4. The time now is 07:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy