On Thu, Aug 26, 2010 at 05:19:25PM +0200, Eric Luyten wrote:
> Hello,
>
>
> I understand the cyrus.header file is the only irreplacable one, i.e.
> cyrus.index and cyrus.cache can be regenerated using 'reconstruct'
> while cyrus.header, a very small (150 bytes or thereabout) and stable
> file, co
So to my mind, the downside of ZFS flush disable is.
Data on disk may not be as current in the unlikely event
of power outage. In point of fact MOST filesystem do not operate
in journalled data mode anyhow and most people just don't
realize this fact. The default for Linux EXT filesystems
Hello,
I understand the cyrus.header file is the only irreplacable one, i.e.
cyrus.index and cyrus.cache can be regenerated using 'reconstruct'
while cyrus.header, a very small (150 bytes or thereabout) and stable
file, contains some vital mailbox identification data.
I observe a cyrus.header fi
On Tue, August 10, 2010 4:06 pm, Gary Mills wrote:
> On Mon, Aug 09, 2010 at 09:03:44PM +0200, Pascal Gienger wrote:
>
>> Am 09.08.10 19:46, schrieb Vincent Fox:
>>
>>> * Turn off ZFS cache flushing
>>> set zfs:zfs_nocacheflush = 1
>>
>> For hardware (fiberchannel, iSCSI, SSA, ...) arrays with thei
