See this thread - it dealt with the same question somehow.
http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg41715.html
Regards,
Robert
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
On Nov 13, 2010, at 7:33 AM, Edward Ned Harvey wrote:
Log devices are generally write-only. They are only read during boot, after
an ungraceful crash. It is extremely difficult to get a significant number
of GB used on the log device, because they are flushed out to primary storage
so
Hello!
I've got a Solaris 10 10/08 Sparc system and use ZFS pool version 15. I'm
playing
around a bit to make it break.
I've created a mirrored Test pool using mirrored log devices:
# zpool create Test \
mirror /dev/zvol/dsk/data/DiskNr1 /dev/zvol/dsk/data/DiskNr2 \
log mirror
On Nov 12, 2010, at 5:21 PM, Alexander Skwar wrote:
Hm. Why are there no errors shown for the logs devices?
You need to crash you machine while log devices are in use, then you'll see
some reads on the next reboot. In use here means that system is actively
writing to log devices at the time
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Alexander Skwar
I've got a Solaris 10 10/08 Sparc system and use ZFS pool version 15. I'm
playing around a bit to make it break.
Now I write some garbage to one of the log mirror devices.
