similar to: Next onnv-gate resync & alpha release binaries.

Author: Darren Moffat <darrenm at opensolaris.org> Repository: /hg/zfs-crypto/gate Latest revision: 9bb308a0778101fcef9ff65336bcec8e68a7bd06 Total changesets: 40 Log message: resynv onnv-gate Files: .hgtags deleted_files/usr/src/cmd/fps/Makefile.inc deleted_files/usr/src/cmd/fps/Makefile.subdirs deleted_files/usr/src/common/crypto/aes/aes_cbc_crypt.c

Author: Darren Moffat <darrenm at opensolaris.org> Repository: /hg/zfs-crypto/zfs-crypto-gate Latest revision: f2267f9eb807cc96d0d8ed72b186a4fae3490010 Total changesets: 1 Log message: merge with zfs-crypto-gate Files: delete: usr/src/lib/libcryptoutil/common/mechkeygen.c

Author: Darren Moffat <Darren.Moffat at Sun.COM> Repository: /hg/zfs-crypto/gate Latest revision: 957d30a3607ed9f3cbe490da5894d1e1b2104033 Total changesets: 28 Log message: resync onnv_105 partial for 6713916 Files: usr/src/Makefile.lint usr/src/Targetdirs usr/src/cmd/Makefile usr/src/cmd/Makefile.cmd usr/src/cmd/acctadm/Makefile usr/src/cmd/acctadm/acctadm.xcl

I''m pleased to announce that the ZFS Crypto project now has Alpha release binaries that you can download and try. Currently we only have x86/x64 binaries available, SPARC will be available shortly. Information on the Alpha release of ZFS Crypto and links for downloading the binaries is here: http://opensolaris.org/os/project/zfs-crypto/phase1/alpha/ Please pay particular note to

First let me say I''m deeply sorry for the mail storm that seeding the new hg/zfs-crypto/gate repository caused. An explanation of what happened and why can be found on my blog: http://blogs.sun.com/darren/entry/sorry_mercurial_hg_push_oops There is also a discussion going on in the tools community on how to ensure this doesn''t happen again:

Hello, After some fiddling with the server now I have broken RAID1 with the "current" mirror on the disk with few unreadable sectors. If I try to re-add other disk to the mirror resync goes till those bad sectors and then starts from the beginning. And so on. Is it possible to somehow force resync to continue even after errors? Manual resync with dd would require a bit too long

I have configured 2x 500G sata HDD as Software RAID1 with three partitions md0,md1 and md2 with md2 as 400+ gigs Now it is almost 36 hours the status is cat /proc/mdstat Personalities : [raid1] md0 : active raid1 hdb1[1] hda1[0] 104320 blocks [2/2] [UU] resync=DELAYED md1 : active raid1 hdb2[1] hda2[0] 4096448 blocks [2/2] [UU] resync=DELAYED md2 : active raid1

Hello, I have a c5 box with a 6 drive raid 6 array. I was going away over Christmas so I was shutting the machine down, I noticed a raid resync (on the raid 6 array) so i stopped it, using the command # echo "idle" > /sys/block/md5/md/sync_action then shut the machine down. A week later I turned the machine on and started copying data to it around 24 hours later a raid resync

To my understanding, when using mdbox, doveadm force-resync should be able to recover all the messages from the storage files alone, though of course losing all metadata except the initial delivery folder. However, this does not seem to be the case. For me, force-resync creates only partial indices that lose messages. The message contents are of course still in the storage files, but dovecot just

We have several CENTOS 4 and 5 servers. ALL CENTOS servers have NTP setup to sync time server. Several days ago due to power outage all servers are reboot. Due to DNS server did NOT up quickly, CENTOS servers start up and can NOT find time server. For CENTOS 5.X servers, it did quickly resync to time server after 30 minutes. For CENTOS 4.X servers, it have been 3 days still NOT sync to time

Has anything changed in updates that would affect md raid1 resync speed? I regularly swap a 750G drive and resync to keep an offsite copy and haven't paid enough attention to known when things changed but it seems to take much longer to sync than it did months ago, even if I unmount the partition and stop most other processes that might compete with it. -- Les Mikesell

Hi, when I specify a slash a mailbox name on the command line of doveadm force-resync, it throws a panic. I'm not sure this is considered a bug. mail01:~# doveadm force-resync -u user1 at example.org / doveadm(user1 at example.org): Panic: file mailbox-list-fs.c: line 150 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) doveadm(user1 at example.org): Error:

Hi, I am seeing inconsistencies in search results (finding 2 emails when only 1 exists, finding the email when it has been moved to another folder, etc). I figured I should run force-resync to fix any issues. I ran the following: doveadm -v force-resync -u <user> <mailbox> and I got some worrysome logs. - I should mention that I have been seeing some crashes of fts-lucene in my

Author: Darren Moffat <Darren.Moffat at Sun.COM> Repository: /hg/zfs-crypto/gate Latest revision: 32a041998ab168dc335d487020fc0cb59c85d81f Total changesets: 1 Log message: 6745678 zio->io_checksum == ZIO_CHECKSUM_SHA256_CCM_MAC (0x5 == 0x9), file: zio.c, line: 1498 Files: update: usr/src/uts/common/fs/zfs/zio.c

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

Hello. If running dovadm replicator status, i get something like the following. root at mail2:~# doveadm replicator status Queued 'sync' requests??????? 0 Queued 'high' requests??????? 0 Queued 'low' requests???????? 0 Queued 'failed' requests????? 0 Queued 'full resync' requests 4 Waiting 'failed' requests???? 0 Total number of known users? 1000

OK todays problem. I have a HP N54L Microserver running centos 6.5. In this box I have a 3x2TB disk raid 5 array, which I am in the process of extending to a 4x2TB raid 5 array. I've added the new disk --> mdadm --add /dev/md0 /dev/sdb And grown the array --> mdadm --grow /dev/md0 --raid-devices=4 Now the problem the resync speed is v slow, it refuses to rise above 5MB, in general

Hi All, Anyone know the sip header to send to a Linksys to resync it's config file? Thanks. JR -- JR Richardson Engineering for the Masses

Hi list, I am using dovecot 2.2.27 (c0f36b0) on two servers with (dovecot) replication between them. I do not use dovecot-directors or -proxies. I just have a floating IP on the servers to do failover. I had the problem today that in one user's INBOX and one if his mailfolders got flooded with hundreds of thousands of duplicates. How this happened is another issue (of someone has an idea it

Dear Colleagues, All of a sudden, I've begun receiving this output when reindexing my mail boxes: # /usr/local/bin/doveadm force-resync -u vas "*" doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/sent/dovecot.index.log was locked for 55 seconds (Mailbox was synchronized) doveadm(vas): Warning: Transaction log file