Displaying 20 results from an estimated 820 matches for "resynced".
Did you mean:
desynced
2004 Aug 06
2
bitstream problem: resyncing...
This one really has me stumped.
I'm running 866MHz, 256MB RAM, 80GB Disk (7200RPM) on Linux-mandrake 8.2
icecast 1.3.12 & ices 0.2.3 & lame 3.91
all mp3s encoded with lame 3.91 or higher and --r3mix (VBR)
Sorry for the long email but I'm hoping to get someone out there that's seen
this before and give me some advice...
I'm continually getting errors like this when running
2009 May 08
3
Software RAID resync
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
2009 Jun 21
1
domU shutdown with cx88 crashes dom0
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
2005 Oct 12
0
Zaptel Debug: "T1: Lost our place, resyncing "
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
2010 Mar 04
1
Resync raid1 from disk with unreadable sectors
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
2006 Feb 20
9
Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
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.
2018 Sep 12
1
Adding namespace alias_for causes index resync?
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
2007 Dec 18
2
resync linksys SPA9XX config file from Asterisk
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
2010 Apr 12
1
How long will CENTOS 4.X automatic resync to to time server???
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
2005 Jan 05
1
Resyncing cut streams...
I'm interested to know of any player, which can properly resync after
receiving a theora+vorbis stream that has been cut somewhere in the
middle... ie it doesn't start at granule 0.
The problem being... when streams are cut in this way, the start time, and
the times of the first few packets in each stream are unknown. When working
at a packet level... the first few packets will arrive
2010 May 13
1
raid resync speed?
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
2005 Oct 11
3
Asterisk and Mitel SX 200 Slip and Frame Err ors causing Major Ala rms
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
2012 Jan 02
0
raid resync deleting data?
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
2012 May 26
1
Crash on force-resync if / is given as mailbox name
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:
2012 Jan 31
1
force-resync fails to recover all messages in mdbox
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
2018 Nov 06
2
Time server on AD DC in an LXD container.
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.
>
>
2016 Jun 13
1
Slow RAID Check/high %iowait during check after updgrade from CentOS 6.5 -> CentOS 7.2
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
2015 Mar 13
1
How to detect out-of-sync condition
...9;s sieve filter.
Then I'm not sure how mailboxes ever get out of sync.
> So it looks like I need to compare the index/mailbox mtimes as you suggest.
>
> What am I looking for?
> I see that the indexes are updated when I run the resync.
>
> I checked my mailbox (that was not resynced) and noticed that
> dovecot.index last update was 16 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...
2019 Jul 25
2
corrupt mdbox index / zero mails showing in imap
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
2023 Jan 12
2
Upgrading system from non-RAID to RAID1
> Hallo Simon,
>
>> Anyway, the splitting of large disks has additional advantages. Think of
>> what happens in case of a failure (power loss, kernel crash...). With
>> the
>> disk as one large chunk, the whole disk has to be resynced on restart
>> while with smaller segments only those which are marked as dirty have to
>> be resynced. This can make a bit difference.
>
> I am not sure if this is true. If a underlying disk fails, it will mark
> all partitions on that disk as dirty, so you will have to resync...