Re: [zfs-discuss] recovering from "zfs destroy -r"

Those were backups. What about http://www.solarisinternals.com/wiki/index.php/ZFS_forensics_scrollback_script? I am willing to give it a go. Thanks, P On 27 Jun 2011, at 09:32, "Roy Sigurd Karlsbakk" mailto:r...

[zfs-discuss] recovering from "zfs destroy -r"

Hi, Is there a simple way of rolling back to a specific TXG of a volume to recover from such a situation? Many thanks, Przem ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] OCZ Vertex 2 Pro performance numbers

On 25 Jun 2010, at 15:23, Thomas Burgess mailto:wonsl...@gmail.com>> wrote: Conclusion: This device will make an excellent slog device. I'll order them today ;) I have one and i love it...I sliced it though, used 9 gb for ZIL and the rest for L2ARC (my server is on a smallish network with abo

Re: [zfs-discuss] SSDs adequate ZIL devices?

On 15/06/2010 23:46, "Christopher George" wrote: >> So why buy SSD for ZIL at all? > > For the record, not all SSDs "ignore cache flushes". There are at least > two SSDs sold today that guarantee synchronous write semantics; the > Sun/Oracle LogZilla and the DDRdrive X1. Also, I believe it

Re: [zfs-discuss] High-Performance ZFS (2000MB/s+)

On 15/06/2010 12:42, "Arve Paalsrud" wrote: > Hi, > > We are currently building a storage box based on OpenSolaris/Nexenta using > ZFS. > Our hardware specifications are as follows: > > Quad AMD G34 12-core 2.3 GHz (~110 GHz) > 10 Crucial RealSSD (6Gb/s) > 42 WD RAID Ed. 4 2TB disks + 6Gb/s SAS

Re: [zfs-discuss] [storage-discuss] iscsitgtd failed request to share on zpool import after upgrade from b104 to b134

Anybody has an idea what I can do about it? On 04/05/2010 16:43, "eXeC001er" wrote: > Perhaps the problem is that the old version of pool have shareiscsi, but new > version have not this option, and for share LUN via iscsi you need to make > lun-mapping. > > > >

Re: [zfs-discuss] [storage-discuss] iscsitgtd failed request to share on zpool import after upgrade from b104 to b134

Jim, On May 4, 2010, at 3:45 PM, Jim Dunham wrote: >> >> On May 4, 2010, at 2:43 PM, Richard Elling wrote: >> >> >On May 4, 2010, at 5:19 AM, Przemyslaw Ceglowski wrote: >> > >> >> It does not look like it is: >> >> >> &g

Re: [zfs-discuss] [storage-discuss] iscsitgtd failed request to share on zpool import after upgrade from b104 to b134

On May 4, 2010, at 2:43 PM, Richard Elling wrote: >On May 4, 2010, at 5:19 AM, Przemyslaw Ceglowski wrote: > >> It does not look like it is: >> >> r...@san01a:/export/home/admin# svcs -a | grep iscsi >> online May_01 svc:/network/iscsi/initiator:default

Re: [zfs-discuss] [storage-discuss] iscsitgtd failed request to share on zpool import after upgrade from b104 to b134

..@gmail.com] >Sent: 04 May 2010 13:14 >To: Przemyslaw Ceglowski >Subject: Re: [storage-discuss] iscsitgtd failed request to share on zpool >import after upgrade from b104 to b134 > >Look and see if the target daemon service is still enabled. COMSTAR has been >the official sc

[zfs-discuss] iscsitgtd failed request to share on zpool import after upgrade from b104 to b134

Hi, I am posting my question to both storage-discuss and zfs-discuss as I am not quite sure what is causing the messages I am receiving. I have recently migrated my zfs volume from b104 to b134 and upgraded it from zfs version 14 to 22. It consist of two zvol's 'vol01/zvol01' and 'vol01/zvol02