That will be inaccurate because of cache... stuff written to disk just gets shoved into memory until the disk's ready. 30 gigs would probably fill the cache, but still, there's better ways that don't involve waiting for 30 gigs of data to be written.
Linux usually has the hdparm command. It has read tests that take just a few seconds:
There's no equivalent write-speed test but, for a traditional hard disk, read speed and write speed should be about the same.
If a file size increases in Linux/UNIX to say in GB's then will there be a decrease in write speed.
I mean will it take more time to write to a large file then to a small one??
Please clarify?
Thanks in advance (2 Replies)
I analysed disk performance with blktrace and get some data:
read:
8,3 4 2141 2.882115217 3342 Q R 195732187 + 32
8,3 4 2142 2.882116411 3342 G R 195732187 + 32
8,3 4 2144 2.882117647 3342 I R 195732187 + 32
8,3 4 2145 ... (1 Reply)
Hi,
We have smb client running on two of the linux boxes and smb server on another linux system. During a backup operation which uses smb, read of a file was allowed while write to the same file was going on.Also simultaneous writes to the same file were allowed.Following are the settings in the... (1 Reply)
Would simply like to write data (no audio) to a CD/RW disk. The disk drive states CD/RW on the front but don't know for sure if the software is configured to recognize it as a writable disk. I can read/move data from the disk to the hard drive with no issue from the disk. Any help in this... (4 Replies)
I am now on Kernel 2.6.32-26
For me 16x CD write speed is okay.
I have old hardware which was able to write DVDs at 1x, back in previous linux version.
Now, I dont get speed of less than 4x.
Tested on k3b, xfburn, and brasero. But all start at bottom 4x write speed. k3b forced back to... (0 Replies)
Hi,
I went to a computer store and the salesman sold me a SATA cable and told me that all SATA cables are the same. Another salesman at a different store told me a cable rated for SATA 2, which I bought, MIGHT work as well as one rate for SATA 3 but it is not guaranteed. I decided to run a... (3 Replies)
hi all:
as we know , when usb flash disk plug in and aotu mounted , the default permission of the usb flash disk is 700. that means others have no permission . the question: how to make others have read/write permission when the aotu mounted usb flash disk pluge in ? thanks !! (0 Replies)
Hi,
We have two servers in scenario (vmsoldot01 is Oracle VM with Linux and tldtppod15 is physical Linux server). One NAS share is mounted on both servers with similar permissions and access. But READ speed is too bad on virtual in comparison to physical server.
While trying to diagnose this, I... (2 Replies)
Hello All,
I am building a real time parser for a log file in my application.
The log file is continuously written at a very fast pace and gets rolled over every 10 minutes.
I have measured the speed and observed that around 1000 lines are written to it every second, each line about 30-40... (7 Replies)
Discussion started by: cool.aquarian
7 Replies
LEARN ABOUT DEBIAN
share
share(1M)share(1M)NAME
share - make local resource available for mounting by remote systems
SYNOPSIS
share [-F FSType] [-o specific_options] [-d description] [pathname]
The share command exports, or makes a resource available for mounting, through a remote file system of type FSType. If the option -F FSType
is omitted, the first file system type listed in /etc/dfs/fstypes is used as default. For a description of NFS specific options, see
share_nfs(1M). pathname is the pathname of the directory to be shared. When invoked with no arguments, share displays all shared file sys-
tems.
-F FSType
Specify the filesystem type.
-o specific_options
The specific_options are used to control access of the shared resource. (See share_nfs(1M) for the NFS specific options.) They may be
any of the following:
rw
pathname is shared read/write to all clients. This is also the default behavior.
rw=client[:client]...
pathname is shared read/write only to the listed clients. No other systems can access pathname.
ro
pathname is shared read-only to all clients.
ro=client[:client]...
pathname is shared read-only only to the listed clients. No other systems can access pathname.
Separate multiple options with commas. Separate multiple operands for an option with colons. See .
-d description
The -d flag may be used to provide a description of the resource being shared.
Example 1: Sharing a Read-Only Filesystem
This line will share the /disk file system read-only at boot time.
share -F nfs -o ro /disk
Example 2: Invoking Multiple Options
The following command shares the filesystem /export/manuals, with members of the netgroup having read-only access and users on the speci-
fied host having read-write access.
share -F nfs -o ro=netgroup_name,rw=host1:host2:host3 /export/manuals
/etc/dfs/dfstab
list of share commands to be executed at boot time
/etc/dfs/fstypes
list of file system types, NFS by default
/etc/dfs/sharetab
system record of shared file systems
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mountd(1M), nfsd(1M), share_nfs(1M), shareall(1M), unshare(1M), attributes(5)
Export (old terminology): file system sharing used to be called exporting on SunOS 4.x, so the share command used to be invoked as
exportfs(1B) or /usr/sbin/exportfs.
If share commands are invoked multiple times on the same filesystem, the last share invocation supersedes the previous--the options set by
the last share command replace the old options. For example, if read-write permission was given to usera on /somefs, then to give read-
write permission also to userb on /somefs:
example% share -F nfs -o rw=usera:userb /somefs
This behavior is not limited to sharing the root filesystem, but applies to all filesystems.
9 Dec 2004 share(1M)