The following patch to 1.4.10 has been running on our production
fileservers now for 7 days, both namei and inode. Not a single volume
offline issue during this interval.
STABLE14-background-fsync-consistency-issues-20090522
-- David Boldt
<[email protected]>
"The reverse side also has a reverse side."
--Japanese Proverb
From:
David R Boldt <[email protected]>
To:
"Bryan Howard" <[email protected]>
Cc:
[email protected]
Date:
05/15/2009 02:09 PM
Subject:
Re: [OpenAFS] solaris 10 versions supporting inode fileservers
Sent by:
[email protected]
"oops"; yes!
From:
"Bryan Howard" <[email protected]>
To:
"David R Boldt" <[email protected]>
Cc:
[email protected]
Date:
05/15/2009 01:01 PM
Subject:
Re: [OpenAFS] solaris 10 versions supporting inode fileservers
David R Boldt wrote:
>> > Both of the volumes most frequently impacted have content
>> > completely rewritten roughly every 20 minutes while being on
>> > an automated replication schedule of 15 minutes. One of them
>> > 25MB, the other 95MB, both at about 80% quota.
>>
>> How log does the replication take?
>
> We replicate to California, South Dakota and Virginia, averaging
> 18MB/Min (empirically determined replication velocity).
> So about 65 sec and 155 sec, respectively.
David, something doesn't add up there. Shouldn't that be
about 65 sec and 255 sec respectively?
{Bryan}
