Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Extremely slow file writing with many small files on mounted NAS Post 302946656 by hicksd8 on Thursday 11th of June 2015 05:03:26 AM
Old 06-11-2015
If these are normal hardware RAID controllers (or some software RAID controllers for that matter) you might be able to set the cache; to write-through, write-around and/or write-back.

If the RAID controller cache was set to write-through then the controller will await completion each I/O before proceeding. In the case of millions of small files that would be very painful. You wouldn't see the same degradation with large files because each I/O is bigger.

Search Google (and of course THIS FORUM) for the pro's and con's of these cache settings.
 

10 More Discussions You Might Find Interesting

1. 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

2. Shell Programming and Scripting

Need help writing a small script

Hi I am trying to do the following: run a command that looks at a binary file and formats it find the first line that has what I am looking for (there will be multiple) print the name of the file that has it So I am running this but ti's not working ls -ltr *20080612* | while read line... (3 Replies)
Discussion started by: llsmr777
3 Replies

3. Shell Programming and Scripting

Split a file into 16 small files

Hi I want to split a file that has 'n' number of records into 16 small files. Can some one suggest me how to do this using Unix script? Thanks rrkk (10 Replies)
Discussion started by: rrkks
10 Replies

4. Solaris

why telnet from PC to Solaris x86 is extremely slow?

I got the following info from this forum, in regards to configuring my Solaris x86 to link to the Net: # echo 192.168.0.1 > /etc/defaultrouter # route add default 192.168.0.1 # echo nameserver 192.168.0.1 >> /etc/resolv.conf # cp /etc/nsswitch.dns /etc/nsswitch.conf So I did... (1 Reply)
Discussion started by: newbie09
1 Replies

5. Red Hat

NFS writing so slow

Hi, I facing an NFS problem. I have machine1, which has diskA and diskB, and machine2, both are Mandriva 2009 Linux. When I am on machine2 and NFS mount both diskA and diskB of machine1. Writing to diskA is very fast, but writing to diskB is very slow. I tried different mount rsize and wsize... (2 Replies)
Discussion started by: hiepng
2 Replies

6. 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

7. Shell Programming and Scripting

Check if NAS filesystem is mounted

Anyone know the best way to check and see if a NAS filesystem is mounted on a linux box. I have no idea where to start :wall:. (2 Replies)
Discussion started by: d3mon_spawn
2 Replies

8. Solaris

how to make nas share mounted in zones persistent across reboots?

there are few nas shares that would be mounted on the local zone. should i add an entry into the add an entry in zone.xml file so that it gets mounted automatically when the zone gets rebooted? or whats the correct way to get it mounted automatically when the zone reboots (2 Replies)
Discussion started by: chidori
2 Replies

9. Solaris

Chgrp failed on NAS mounted

Hi, I am facing chgrp issue for a directory on a NAS mounted partation. issue details : user1 belongs to two groups grp1(primary) and grp2(secondary) not able to change directory group to secondary. WORKING on /tmp #mkdir /tmp/a #ls -ld /tmp/a drwxr-xr-x 2 user1 grp1 117 Mar 24... (7 Replies)
Discussion started by: naveen.surisett
7 Replies

10. Red Hat

Related to "NAS" some file system (mounted volumes) were not writable

Dear friends, I have been facing an issue with one of my red hat unix machine, suddenly lost to switch sudo users. My all colleagues lost to switch to access sudo users. Then, we have realized its related to NAS issue which does not allowing to write the file. because of this we got so many... (1 Reply)
Discussion started by: Chand
1 Replies
scnas(1M)						  System Administration Commands						 scnas(1M)

NAME
scnas - manage network-attached storage (NAS) device configuration data for Sun Cluster. SYNOPSIS
scnas [-H] scnas -a [-H] [-n] -h device-name -t device-type -o specific-options [-f input-file] scnas -c [-H] [-n ] -h device-name -o specific-options [-f input-file] scnas -p [-H] [-h device-name] [-t device-type] scnas -r [-H ] -h device-name DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scnas command manages NAS devices in a Sun Cluster configuration. To manage NAS directories in the cluster, use the scnasdir command. You can use the scnas command to create the NAS device configuration, to update the NAS type-specific properties, and to remove the device configuration from Sun Cluster. The options to this command are processed in the order in which they are typed on the command line. The scnas command can only be run from an active cluster node. The results of running the command are always the same, regardless of the nodethat is used. All forms of the scnas command accept the -H option. Specifying -H displays help information. All other options are ignored. Help informa- tion is also printed when scnas is run without options. The NAS device must be set up before using the scnas command to manage a NAS device. Refer to the documentation for the particular NAS device for procedures for setting up a device. You can use this command only in the global zone. OPTIONS
Basic Options The following options are common to all forms of the scnas command: -H If this option is specified on the command line at any position, the command prints help information. All other options are ignored and are not executed. Help information is also printed if scnas is run with no options. You can use this option only in the global zone. -n If this option is specified on the command line at any position, the scnas command only checks the usage and does not write the config- uration data. If the -n option is specified with the -f option, the scnas command checks the input file for the password. The following options modify the basic form and function of the scnas command. None of these options can be combined on the same command line. -a Specifies the add form of the scnas command. You can use this option only in the global zone. The -a option can be used to add a NAS device into the Sun Cluster configuration. Depending on the type of your NAS device, you might have to set additional properties. These required properties are also explained in the -t option description in the "Additional Options" section. -c Specifies the change form of the scnas command. The -c option is used to change specific NAS device properties. You can use this option only in the global zone. -r Specifies the remove form of the scnas command. The -r option is used to remove the NAS device from the Sun Cluster configuration. You can use this option only in the global zone. Before removing a device, all its exported directories must be removed by using scnasdir. -p Specifies the print form of the scnas command. You can use this option only in the global zone. When no other options are given, the -p option prints a listing of all the current NAS devices configured in Sun Cluster and all their associated properties. This option can be used with additional options to query a particular device or a particular type of device. Additional Options The following additional options can be combined with one or more of the previously described basic options to configure all properties for a device. The device does not need to be online to use these options. Refer to the SYNOPSIS section to see the options that can be used with each form of scnas. The additional options are as follows: -h device-name Use this option to specify the name of the NAS device in the Sun Cluster configuration. The device name identifies the device and can be used to remotely access the device by using rhs or telnet. This device name must be specified for the add, change, and remove forms of the scnas command. -t device-type The NAS device type. You must specify this option when you add a NAS device to the Sun Cluster configuration. The NAS device type is identified by the vendor name. You can specify either sun for a NAS device from Sun Microsystems, Inc. or netapp for a NAS device from Network Appliance, Inc. Different types of NAS devices have different or in some cases, no properties. -o specific-options Use this option to provide the properties that are specific to a NAS device type. For example, the NAS device from Network Appliance, Inc. has the following property: -o userid=userid Note - You do not specify properties for the NAS device from Sun Microsystems, Inc. As this device does not have any properties, the -f and -o options do not apply. The userid property is used by the cluster to perform administrative duties on the device. When you add a userid to the device configu- ration, you are prompted for its password. You can also place the password in a text file and use it by specifying the -f option. -finput-file For security reasons, the password cannot be specified in command-line options. To keep the password secure, place it in a text file and specify the file by using the -f option. If you do not specify an input file for the password, the command prompts for the pass- word. Note - You do not specify properties for the NAS device from Sun Microsystems, Inc. As this device does not have any properties, the -f and -o options do not apply. Set permissions of the input file to readable by root and prohibit access by either group or world. In the input file, the password cannot be entered across multiple lines. Leading white spaces and tabs are ignored. Comments begin with an unquoted pound (#) sign, and continue to the next new line. The parser ignores all comments. When you use an input file for the device user password, the # sign cannot be part of the password. EXAMPLES
Example 1 Adding a NAS Device From Sun Microsystems, Inc. to a Cluster The following scnas command adds a Sun Microsystems, Inc. storage system to the Sun Cluster configuration. # scnas -a -h sunnas1 -t sun Example 2 Adding a NAS Device From Network Appliance, Inc. to a Cluster The following scnas command adds a Network Appliance, Inc. storage system to the Sun Cluster configuration. # scnas -a -h netapp1 -t netapp -o userid=root Please enter password: Example 3 Removing a NAS Device From a Cluster The following scnas command removes a NAS device from the Sun Cluster configuration. # scnas -r -h sunnas1 EXIT STATUS
The following exit values are returned: 0 The command executed successfully. nonzero An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clnasdevice(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scnasdir(1M) Sun Cluster 3.2 6 Sep 2007 scnas(1M)
All times are GMT -4. The time now is 05:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy