Sponsored Content
Full Discussion: ZFS Filesystem
Operating Systems Solaris ZFS Filesystem Post 302955400 by tharmendran on Thursday 17th of September 2015 05:18:12 AM
Old 09-17-2015
Hi achenlejlliagre,
We are using RMAN backup. The DB is LDOM which we hosted in CDOM host. Futher check find out that, even LDOM level no io queue but saw io queue at CDOM hostserver while backup running. Is that normal
 

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 02:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy