Sponsored Content
Full Discussion: ZFS Filesystem
Operating Systems Solaris ZFS Filesystem Post 302953085 by tharmendran on Tuesday 25th of August 2015 09:34:26 AM
Old 08-25-2015
Hi jlliagre,

Currently we use the affected filesystem to store database related files such tables,indexes.

Below is the our current ZFS setting. Mostly i heard arc_max,zfs:zfs_vdev_max_pending,ssd:ssd_max_throttle parameter need to fine tune. Is that rite?


Code:
arc_reduce_dnlc_percent = 0x3
zfs_arc_max = 0x0
zfs_arc_min = 0x0
arc_shrink_shift = 0x7
zfs_mdcomp_disable = 0x0
zfs_prefetch_disable = 0x0
zfetch_max_streams = 0x8
zfetch_min_sec_reap = 0x2
zfetch_block_cap = 0x100
zfetch_array_rd_sz = 0x100000
zfs_default_bs = 0x9
zfs_default_ibs = 0xe
metaslab_aliquot = 0x80000
mdb: variable reference_tracking_enable not found: unknown symbol name
mdb: variable reference_history not found: unknown symbol name
spa_max_replication_override = 0x3
spa_mode_global = 0x3
zfs_flags = 0x0
zfs_txg_synctime_ms = 0x1388
zfs_txg_timeout = 0x1e
zfs_write_limit_min = 0x2000000
zfs_write_limit_max = 0xfb4d0c00
zfs_write_limit_shift = 0x3
zfs_write_limit_override = 0x0
zfs_no_write_throttle = 0x0
zfs_vdev_cache_max = 0x4000
zfs_vdev_cache_size = 0x0
zfs_vdev_cache_bshift = 0x10
vdev_mirror_shift = 0x15
zfs_vdev_max_pending = 0xa
zfs_vdev_min_pending = 0x4
zfs_vdev_future_pending = 0xa
zfs_scrub_limit = 0xa
zfs_no_scrub_io = 0x0
zfs_no_scrub_prefetch = 0x0
zfs_vdev_time_shift = 0x6
zfs_vdev_ramp_rate = 0x2
zfs_vdev_aggregation_limit = 0x20000
fzap_default_block_shift = 0xe
zfs_immediate_write_sz = 0x8000
zfs_read_chunk_size = 0x100000
zfs_nocacheflush = 0x0
zil_replay_disable = 0x0
metaslab_gang_threshold = 0x100001
metaslab_df_alloc_threshold = 0x100000
metaslab_df_free_pct = 0x4
zio_injection_enabled = 0x0
zvol_immediate_write_sz = 0x8000

One more thing the documentation say need to change the logbias setting for database filesystem

My current database fileystem as below;
Code:
NAME           PROPERTY       VALUE         SOURCE
ora2pool/ora2  primarycache   all           default
ora2pool/ora2  recordsize     128K          default
ora2pool/ora2  compressratio  1.00x         -
ora2pool/ora2  compression    off           default
ora2pool/ora2  available      351G          -
ora2pool/ora2  used           484G          -
ora2pool/ora2  quota          none          default
ora2pool/ora2  logbias        latency       default

 

7 More Discussions You Might Find Interesting

1. Solaris

How do I export a zfs filesystem that I created?

I created a zpool and two ZFS volumes in OpenSolaris. I would like both ZFS volumes to be exportable. However, I don't know how to set that up. These are the steps I did: 1) Create the zpool using raidz1 across five disks. I have six disks and created a zpool across 5 of them. c4t0d0... (3 Replies)
Discussion started by: sqa777
3 Replies

2. Solaris

Why does the # of blocks change for a file on a ZFS filesystem?

I created a zpool and zfs filesystem in OpenSolaris. I made two NFS mount points: > zpool history History for 'raidpool': 2009-01-15.17:12:48 zpool create -f raidpool raidz1 c4t1d0 c4t2d0 c4t3d0 c4t4d0 c4t5d0 2009-01-15.17:15:54 zfs create -o mountpoint=/vol01 -o sharenfs=on -o... (0 Replies)
Discussion started by: sqa777
0 Replies

3. Solaris

Mount old zfs filesystem

Hey all, I have a machine with 16 drive slots. Two of the drives have a ZFS mirror of the operating system, the other 14 contain the storage raidz. So, after installing Opensolaris on the OS drives, how can I remount the storage raid? TIA (11 Replies)
Discussion started by: PatrickBaer
11 Replies

4. Filesystems, Disks and Memory

Howto Convert a filesystem from Veritas to ZFS?

Hi Folks, Looking for info here more than any actual HowTo, does anyone know if there is an actual way of converting a Veritas or UFS filesystem to ZFS leaving the resident data intact. All that I have been able to find, including the commercial products seem to require the FS backed up from... (1 Reply)
Discussion started by: gull04
1 Replies

5. Solaris

Please explain why ZFS is said to be a hybrid filesystem and a volume manager also

Hi guys! How come ZFS is said to be not just a filesystem but a hybrid filesystem and also a volume manager? Please explain. I will appreciate your replies. Hope you can help me figure this out. Thanks in advance! (1 Reply)
Discussion started by: Klyde
1 Replies

6. Solaris

Extend zfs storage filesystem

Hello, Need to ask the question regarding extending the zfs storage file system. currently after using the command, df -kh u01-data-pool/data 600G 552 48G 93% /data /data are only 48 gb remaining and it has occupied 93% for total storage. zpool u01-data-pool has more then 200 gb... (14 Replies)
Discussion started by: shahzad53
14 Replies

7. UNIX for Beginners Questions & Answers

How to finish expanding a zfs filesystem?

I have a esxi 6.7 server running a Solaris 10 x86 vm (actually a bunch of them). The VM uses zfs for the pools (of course). I expand the underlying ESX logical disk, for example from 50GB to 100gb, then I set autoexpand=on <pool> that belongs to the esx logical disk. what am i missing to... (2 Replies)
Discussion started by: mrmurdock
2 Replies
SNAPPER-CONFIGS(5)					  Filesystem Snapshot Management					SNAPPER-CONFIGS(5)

NAME
snapper-configs - Configuration files for snapper configs DESCRIPTION
Each file /etc/snapper/configs/* describes a snapper config. VARIABLES
The following is a list of variables that can be present in the configuration file. Boolean values must be "yes" or "no". SUBVOLUME=path Path of the subvolume or mount point. There is no default value. The value must always be specified. FSTYPE=value Filesystem type for the subvolume. Default value is "btrfs" but it's recommended to always specify the filesystem type. ALLOW_USERS=users List of users allowed to operate with the config. The user-names must be separated by spaces. Spaces in usernames can be escaped with a "". Default value is "" but "root" is always implicitly included. ALLOW_GROUPS=groups List of groups allowed to operate with the config. The group-names must be separated by spaces. Spaces in group-names can be escaped with a "". Default value is "". BACKGROUND_COMPARISON=boolean Defines whether pre and post snapshots should be compared in the background after creation. Default value is "no". NUMBER_CLEANUP=boolean Defines whether the number cleanup algorithm should be run for the config. Default value is "no". NUMBER_MIN_AGE=seconds Minimal age for snapshots to be deleted by the number cleanup algorithm. Default value is "1800". NUMBER_LIMIT=number Defines how many snapshots the number cleanup algorithm should keep. The youngest snapshots will be kept. Default value is "50". TIMELINE_CREATE=boolean Defines whether hourly snapshots should be created. Together with the timeline cleanup algorithm this will create a collection of snapshots with more snapshots is the near past and less snapshots in the far past. Default value is "no". TIMELINE_CLEANUP=boolean Defines whether the timeline cleanup algorithm should be run for the config. Default value is "no". TIMELINE_MIN_AGE=seconds Minimal age for snapshots to be deleted by the timeline cleanup algorithm. Default value is "1800". TIMELINE_LIMIT_HOURLY=number Defines how many hourly snapshots the timeline cleanup algorithm should keep. An hourly snapshots is the first snapshot in an hour. The youngest hourly snapshots will be kept. Default value is "10". TIMELINE_LIMIT_DAILY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". TIMELINE_LIMIT_MONTHLY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". TIMELINE_LIMIT_YEARLY=number Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The youngest daily snapshots will be kept. Default value is "10". EMPTY_PRE_POST_CLEANUP=boolean Defines whether the empty-pre-post cleanup algorithm should be run for the config. Default value is "no". EMPTY_PRE_POST_MIN_AGE=seconds Minimal age for snapshots to be deleted by the empty-pre-post cleanup algorithm. Default value is "1800". HOMEPAGE
http://snapper.io/ AUTHORS
Arvin Schnell <aschnell@suse.de> SEE ALSO
snapper(8), snapperd(8) 0.1.7 2013-07-09 SNAPPER-CONFIGS(5)
All times are GMT -4. The time now is 05:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy