similar to: Stale CVS locks removed

I am having a problem that I have seen described in various bug reports.. One filed bug (#1267) was supposed to have been fixed in 3.0.7 but this problem is still existing in 3.0.10 from what I can tell. Here's what I see: mercury:/root# smbstatus -LB ----------8<----------<SNIP>----------8<---------- Byte range locks: Pid dev:inode R/W start size

Hello Timo, I'm running dovecot-1.0.rc15 (imap and pop) postfix-2.3.5,1 procmail-3.22_6 (which is my LDA) on FreeBSD 6.1-STABLE I'm still using the mbox format (I'm planning to migrate to Maildir soon), mailboxes are on an NFS filesystem. I regulary see stale dotlocks files (either from dovecot (29 bytes, hold the pid of the process) or procmail (1 byte) and processes

Go monty! jack. ----- To: cvs@xiph.org Subject: [xiph-cvs] cvs commit: vorbis/vq huffbuild.c latticetune.c make_residue_books.pl Date: Sun, 3 Jun 2001 22:50:13 -0700 (PDT) From: xiphmont@xiph.org (Monty) Precedence: bulk Reply-To: cvs@xiph.org xiphmont 01/06/03 22:50:12 Modified: lib codebook.c codebook.h floor0.c mapping0.c os.h res0.c vq

Greetings dovecot mailing list. I have implemented a relatively big dovecot setup (250k users) and overall I am very pleased with dovecot functionality and performance. Setup description: * dovecot 1.0.x * FreeBSD 6.3 * Postfix (using dovecot deliver as LDA). * OpenLdap backend * Storage is NFS (Clariion EMC NFSd for Maildir, and FreeBSD NFSd for Indexes). * Locking is fcntl using

Because my primary server went down today, I have a couple of servers that have 'stale NFS mounts' which I can't unmount... # umount /home/storage/users umount: /home/storage/users: device is busy umount: /home/storage/users: device is busy short of restarting...is there a trick that I can do to umount/remount? Craig

We're there. The decode engine with all 1.0 features is finished and in CVS, tagged as release candidate 1. CVS mainline head and the current nightly snapshot will get you the latest and greatest. Next, we continue work toward rc1 of the encode side. Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this

We're there. The decode engine with all 1.0 features is finished and in CVS, tagged as release candidate 1. CVS mainline head and the current nightly snapshot will get you the latest and greatest. Next, we continue work toward rc1 of the encode side. Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this

Hi all, I haven't found any root cause or workaround for this yet. Can any one help me in underatanding the issue? Regards, Jeevan. On Dec 21, 2017 8:20 PM, "Jeevan Patnaik" <g1patnaik at gmail.com> wrote: > Hi, > > > After running rm -rf on a directory, the files under it got deleted, but > the directory was not deleted and was showing stale file handle

An ESTALE error usually means the gfid could not be found. Does repeating the "rm -rf" delete the directory? Regards, Nithya On 3 January 2018 at 12:16, Jeevan Patnaik <g1patnaik at gmail.com> wrote: > Hi all, > > I haven't found any root cause or workaround for this yet. Can any one > help me in underatanding the issue? > > Regards, > Jeevan. > >

Hi, After running rm -rf on a directory, the files under it got deleted, but the directory was not deleted and was showing stale file handle error. After 18 minutes, I'm able to delete the directory. So could anyone help me in knowing what could have happened or when in general I get such errors. The following is NFS log: [2017-12-21 13:56:01.592256] I [MSGID: 108019]

We're in the process of moving some xiph.org machines around, and for that reason there will be a brief actual outage of Mail, WWW and CVS today. However, the main DNS is also moving to a new IP address, and that will take some time to propogate (the TTL is cranked way down, so the limiting factor is probably the next Internic a.root update). For that reason, xiph.org will not resolve from

We're in the process of moving some xiph.org machines around, and for that reason there will be a brief actual outage of Mail, WWW and CVS today. However, the main DNS is also moving to a new IP address, and that will take some time to propogate (the TTL is cranked way down, so the limiting factor is probably the next Internic a.root update). For that reason, xiph.org will not resolve from

Motherfish.xiph.org, the main CVS and web server, suffered filesystem corruption in the past few days and was oopsing on some CVS operations and mail archive searches. Earlier today I took the box down and ran four hours of diagnostics; nothing unusual found. It's possible there was a media error in swap, the box got hit by a brownout, whatever. I'll be keeping an eye on it. The root

Motherfish.xiph.org, the main CVS and web server, suffered filesystem corruption in the past few days and was oopsing on some CVS operations and mail archive searches. Earlier today I took the box down and ran four hours of diagnostics; nothing unusual found. It's possible there was a media error in swap, the box got hit by a brownout, whatever. I'll be keeping an eye on it. The root

Hi, sorry, I was on vacation and just found it in my inbox again. > Am 25.09.2023 um 23:32 schrieb Strahil Nikolov <hunter86_bg at yahoo.com>: > > Hi, > > I found this one in my spam folder and ai can?t find any follow up communication. > Have you found the problem ? Sort of. I just recognized that the volume stops syncing completely while my other volume just did

I am running an older version of nut (2.0.2) on a FreeBSD 4.11 machine. This has been running fine for many months until the last few weeks. It seems that several times a week the machine is shutting itself down. Looking at the log files I notice these lines which lead me to think there is something wrong with the serial communication betwen my host and the Ellipse 600 UPS. Jan 5 04:49:02

Yes. I am one of them. ---Aki TuomiDovecot oy -------- Original message --------From: Raffaele Gambelli <R.Gambelli at hitachi-systems-cbt.com> Date: 23/02/2018 12:25 (GMT+02:00) To: dovecot at dovecot.org Subject: Re: Stale mailbox lock file Thanks Aki, do you know if this list is read by dovecot developers team too? Could you point me to the right list otherwise? Raffaele Gambelli

Today, rsyncd manages its pid file by open()ing it with O_CREAT|O_EXCL at startup, and then unlink()ing it at shutdown. If the open() fails at startup because the file already exists, then rsyncd will assume another instance of itself is already running and not start. However, there's a problem with this approach: if rsyncd is terminated without being able to clean up (e.g., kill -9, or the

Hi all, I've had just a couple instances so far where a user has closed a file, but fuser still reports it open, and when I look at the pid it reports, it's a smbd process. If I kill the process, other users can open the file. Is there a way that I can debug why this is happening? Samba 3.0.9 with ext3 filesystem underlying. Thanks for any ideas, as this is one of those things

<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> <div>Thanks but what answer it mean "<span style="font-size: 12.8px;">doveconf -n"? </span> </div><div><span style="font-size: 12.8px;">I have neither control nor access in the dovecot installation to which I'm