Hello,
Bob Friesenhahn wrote:
On Thu, 3 Dec 2009, mbr wrote:
What about the data that were on the ZILlog SSD at the time of
failure, is
a copy of the data still in the machines memory from where it can be used
to put the transaction to the stable storage pool?
The intent log SSD is used as 'write only' unless the system reboots, in
which case it is used to support recovery. The system memory is used as
the write path in the normal case. Once the data is written to the
intent log, then the data is declared to be written as far as higher
level applications are concerned.
thank you Bob for the clarification.
So I don't need a mirrored ZILlog for security reasons, all the information
is still in memory and will be used from there by default if only the ZILlog
SSD fails.
If the intent log SSD fails and the system spontaneously reboots, then
data may be lost.
I can live with the data loss as long as the machine comes up with the faulty
ZILlog SSD but otherwise without probs and with a clean zpool.
Has the following error no consequences?
Bug ID 6538021
Synopsis Need a way to force pool startup when zil cannot be replayed
State 3-Accepted (Yes, that is a problem)
Link http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6538021
Michael.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
