search for: empty_dir

Index: namei.c =================================================================== --- namei.c (revision 968) +++ namei.c (working copy) @@ -526,7 +526,7 @@ status = -EBUSY; - if (!empty_dir(inode)) { + if ( S_ISDIR (inode->i_mode) && !empty_dir(inode)) { LOG_TRACE_STR ("dentry is not empty, cannot delete"); goto bail; } else if (OCFS_I(inode)->open_hndl_cnt > 0) { bug 81 description: Env: kernel 2.4.20 Dell...

An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20101031/bb482d8d/attachment.html>

...arents(set->state_dir, 0755) < 0 && errno != EEXIST) i_fatal("mkdir(%s) failed: %m", set->state_dir); mkdir_login_dir(set, t_strconcat(set->base_dir, "/login", NULL)); mkdir_login_dir(set, t_strconcat(set->base_dir, "/token-login", NULL)); empty_dir = t_strconcat(set->base_dir, "/empty", NULL); if (safe_mkdir(empty_dir, 0755, master_uid, getegid()) == 0) { i_warning("Corrected permissions for empty directory " "%s", empty_dir); } Granted this is from a pretty quick browsing of the sources but I couldn...

...en=5EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 56037886 EXT3-fs error (device sd(8,49)): ext3_readdir: bad entry in directory #2933557: directory entry across blocks - offset=0, inode=1986311577, rec_len=30216, name_len=5 EXT3-fs warning (device sd(8,49)): empty_dir: bad directory (dir #2933557) - no `.' or `..' EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 4466464 EXT3-fs warning (device sd(8,49)): empty_dir: bad directory (dir #2933557) - no `.' or `..' EXT3-fs warning (device sd(8,49)): ext3_free_block...

Hi Folks, We can see these massages on our MDS Feb 12 12:46:08 mds01 kernel: LDISKFS-fs warning (device dm-0): empty_dir: bad directory (dir #31452569) - no `.'' or `..'' Feb 12 12:46:08 mds01 kernel: LDISKFS-fs warning (device dm-0): ldiskfs_rmdir: empty directory has too many links (3) It seem to indicate that we have bad(corrupted) directory. Do you have any idea how to find out which dir is t...

Hi, all I?m new to the list but not to dovecot. I?ve been using it in a basic configuration for some time, but finally decided to tweak my deployed system to take advantage of some more dovecot features. In particular I?m trying to set up pigeonhole to implement spam retraining with imapsieve. All of this is with dovecot 2.2.31 (65cde28) and pigeonhole 0.4.19. Before going any further let me

...t=0, inode=1886221359, rec_len=24927, name_len=109 May 21 14:07:23 glass kernel: EXT3-fs error (device md(9,0)): ext3_readdir: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927, name_len=109 May 21 14:07:23 glass kernel: EXT3-fs warning (device md(9,0)): empty_dir: bad directory (dir #2945366) - no `.' or `..' If I hunt down the directory (find . -inum ...) and do an "ls -la", it appears empty and reponds reasonably well to "rmdir". So far the directories have mostly been browers caches, so no real data has been lost (I th...

...de=4288315399, rec_len=65535, name_len=255 Oct 19 17:22:46 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_readdir: bad entry in directory #10125314: rec_len %% 4 != 0 - offset=0, inode=4288315399, rec_len=65535, name_len=255 Oct 19 17:22:46 noname kernel: EXT3-fs warning (device lvm(58,1)): empty_dir: bad directory (dir #10125314) - no `.' or `..' Oct 19 17:22:46 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_free_blocks: Freeing blocks in system zones - Block = 20250624 , count = 1 Oct 19 17:23:52 noname kernel: EXT3-fs error (device lvm(58,1)): ext3_new_block: Allocating block...