similar to: Hardlinking with Sieve

Have a directory with a bunch rpms in it, mostly x86_64. Have another directory with a bunch, mostly 'noarch'. Some of the noarch files are already in the x86_64 dir and don't want to overwrite them. They are on the same physical disk, so really, just want the new 'noarch' files hardlinked into the destination. sitting in the noarch dir, I tried: rsync -auv

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc8.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc8.tar.gz.sig I then decided to add the deliver -c feature to this release. Seems to work in my tests, but who knows if it breaks something.. Although most of the code is called only if -c parameter is given. Anyway we really should have a comprehensive test suite written some day (yes, help

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc8.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc8.tar.gz.sig I then decided to add the deliver -c feature to this release. Seems to work in my tests, but who knows if it breaks something.. Although most of the code is called only if -c parameter is given. Anyway we really should have a comprehensive test suite written some day (yes, help

Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> writes: > Could you try what happens, if you create the hardlink manually as the > vmail user _two_ times, if the first link() succeeds. Maybe: > > 1) hard links won't work on your encfs, > 2) link() fails with "Operation not permitted" instead of "File exists" in > your case, if the target file

Context ------- I am one of the active developers of the open source application "Back in Time" which uses "rsync" as backend and I want to fix an open issue: "Back in Time"-Bug: https://github.com/bit-team/backintime/issues/994#issuecomment-1724211507 "Back in Time" uses "--link-dest" to reduce traffic and storage by hardlinking

Hi, now it's time to come back to this topic. As supposed, the missing hardlinks where no issue of rsync. I am not sure if pairing aufs (http://aufs.sourceforge.net/) and rsync -RH will catch each and every hardlink compared to a single filesystem, but it seems to work very reliable. I tried mhdfs and aufs. Aufs is faster and very stable (I am on wheezy kernel 3.2). So at last I have my

Hi, hardlinking (-H) works perfectly while using a syntax like -avhxSDH <SRC> <DEST> Now I have to mirror multiple SRC directories which contain hardlinks. e. g: src1/a is a hardlink to src2/b -RavhxSDH SRC1 SRC2 DEST does not preserve hardlink a and b in DEST. Is there any chance to do that? Thanks lopiuh -------------- next part -------------- An HTML attachment was scrubbed...

I'm running a mirror of several repositories that are fetched using separate rsync runs. Since some of those repositories are hosting related files, I'm using the hardlink utility[1] in order to save disk space. However, I've noticed an issue that may lead to potential file metadata inconsistencies when using hardlink. Consider the following scenario: - two repositories (rep_a and

On Fri, 2023-09-22 at 07:37 -0400, Kevin Korb wrote: > So I decided to do a quick test using the Linux kernel source tree since > it has lots of files. Excellent idea using kernel sources! A lot of different files... I will use this to create indicative benchmarks for different scenarios... > ? I duplicated a tree, used 'find . -type f -exec > chmod 444 {} +' to make read

Hi, Recently I gzipped mails older than 30 days in our users' maildirs. I used find and gzip. Gzip added 'Z' at the end of the filename and everything seemed to work fine, users did not notice any difference in performance (yet :-), and I saved about 30% of our mail storage space. There seems to be a problem when moving gzipped messages from one folder to another though. Dovecot

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz.sig Not many bug reports these last few days, so maybe this release will be a good one. + Maildir: When hardlink-copying a file, copy the W=<vsize> in the filename if it exists in the original filename. - mbox: With rc8 empty lines were inserted in the middle of saved

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc9.tar.gz.sig Not many bug reports these last few days, so maybe this release will be a good one. + Maildir: When hardlink-copying a file, copy the W=<vsize> in the filename if it exists in the original filename. - mbox: With rc8 empty lines were inserted in the middle of saved

Hello, I'm trying to enable hardlinks for messages sent to mutiple users. (I need this because I have mailing lists with 5000 users used many times a day). I've read that, to do this, I have to write a script that uses the /usr/local/libexec/dovecot/deliver command in this way: deliver -p <FILE> -d <USER1> -d <USER2> Of course, I enabled the "socket listen"

We have a few users that every so often get empty data in their message overview. From and subject are empty, and the date is 1-Jan-1970. When opening the message in full view, all things are fine. Also, the data in the actual maildir file is fine. It looks a lot like the issue described here: http://dovecot.org/list/dovecot/2008-March/029282.html The server is Linux, ext3, no NFS, and Dovecot

Dovecot (v1.1.rc8) died tonight, with an error about time moving backwards by 4398 seconds. I can see from logs that this has happend a few times before with the imap processes, without me noticing. I sure noticed the master process missing, though :-). I was puzzled that it was always 4398 seconds, in particular because this server runs an NTP daemon. A little searching for this problem shows

Hi, I'm trying to get the so-called "single instance store" (I think cyrus has got the name for the first time) with dovecot --version = 2.0.19 binary package installed from ubuntu 12.04 lts official repo. I have checked that "maildir_copy_with_hardlinks" is enabled ("dovecot -a|grep hard" shows "yes") then I have installed and enabled the lmtp

In working on trying to fix the crash issue from my last email I had enabled LMTP delivery to try it out instead of using the LDA. I have discovered that when a single piece of email is to be delivered to multiple users the message is being hard linked instead of copied into each mail box. This is a major problem that makes LMTP unusable in an environment where each mailbox has it's own UID

The maildirsize file is double counting messages when moving them from folder to folder when "maildir_copy_with_hardlinks = no": 1024000000000S 99337571 19370 14010590 2 <--- moved from subfolder to subfolder -7005295 -1 14010590 2 <--- moved from subfolder to INBOX -7005295 -1 14010590 2 <--- moved from INBOX to subfolder -7005295 -1 14010590 2 <---

OK, I solved it all ( so far :) ), mixing in some load-instructions and called on the result of that, which worked. Here is the skeleton-code: %kernel = type { int ()* } int puts_kernel(){...} ; main() %theKernel = malloc %kernel %puts_kernelPTR = getelementptr %kernel* %theKernel, long 1, ubyte 0 store int ()* %puts_kernel, int ()** %puts_kernelPTR %tmp.11 = load int ()** %puts_kernelPTR

http://dovecot.org/tmp/deliver-multiple.diff for Dovecot v1.1 implements -p <path> parameter for deliver, which reads the input mail from the specified path instead of stdin. With maildir and hardlink copying enabled, it also tries to hard link the file to destination instead of copying it. So to get the same mail delivered to multiple recipients using hard links, you'd have to write a