search for: new_dir

This patch series allows user-specified mount commands to be sent in via kernel command line ("kinit_mount=...") or via an embedded /etc/fstab file. The first patch is a cleanup of a patch sent last November by San Mehat (http://web.archiveorange.com/archive/v/EazJNBMORV2U7E0coh5h); the next two are small improvements or bug fixes.

Hi Linus, Here are some 2.6.20 fixes for ocfs2. The patch by Zhen Wei isn't really a fix, but a very small amount of support for a feature which is mostly implemented in ocfs2-tools. Considering it's just a single attribute export via configfs, I'd say it's pretty safe to merge. Please pull from 'upstream-linus' branch of

Between versions 1.0.4 and 1.0.5 there were some changes to the way dovecot-shared group ownership is propogated into new maildirs. Changing the group of new_dir/{tmp,new,cur} was added, but changing the group of new_dir itself was removed. As far as I can tell, this latter change may have been accidental. This patch puts the functionality back, in the 1.1 tree. ---------------------------------- # HG changeset patch # User Simon Michelson <simon at i...

...n: Linux Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: normalperson@yhbt.net QAContact: rsync-qa@samba.org When renaming $dest_dir to $old_dir, don't say we're renaming $new_dir to $old_dir on errors. --- a/atomic-rsync +++ b/atomic-rsync @@ -48,7 +48,7 @@ if (system($RSYNC_PROG, "--link-dest=$dest_dir", @ARGV)) { exit $?; } -rename($dest_dir, $old_dir) or die "Unable to rename $new_dir to $old_dir: $!"; +rename($dest_dir, $old_dir) or die &quot...

...I am not able to solve by my own: Before I am doing the backup I am checkig if there are any changes to backup ... rsync --delete $RSYNC_EXCLUDE -avzne "$RSYNC_SSH" $RSYNC_SOURCE $RSYNC_DESTINATION But when I have created a path of new directories in $RSYNC_SOURCE e. g. $RSYNC_SOURCE/new_dir/new_dir/new.file then its fails with ... skipping daemon-excluded directory "$RSYNC_SOURCE/new_dir/new_dir" *** Skipping any contents from this failed directory *** sent 288255 bytes received 962 bytes 23137.36 bytes/sec total size is 14120423141 speedup is 48822.94 (DRY RUN) rsync...

...w2k and Linux */ import java.util.*; import java.io.*; public class SMBtest { public static void main(String args[]) { String directory = args[0]; File orig_dir = new File(directory); File orig_fl[] = orig_dir.listFiles(); int orig_len = orig_fl.length; int cnt = 0; int er_cnt = 0; do { File new_dir = new File(directory); File new_fl[] = new_dir.listFiles(); int new_len = new_fl.length; cnt ++; if (new_len != orig_len) { er_cnt ++; System.out.print(" new:" + new_len + "!= old:" + orig_len + " "); } new_dir = null; new_fl = nul...

...table tarbal, shouldn't bring here any regression. Also I managed to write test case covering this problem. This file will be attached as the second file. Also I would like to say that the previous patch doesn't work, because it will break recursive scp, for example: > scp -r dir/ host:new_dir/ which is completely valid even if the new_dir doesn't exist. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1142223 -- You are receiving this mail because: You are watching the assignee of the bug.

...ir" (the object that is being renamed), but ext2 does. It looks to me like this is simply an omission of the following little patch from namei.c - Peter - --- fs/ext3/namei.c.orig Mon Mar 19 22:55:03 2001 +++ fs/ext3/namei.c Mon Mar 19 22:53:40 2001 @@ -985,6 +985,13 @@ new_dir->i_version = ++global_event; /* + * Like most other Unix systems, set the ctime for inodes on a + * rename. + */ + old_inode->i_ctime = CURRENT_TIME; + ext3_mark_inode_dirty(old_inode); + + /* * ok, that's it */...

...is not entirely an rsync question. but, it seems the 'crowd' most familiar w/ hard-linking are the rsync crowd. so ... i'm doing rsync + incremental backups to a local drive. the incremental steps, currently, use the rsync REMOTE_DIR OLD_DIR ... time passes ... cp -al OLD_DIR NEW_DIR rsync REMOTE_DIR NEW_DIR approach. all works great. i'd *like* to be able to check my LOCAL (destination) drive for sufficient space b4 doing a backup. question: how does one check "real" available freespace? "real", as in not double-counted hardlinked/shared files....

...vecot-1.1.16/src/lib-storage/index/maildir/maildir-sync.c 2009-05-20 16:42:49.000000000 -0500 +++ dovecot/src/lib-storage/index/maildir/maildir-sync.c 2009-07-07 19:50:37.000000000 -0500 @@ -354,7 +354,8 @@ return -1; } -static int maildir_scan_dir(struct maildir_sync_context *ctx, bool new_dir) +static int maildir_scan_dir(struct maildir_sync_context *ctx, bool new_dir, + bool final) /* APPLE */ { struct mail_storage *storage = &ctx->mbox->storage->storage; const char *path; @@ -486,6 +487,11 @@ } } + /* APPLE - rename can cause readdir to fail with...

...t i; - - for (i = 0; i < nr_dirs; ++i) - free (dirs[i]); - free (dirs); + string_vector_iter (&dirs, (void *) free); + free (dirs.ptr); if (fd >= 0) close (fd); @@ -135,7 +133,6 @@ iso_unload (void) static int iso_config (const char *key, const char *value) { - char **new_dirs; char *dir; if (strcmp (key, "dir") == 0) { @@ -143,15 +140,11 @@ iso_config (const char *key, const char *value) if (dir == NULL) return -1; - new_dirs = realloc (dirs, sizeof (char *) * (nr_dirs + 1)); - if (new_dirs == NULL) { + if (string_vector_append...

Hi, I've run many time e2fsck, but in a special dir ls tells me: ls: r?cksendung-wlan.dvi: No such file or directory ls: baf?g_r?ckmeldung.latex: No such file or directory ls: finpr?f.pdf: No such file or directory $ cat finpr?f.pdf cat: finpr?f.pdf: Datei oder Verzeichnis nicht gefunden I don't know what to do? How can I find the failure? If I cat the files with debugfs, I see the

...if (!bh) goto end_rmdir; @@ -2019,7 +2016,7 @@ handle->h_sync = 1; retval = -ENOENT; - bh = ext3_find_entry (dentry, &de); + bh = ext3_find_entry (dir, &dentry->d_name, &de); if (!bh) goto end_unlink; @@ -2177,7 +2174,7 @@ if (IS_DIRSYNC(old_dir) || IS_DIRSYNC(new_dir)) handle->h_sync = 1; - old_bh = ext3_find_entry (old_dentry, &old_de); + old_bh = ext3_find_entry (old_dir, &old_dentry->d_name, &old_de); /* * Check for inode number is _not_ due to possible IO errors. * We might rmdir the source, keep it as pwd of some process @@...

Hi all, this series removes most users of the write_one_page API. These helpers internally call ->writepage which we are gradually removing from the kernel. Changes since v2: - more minix error handling fixes Changes since v1: - drop the btrfs changes (queue up in the btrfs tree) - drop the finaly move to jfs (can't be done without the btrfs patches) - fix the existing minix code to

Howdy, I have dovecot installed on CentOS (rhel3 clone), and I'm using Dag's dovecot package. I have postfix setup to deliver to Maildir, in /home. The /home volume was formatted with JFS. In this setup, both Outlook and Thunderbird would not show any new mail unless they were completely shutdown and restarted. I have moved /home to an ext3 formatted and all is well. Anyone have

Can someone explain to me what is happening here: ~ $ touch foo ~ $ ln foo bar ~ $ ls foo bar bar foo ~ $ mv foo bar ~ $ ls foo bar bar foo I try to move a file over a hard linked copy of itself and the move fails, but there is no error. Is this the intended behavior? -- Ben Escoto

The following patches implement indexed directory support in Ocfs2, mostly according to the design doc I wrote up a while ago: http://oss.oracle.com/osswiki/OCFS2/DesignDocs/IndexedDirectories The patches have been rebased on top of 2.6.29-rc2. It should be trivial to put them into merge_window. Things are what I'd call complete now. I'd like to get these into the merge_window branch

......done. Loaded symbols for /lib/ld-linux.so.2 Core was generated by `imap'. Program terminated with signal 10, Bus error. #0 mailbox_list_index_sync_write_dir (ctx=0xf75e8, sync_dir=0xf7650, offset_pos=<value optimized out>, partial=true) at mailbox-list-index-sync.c:594 594 new_dir->count = nondeleted_count; (gdb) bt full #0 mailbox_list_index_sync_write_dir (ctx=0xf75e8, sync_dir=0xf7650, offset_pos=<value optimized out>, partial=true) at mailbox-list-index-sync.c:594 dir = <value optimized out> recs = <value optimized out> i = &...

...+ +static void +linuxdisk_unload (void) +{ + size_t i; + + free_virtual_disk (&disk); + + for (i = 0; i < nr_dirs; ++i) + free (dirs[i]); + free (dirs); +} + +static int +linuxdisk_config (const char *key, const char *value) +{ + if (strcmp (key, "dir") == 0) { + char **new_dirs; + char *dir; + + dir = nbdkit_realpath (value); + if (dir == NULL) + return -1; + + new_dirs = realloc (dirs, (nr_dirs+1) * sizeof (char *)); + if (new_dirs == NULL) { + nbdkit_error ("realloc: %m"); + free (dir); + return -1; + } + dirs = new_di...

This was a rather longer trip around the houses than I anticipated! The basic purpose of the patch series is to set $nbdkit_stdio_safe to "0" or "1" in sh and eval plugin scripts. To do that, I ended up adding a nicer way to manipulate environ lists, and to do that, I ended up adding a whole generic vector implementation which is applicable in a lot of different places.