search for: scari

Hi, I tried to backup my gentoobox using rsync into a NTFS External Drive Rsync Failed And now there is no space lesft on my root directory "/" and kcore file size is 128 TiB and my External NTFS HDD makes scary sounds (Like it is working hardly) even when its not mounted rsync created some files/directories that i cant remove them on my External HDD using "rm -rf" , Please

If your hard disk is making scary noises that could be the drive starting to fail have you tried to determine if the drive is still good or on the way out? On Thu, Apr 30, 2015 at 2:12 AM, Kezhawe <kezhawe28 at gmail.com> wrote: > Hi, > > I tried to backup my gentoobox using rsync into a NTFS External Drive > Rsync Failed And now there is no space lesft on my root directory

I can still read&write on the external hdd and on my laptop (which I have my gentoo there) I can't do anything on / because its filled up with /proc/kcore after "rsync failed" rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} /*

I'm still working on figuring out why some accesses to profile data are failing. We are running 3.3.2-0.33.fc11 (the latest release for FC11). I saw this in the log file stat_cache_lookup: lookup succeeded for name [USER/STARTMENU] -> [user/StartMenu] [2009/07/08 17:39:59, 3] locking/locking.c:fetch_share_mode_unlocked(857) fill_share_mode_lock failed I saw Volker had a fix

http://bugs.freedesktop.org/show_bug.cgi?id=16269 Summary: NV47 DVI DPMS scary loop Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: vallesroc

Hi, Checking in - this is still an issue with 2.3-master as of today (2.3.devel (3a6537d59)). I haven't been able to narrow the problem down to a specific commit. The best I have been able to get to is that this commit is relatively good (not perfect but good enough): d9a1a7cbec19f4c6a47add47688351f8c3a0e372 (from Feb 19, 2018) whereas this commit:

> On 31 May 2018, at 17:52, Michael Grimm <trashcan at ellael.org> wrote: > > Reuben Farrelly <reuben-dovecot at reub.net> wrote: > >> Checking in - this is still an issue with 2.3-master as of today (2.3.devel (3a6537d59)). > > That doesn't sound good, because I did hope that someone has been working on this issue ... > >> I haven't been

On 1/06/2018 2:47 AM, Michael Grimm wrote: > On 31. May 2018, at 18:09, Remko Lodder <remko at FreeBSD.org> wrote: >>> On 31 May 2018, at 17:52, Michael Grimm <trashcan at ellael.org> wrote: >>> I would love to get some feedback from the developers regarding: >>> >>> #) are commercial customers of yours running 2.3 master-master replication

Hi Timo, Yes this seems to work fine so far. I?ll ask the people to add it to the current FreeBSD version.. Cheers Remko > On 6 Jun 2018, at 19:34, Timo Sirainen <tss at iki.fi> wrote: > > Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 <https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336> >

Aaaaand I forgot to CC the list, sorry for that, it's way too early in the morning :P On 07.06.18 - 07:39, Thore B?decker wrote: > What does the output of these two commands show after that error has > been logged? > > doveadm replicator status > > doveadm replicator dsync-status > > If there are *waiting failed* requests, that never make it "through" >

> On 7 Jun 2018, at 07:21, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > Still not quite right for me. > > Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) > Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout during

Am 2018-06-07 08:48, schrieb Remko Lodder: > On Thu, Jun 07, 2018 at 08:04:49AM +0200, Michael Grimm wrote: >> Conclusion: After 12 hours of running a patched FBSD port I do get >> those >> error messages but replictaion seems to work now. But, I still have >> the >> feeling that there might something else going wrong. > > I agree with that. Are you using

Timo Sirainen: > Should be fixed by > https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 please ignore my ignorance but shouldn't one add this commit regarding src/doveadm/client-connection-tcp.c ... https://github.com/dovecot/core/commit/2a3b7083ce4e62a8bd836f9983b223e98e9bc157 ... to a vanilla 2.3.1 source tree as well? I do have to admit that I am

I have a zfs dataset that I use for network home directories. The box is running 2008.11 with the auto-snapshot service enabled. To help debug some mysterious file deletion issues, I''ve enabled nfs logging (all my clients are NFSv3 Linux boxes). I keep seeing lines like this in the nfslog: <br> <br> <pre> Wed Aug 19 10:20:48 2009 0 host.name.domain.com 1168

i got this link from another list. does this affect applications running in wine? http://security.tombom.co.uk/shatter.html -- Oh, I have slipped the surly bonds of DOS, and danced the skies on Linux silvered wings. http://pfrostie.freeservers.com/cad-tastrafy/ http://www.freelists.org/list/cad-linux

It is listed as a known issue, but I have a lot of 256Mb systems where I have used the graphic installer.... OUCH! And when this is fixed (I really hope), it will mean some new ISOs to download?

Hi, Yesterday I updated asterisk to the latest zaptel driver and today my congestion problems are gone... (see http://bugs.digium.com/view.php?id=6509), only to be replaced by: Feb 17 10:02:37 DEBUG[19225] chan_zap.c: Write returned -1 (Resource temporarily unavailable) on channel 26 Feb 17 10:03:08 DEBUG[19274] chan_zap.c: Write returned -1 (Resource temporarily unavailable) on channel 216 Feb

Hey all, almost 48h ago I upgraded both my instances to 2.3.1 again to see if the new patches would fix the replication issues for me. So far, the result is: great. I haven't been able to provoke any kind of I/O stall or persisting queued/failed resync requests in my replication setup. Newly added users are replicated instantly upon the first received mails and the home directory gets

Hi [This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at distinct servers.] I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error messages at server1 (and vice versa at server2) as follows: | Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ no activity for 600 seconds (last sent=mail_change, last

Hi, We at Rust are using LLVM for our codegen. Since Rust version 1.19.0, which should ship in July 21st, we are using a slightly patched version of LLVM 4.0. The transition to LLVM 4.0 had been fairly pain-free on x86 (at least excluding the standard suite of assertion failures using MSVC SEH, but that's fairly under control), but we have encountered several scary bugs in ARM, most