This should work. It shouldn't even lose the in-flight transactions.
ZFS reverts to using the main pool if a slog write fails or the
slog fills up.
So, the only way to lose transactions would be a crash or power loss,
leaving outstanding transactions in the log, followed by the
On 10/18/07, Neil Perrin [EMAIL PROTECTED] wrote:
The umem one is unavailable, but the Gigabyte model is easy to find.
I had Amazon overnight one to me, it's probably sitting at home right
now.
Cool let us know how it goes.
Not so well. I was completely unable to get the card to work
On 10/22/07, Scott Laird [EMAIL PROTECTED] wrote:
Oct 20 12:50:54 fs2 ahci: [ID 632458 kern.warning] WARNING:
ahci_port_reset: port 1 the device hardware has been initialized and
the power-up diagnostics failed
IIRC, Gigabyte cheaped out and didn't implement SMART. Thus,
everything that tries
I'm debating using an external intent log on a new box that I'm about
to start working on, and I have a few questions.
1. If I use an external log initially and decide that it was a
mistake, is there a way to move back to the internal log without
rebuilding the entire pool?
2. What happens if
Scott Laird wrote:
I'm debating using an external intent log on a new box that I'm about
to start working on, and I have a few questions.
1. If I use an external log initially and decide that it was a
mistake, is there a way to move back to the internal log without
rebuilding the entire
On 10/18/07, Neil Perrin [EMAIL PROTECTED] wrote:
Scott Laird wrote:
I'm debating using an external intent log on a new box that I'm about
to start working on, and I have a few questions.
1. If I use an external log initially and decide that it was a
mistake, is there a way to move
Scott Laird wrote:
On 10/18/07, Neil Perrin [EMAIL PROTECTED] wrote:
Scott Laird wrote:
I'm debating using an external intent log on a new box that I'm about
to start working on, and I have a few questions.
1. If I use an external log initially and decide that it was a
mistake, is there
On 10/18/07, Neil Perrin [EMAIL PROTECTED] wrote:
So, the only way to lose transactions would be a crash or power loss,
leaving outstanding transactions in the log, followed by the log
device failing to start up on reboot? I assume that that would that
be handled relatively cleanly (files
On Thu, Oct 18, 2007 at 02:29:27PM -0600, Neil Perrin wrote:
So, the only way to lose transactions would be a crash or power loss,
leaving outstanding transactions in the log, followed by the log
device failing to start up on reboot? I assume that that would that
be handled relatively
Scott Laird wrote:
On 10/18/07, Neil Perrin [EMAIL PROTECTED] wrote:
So, the only way to lose transactions would be a crash or power loss,
leaving outstanding transactions in the log, followed by the log
device failing to start up on reboot? I assume that that would that
be handled
10 matches
Mail list logo
