Tag Info

New answers tagged

1

Basicly there is no official way to recover other than restore from backup. But there is ZFS feature called rewind, that may be possible to remove transactions from the pool to a point that the pool is functional again. The following text is from ZFS Internals blog part #11 DO NOT TRY IT IN PRODUCTION. USE AT YOUR OWN RISK! zpool import -FX mypool ...


4

I'm using ZFS with non-ECC RAM. Widely enough. I'm not writing this to say it's safe. However, for several years I didn't see zfs corruption yet. Furthermore, when using zfs on ancient hardware, I saw all sort of memory problems, even an inability to boot up. From my experience - you will encounter all sorts of fatal kernel traps faster than the zfs data ...


4

The problem is zfs's error correction features (checksum & scrub) can potentially result in a total loss of data on a memory corruption error as opposed to say xfs which will happily write your error to disk in just the affected block(s).


1

option - when you want to stay with FreeBSD, check FreeNAS to automate complexity you are afraid of. option - NexentaStor, it is Solaris based storage appliance SW with great management web gui. Up to 18TB setup is for free. Again there you can easily manage complex zfs send|receive vs. a lot of datasets configuration. If you have speedy lines between ...


0

What you need is the sas2ircu utility from LSI (now Avago). LSI maintains versions for FreeBSD, Linux and Windwos. With FreeNAS you will need the FreeBSD version. To try it you would put it in the /tmp directory and make it executable first. Step one is discover the ID of your SAS HBA (example): /tmp# ./sas2ircu list LSI Corporation SAS2 IR Configuration ...


2

After further experimentation I've found a fair solution, however it comes with a significant trade-off. Disks which have been offline'd but not detached can later be brought back online with only an incremental resilvering operation ("When a device is brought online, any data that has been written to the pool is resynchronized with the newly available ...


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 ...


11

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 resilvering process will read/verify the 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 ...


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 ...



Top 50 recent answers are included