Tag Info

Hot answers tagged

7

Don't go down the road of breaking the ZFS array to "rotate" disks offsite. As you've seen, the rebuild time is high and the resolver will read/verify the entire used size of the dataset. If you have the ability, snapshots and sending data to a remote system is a clean, non-intrusive approach. I suppose you could go through the process of having a dedicated ...


6

ZFS pool information is not stored in a plain text file. Information about a pool is stored on the disks themselves. ZFS pool information can also be written to a ZFS cache file, but it does not contain mount point information. If you want to get mount point values for your ZFS pools you can use the following: zfs get mountpoint <pool name> zfs get ...


6

RAIDZ2 isn't going to be especially fast with 4 SATA disks... on a server with 4GB of RAM... with a weak processor... and without any level of ZFS tuning. ZFS mirrors would have been a better choice for a few reasons as well. However, have you measured actually filesystem performance? What are you expecting to see? That's about right, based on the gear ...


4

As Gene points out, the list of file systems (not partitions!) in a ZFS pool is stored within the pool itself. Specifically, it is stored as a part of the pool metadata, which is not easily accessible in raw form. You can access the metadata using zdb (the ZFS debugger tool), but you need to be careful as well as have some familiarity with the ZFS on-disk ...


2

Hmmm, some bad information here. For 4 disks, there's really nothing wrong with XFS. I tend to avoid ZFS RAIDZ for performance and expandability reasons (low reads/writes, can't be expanded). Use ZFS mirrors if you can. However, with 4 disks and nowhere to place your OS, you'll either lose a lot of capacity or have to go through odd partitioning games to fit ...


2

It may not be zfs - you have lots of free memory, so consider this possibility - echo 'pg_contig_disable/D' | mdb -k If the output is: echo pg_contig_disable/D | mdb -k pg_contig_disable: pg_contig_disable: 0 You may be experiencing a sort of NUMA issue. Solaris 10 tries to facilitate faster memory access by setting up blocks of memory for ...


1

Thanks to jim mcnamara for pointing me in the right direction. I wasn't seeing symptoms consistent with the pg_contig_disable issue, but it did lead me to an issue with zfetch. I found the same issue we were having on the following site: http://solaristalk.blogspot.com/2014_05_01_archive.html This led to a tuning article on the Oracle site describing why ...


1

An alternative implementation is to create a ZVOL block device (http://zfsonlinux.org/example-zvol.html), use LUKS to encrypt the newly created ZVOL and then create an ext4 (or other) filesystem on top of the encrypted block device.


1

The top and bottom 512 kilobytes of the disk/partition contain the labels, which include a listing of the last few uberblocks (for recovery and rollback) and the RAID geometry of the pool (more specifically the vdev the disk was part of). By making a new pool you've almost certainly wiped out the old labels. This means you need to know the exact geometry of ...



Only top voted, non community-wiki answers of a minimum length are eligible