Sponsored Content
Full Discussion: NFS writing so slow
Operating Systems Linux Red Hat NFS writing so slow Post 302330898 by rcjmack on Thursday 2nd of July 2009 04:32:24 PM
Old 07-02-2009
Could you give me a idea of the hardware specs on the drives, diskA and diskB. Size of partition, etc?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ls -l over NFS slow

I have an HP-UX server with a Network Appliance Filer attached over Gigabit Ethernet. I am noticing very slow response time when using "ls -l" on one directory on one of the several NFS mounted filesystems. The "ls" command by itself does not seem to be a problem. Typically I get a response within... (3 Replies)
Discussion started by: keelba
3 Replies

2. UNIX for Advanced & Expert Users

File writing is slow

Hello Guru, I am using a Pro*C program to prepare some reports usaually the report file size is greater than 1GB. But nowadays program is very slow. I found out the program is taking much time to write data to file ..... is there any unix related reason to be slow down, the file writting... (2 Replies)
Discussion started by: bhagyaraj.p
2 Replies

3. UNIX for Dummies Questions & Answers

Remote server mount slow - NFS

Hi, Following my last post I've mounted the remote server on my local server. However copying files from this mounted server is increadbily slow. If I copy files using rcp it's very fast so I assume there must be a setting somewhere? Any help appreicated. Thanks (2 Replies)
Discussion started by: AngryBunny
2 Replies

4. Red Hat

file writing over nfs very slow

Hi guys, I am trying something. I wrote a simple shell program to test something where continuous while loop writes on a file over the nfs. The time taken to write "hello" 3000 times take about 10 sec which is not right. Ideally it should take fraction of seconds. If I write on the local disk, it... (1 Reply)
Discussion started by: abhig
1 Replies

5. Solaris

Problem with nfs sharing, permission denied for writing.

Hi I have a problem with NFS sharing on solaris 10, the problem simply with write permission, after do the following command, the folder still not writable from machine 2 : on machine 1 (10.10.10.32) : share -F nfs -o rw /u01/portalrepository/ on machine 2 (10.10.10.31) : mount -F nfs... (35 Replies)
Discussion started by: Al-Mothafar
35 Replies

6. Red Hat

RHEL 5.6 Slow rsync to NFS array

Hi All, I have RHEL 5.6 with a 70GB local directory of Web content. Images, PHP scripts etc. I need to copy all this content to an NFS array thats mounted on the RHEL server. I did a baseline cp to copy the content one week ago. Since my baseline copy the local directory has grown by 8GB.... (2 Replies)
Discussion started by: general_lee
2 Replies

7. HP-UX

Writing from Unix DB to Linux NFS

I have an HP Unix server with Oracle DB and want to write Datapumo export files across the network to IMB/Linux NFS. Will that work? (3 Replies)
Discussion started by: Duane McDonough
3 Replies

8. AIX

Slow NFS when cio/dio enabled

Hi, I have a bit of a NFS problem on AiX 6.1 : When I set the mount to cio and dio - needed for a database app - Everything slows down. The following is copying 700mb, top one is a normal mount bottom one is a mount with the cio/dio option enabled : # ./a.sh Wed Jan 11 11:41:24 GMT 2012... (5 Replies)
Discussion started by: AJCG1976
5 Replies

9. UNIX for Dummies Questions & Answers

Extremely slow file writing with many small files on mounted NAS

I am working on a CentOS release 6.4 server which has two mounted NAS devices, one with 20 x 3TB HDD running in FreeBSD with Zfs2 and one NAS which I don't know much about, but which has 7 HDDs in RAID-6. I was running tar -zxvf on a tarball that is 80Mb with 50,000 small files inside. Even... (4 Replies)
Discussion started by: TupTupBoom
4 Replies
idisk(1M)																 idisk(1M)

