That really doesn't say anything about the file system. For example; by default Linux also heavily uses caching, which will easily give the impression that certain file system related actions are much faster, while in fact everything is simply happening in the background where you'll be unaware of this.MHA152 said:I am using the UFS filesystem, but it's slow because when I was using Linux and the ext4 filesystem the speed of copying and moving files was more than now.
[file]async[/file]
All I/O to the file system should be done asynchronously.
This is a [u]dangerous[/u] flag to set, since it does not guar-
antee that the file system structure on the disk will
remain consistent. For this reason, the async flag
should be used sparingly, and only when some data recov-
ery mechanism is present.
[file]noatime[/file]
Do not update the file access time when reading from a
file. This option is useful on file systems where there
are large numbers of files and performance is more criti-
cal than updating the file access time (which is rarely
ever important). This option is currently only supported
on local file systems.
[cmd=#] tunefs -p /dev/mirror/gm0s1a[/cmd]
tunefs: POSIX.1e ACLs: (-a) disabled
tunefs: NFSv4 ACLs: (-N) disabled
tunefs: MAC multilabel: (-l) disabled
tunefs: [color=blue]soft updates: (-n) enabled[/color]
tunefs: soft update journaling: (-j) disabled
tunefs: gjournal: (-J) disabled
tunefs: trim: (-t) disabled
tunefs: maximum blocks per file in a cylinder group: (-e) 4096
tunefs: average file size: (-f) 16384
tunefs: average number of files in a directory: (-s) 64
tunefs: minimum percentage of free space: (-m) 8%
tunefs: optimization preference: (-o) time
tunefs: volume label: (-L)
# Device Mountpoint FStype Options Dump Pass#
/dev/mirror/gm0s1a / ufs rw,[color=blue]noatime[/color] 1 1
/dev/mirror/gm0s1b none swap sw 0 0
/dev/mirror/gm0s1d /usr ufs rw,[color=blue]noatime[/color] 2 2
MHA152 said:I have 3 GB RAM but I don't like ZFS because I don't need many ability and I just want to have a good filesystem.