search for: resyncing

...DEBUG: Bitrate: 128 kbit/s Padding: 0 Mode: j-stereo DEBUG: Ext: 0 Mode_Ext: 2 Copyright: 0 Original: 1 DEBUG: Error Protection: 0 Emphasis: 0 Stereo: 2 Playing /home/audiotron/music/Beck/Odelay/09-Minus.mp3 DEBUG: Initially delaying metadata update... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstream problem: resyncing... bitstrea...

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

Hi, I've got a big problem with a cx88 DVB card. It is passed through to a CentOS 5.3 domU (dom0 is CentOS 5.3 as well), but when I shutdown the domU, this happens: cx88[0]: mpeg risc op code error cx88[0]: mpeg - dma channel status dump cx88[0]: cmds: initial risc: 0xffffffff cx88[0]: cmds: cdt base : 0xffffffff cx88[0]: cmds: cdt size : 0xffffffff cx88[0]: cmds: iq base

We are trying to debug a connection between Asterisk and a legacy PBX (Mitel SX200). We turned on the Zaptel debugging and we get the following message quite frequently: Oct 12 07:14:09 localhost kernel: T1: Lost our place, resyncing ( 28 ) Oct 12 07:14:09 localhost last message repeated 3 times -- Oct 12 07:14:11 localhost kernel: T1: Lost our place, resyncing ( 28 ) Oct 12 07:14:11 localhost last message repeated 7 times -- Oct 12 07:14:15 localhost kernel: T1: Lost our place, resyncing ( 28 ) Oct 12 07:14:15 localhost last m...

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 was using G729 with Asterisk 1.07. With the new ability to do packet loss correction with ILBC, I felt I'd give it a try. The new PLC does not work with G729. I don't use Speex because my softphone does not support it. This is a 1.5mb IP-VPN connection with prioritized QOS for port 4569 (IAX2). I've never really stressed the bandwidth. Typically, only 10-20 concurrent calls.

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

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

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

...and then jam all the collected data (ie 1+ seconds of raw audio and video) out in one big chunk. All of which are poor solutions. The other issue is, how are we supposed to tell the difference between a file of this kind that really does intend for there to be a wait time at the start (ie for resyncing, where the video may really not be intended to start for some amount of time to compensate for the different granularitys of the audio and video), and one which looks idenical but expects us to treat the start as really being the start regardless of the granule pos. I'm starting to think t...

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

Eric "ManxPower" Wieling wrote: >> >>> span=1,1,0,d4,ami >>> e&m=1-24 >>> > > Looks like you have told Asterisk to get it's timing from the Mitel. > I'll bet the Mitel is trying to get it's timing from Asterisk. > > Try span=1,0,0,d4,ami and run ztcfg -vvv > I just set this back. It was originally set to your

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

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:

I noticed a problem with time synchronization on all Windows endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. When I run the following command in Windows: w32tm /monitor dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: ICMP: 1ms delay NTP: +0.0000000s offset from dc1.xxxx.pl RefID: time.cloudflare.com [162.159.200.123] Stratum: 4 dc2.xxxx.pl[192.168.45.9:123]: ICMP: 1ms delay NTP: -0.0001207s

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

Further investigations reveal: --- C:\WINDOWS\system32> w32tm /monitor GetDcList failed with error code: 0x800706BA. Exiting with error 0x800706BA --- error 0x800706BA indicates that the RPC server is unavailable. Any ideas? Thanks, Jonathan Kreider On Tue, Nov 6, 2018 at 5:48 PM Jonathan Kreider <jonathan.kreider at gmail.com> wrote: > > Thanks Robert & Marco. > >

On 2016-06-01 20:07, Kelly Lesperance wrote: > Software RAID 10. Servers are HP DL380 Gen 8s, with 12x4 TB 7200 RPM drives. > > On 2016-06-01, 3:52 PM, "centos-bounces at centos.org on behalf of m.roth at 5-cent.us" <centos-bounces at centos.org on behalf of m.roth at 5-cent.us> wrote: > > >Kelly Lesperance wrote: > >> I did some additional testing - I

...days ago. Just to be clear, you're talking "doveadm index ...", yes? You might have to check dovecot.index.log* as well as they could contain the latest changes that have yet to propagate to the main index file. http://wiki2.dovecot.org/Design/Indexes/TransactionLog > So am I resyncing if the gap is over x days? > If so, is there a way to resync just those mailboxes with a doveadm > command or do I have to write a program look for that condition and run > doveadm when matched? It's possible that "doveadm index" checks modification times as an optimization...

Hi, I have recently migrated (under emergency conditions) a dovecot imap/pop based server to a new instance. The mailboxes used mdbox format and due to various screwups I had corrupt indexes. I thought I'd cleaned this up but then I found that this new instance hadn't been set up correctly for nfs. Long story short, I still get users with new cases of corrupt indexes. The symptom is imap