NAME
idisk - create partitions for disks on an Integrity system SYNOPSIS
partition_description_file}] device DESCRIPTION
creates operating system partitions for disks on an Integrity system. It reads in the partition information from a data file that may be specified in the command string or redirected from stdin. By default, operates in read-only mode and displays the partition information that is currently on the disk. To write new partition infor- mation on the disk the user must specify the option. Options recognizes the following options: Print the primary EFI partition header and partition tables. Print the alternate EFI partition header and partition tables. Print the legacy partition table that resides in the master boot record. writes partition information for the first four partition in the partition table in used by legacy DOS and Win- dows. This information is used as a backup in the event all the EFI information is corrupted. Print the first usable and last usable block numbers that are available to create partitions. First usable is the first block a partition can start on. Last usable is the last block that can be contained in a partition. These numbers are relative to the whole disk and do not take into account any partitions that may exist. They represent the total disk space that can be partitioned. Use the option to only print the values without headings. Work silently. No user prompts or warnings. For use in shell scripts. Validate EFI partition information. Does the same checks the driver does verifying that both the primary and alternate EFI partition headers and tables are correct. Returns two if either is bad and zero if both are correct. Restore the EFI partition headers and tables. This option checks both the primary header and tables and the alternate header and tables. If one is found bad it is restored from the other good ver- sion. One of either the primary or alternate header and tables must be good for this option to succeed. The option must be specified for information to be written to the disk. Remove all EFI partition headers and tables from the disk. This option also destroys the information contained in the MBR (master boot record). The option must be specified for information to be written to the disk. The partition_description_file contains the number of partitions to be created and the type and requested size of each partition. The filename may be specified here or redirected from stdin when the dash is used. Enable write mode. By default operates in read-only mode. To create and write partition information to the disk you must specify the option. Partition Description File The first entry in the partition description file is the number of partitions to create. The maximum number of partitions allowed is 12. This is followed by a line containing the type and size for each of the partitions. Recognized partition types are: and At least one EFI partition is required to create a valid partition table. Size may be specified in megabytes or as a percentage of the whole disk. Internally, creates the partitions whose size is specified in MB first then creates those whose size was specified as a percentage. Those partitions specified as a percent are assigned space from what is available after the MB partitions are created. If the size of a parti- tion is specified as 100% then all space remaining is assigned to that partition. An example partition description file is shown below: The first entry specifies the number of partitions to create. The second specifies an EFI partition of 100 megabytes. The last entry specifies a HPUX partition consisting of all the remaining space on the disk after the EFI partition has been created. When creating partitions, the device file name must be that of the whole disk. Legacy device files must not have any partition number bits set in the minor number. For legacy disk devices, the last eight bits of the minor number represent the option bits. For Integrity system disks, the last four option bits are used to indicate the partition number. Since there are only four bits for parti- tion number, only one to fifteen partitions are supported. For example, a device node with a minor number of 0x008001 would indicate a disk at target eight, partition number one. A minor number of 0x00500F would indicate a disk at target 5 partition fifteen. A minor num- ber with no partition bits set would indicate the whole disk (for example, 0x008000 would be the same disk as above but represent the whole disk and not a partition). Persistent device special files do not use or contain minor number information. A detailed description on persistent device special files can be found in intro(7). Note: For partitions created by device special files must be created for each legacy hardware path to the disk and for the LUN hardware path using or (see intro(7) for details on legacy and agile modes). If legacy mode is disabled (see the descrip- tion of the option in rmsf(1M)), device special files must only be created for the LUN hardware path. Note has been ported to Windows NT 4.0 and 2000. RETURN VALUE
Exit values are: Successful completion. Error condition occurred. EXAMPLES
Create the partitions specified in the above description file, printing only the primary partition information: Create the partitions specified in the above description file, printing only the primary partition information using a persistent device special file (see intro(7)): Create the partitions specified in the above description file, printing all available information (default), redirecting input from stdin: Only read the disk, printing all tables (default) on the disk: Get the first and last usable block for partitioning on the disk: Destroy all partition information on the disk: Restore partition information from either a good primary or alternate header or table to the header or table that is bad: AUTHOR
was developed by HP. SEE ALSO
insf(1M), mksf(1M), efi(4), intro(7). Integrity Systems Only idisk(1M)
All times are GMT -4. The time now is 05:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy