search for: notify_change

...c9 c0344900 00000400 c02733da cdb21e4c 00000000 c02725c6 d11e0a00 d201ab60 c01672a8 c02733c0 00000118 c02725c6 cdb21e6c 00000000 Call Trace: [<c01179c9>] printk+0x61/0x114 [<c01672a8>] __ext3_std_error+0x30/0x40 [<c0162c0a>] ext3_setattr+0x19a/0x1b0 [<c014b606>] notify_change+0xe6/0x180 [<c013696b>] do_truncate+0x5b/0x78 [<c0142d41>] may_open+0x165/0x17c [<c0143015>] open_namei+0x2bd/0x3d0 [<c013770f>] filp_open+0x3b/0x5c [<c0137a63>] sys_open+0x37/0x78 [<c0108877>] syscall_call+0x7/0xb Code: 80 38 00 74 07 40 4a 83 fa ff 75 f4...

-------------- next part -------------- An embedded message was scrubbed... From: =?iso-8859-1?Q?Pe=F1a=2C_Botp?= <botp at delmonte-phil.com> Subject: tailing error Date: Tue, 9 May 2006 11:21:03 +0800 Size: 1852 Url: http://rubyforge.org/pipermail/win32utils-devel/attachments/20060509/45783cb1/attachment.eml

...<c016aac1>] ext3_mark_inode_dirty+0x18/0x31 [<c017082b>] journal_start+0x7f/0xa9 [<c016ab26>] ext3_dirty_inode+0x4c/0x5f [<c0156c20>] __mark_inode_dirty+0x24/0xce [<c01527d2>] inode_setattr+0x118/0x123 [<c016a951>] ext3_setattr+0xc9/0x104 [<c0152903>] notify_change+0xda/0x143 [<c013c6b9>] sys_utime+0xec/0x110 [<c013e5ad>] __fput+0xc2/0xde [<c013d251>] filp_close+0x5a/0x63 [<c013d2b2>] sys_close+0x58/0x7a [<c0108807>] syscall_call+0x7/0xb Code: 0f 0b 8f 06 52 3d 22 c0 83 c4 14 85 f6 75 1f b8 00 e0 ff ff <6>note: wwwo...

...". Do your event log records contain non-ascii text? If so, I''ll have to switch to the wide character version of ReadEventLog() I think. This might also explain the duplicate records you showed me earlier (?). Where are you located, btw? I forgot. Also, regarding the EventLog#notify_change method, I just remembered something. From the MSDN docs: The NotifyChangeEventLog function does not work with remote handles. > troubleshooting in win is terrible, i think i might as well go to the other route, that is, just let a linux syslog do the central processing. I really wanted to av...

Hi, I''ve got EventLog#write and EventLog.add_event_source methods done. Well, I *think* they''re done, but I can''t get the data (text) to work properly, and I''m not sure if it''s a bug in my .mc file, the add_event_source method, the write method, or just a goof in my test file. The source, category and event id seem to be ok. However, the

...5e3ec <[nfsd]nfsd_cache_lookup+c0/2a4> Trace; c01441c8 <dput+18/144> Trace; c013ef32 <vfs_follow_link+112/188> Trace; c0122f5a <vmtruncate+142/180> Trace; c0146e46 <inode_setattr+22/b4> Trace; e095f182 <[nfsd]nfssvc_decode_symlinkargs+1e2/208> Trace; c0146fcc <notify_change+7c/240> Trace; c0130eda <do_truncate+4a/60> Trace; c0131f2a <filp_open+52/5c> Trace; c013126e <sys_ftruncate+136/154> Trace; c0106fd2 <system_call+2e/34> Code; e094e940 <[lockd]nlmsvc_decode_testargs+b8/1f0> 00000000 <_EIP>: Code; e094e940 <[lockd]nlmsvc_...

...21d3dd>] truncate_complete_page+0x1b/0x5c [<ffffffff8022b98f>] truncate_inode_pages_range+0x9b/0x290 [<ffffffff802c555b>] vmtruncate+0x4e/0xc9 [<ffffffff8024335e>] inode_setattr+0x22/0x104 [<ffffffff88050b2f>] :ext3:ext3_setattr+0x1bd/0x228 [<ffffffff8022ceab>] notify_change+0x145/0x2f3 [<ffffffff802d17af>] do_truncate+0x5e/0x79 [<ffffffff80212f1a>] may_open+0x1d3/0x22f [<ffffffff8021b4ce>] open_namei+0x2c8/0x6ed [<ffffffff80227a14>] do_filp_open+0x1c/0x38 [<ffffffff8021a1b8>] do_sys_open+0x44/0xbe [<ffffffff802602f9>] tracesys...

...3:10 kernel: [<c01491f0>] inode_setattr [kernel] 0x24 18:03:10 kernel: [<d401f963>] ext3_setattr [ext3] 0x1c3 18:03:10 kernel: [<d401d810>] ext3_get_block [ext3] 0x0 18:03:10 kernel: [<c01281db>] do_generic_file_read [kernel] 0x2c3 18:03:10 kernel: [<c0149359>] notify_change [kernel] 0x5d 18:03:10 kernel: [<c012a2aa>] generic_file_write [kernel] 0x5c2 18:03:10 kernel: [<c01348ce>] do_truncate [kernel] 0x46 18:03:10 kernel: [<c0134bd1>] sys_ftruncate [kernel] 0x12d 18:03:10 kernel: [<c01085f7>] system_call [kernel] 0x33 I noticed that an...

...9/0x30 [btrfs] [376007.682125] [<ffffffffa00f19a7>] btrfs_join_transaction+0x17/0x20 [btrfs] [376007.682133] [<ffffffffa00f7fa8>] btrfs_dirty_inode+0x58/0xe0 [btrfs] [376007.682141] [<ffffffffa00fcaf2>] btrfs_setattr+0xa2/0xf0 [btrfs] [376007.682144] [<ffffffff811eec74>] notify_change+0x1c4/0x3b0 [376007.682146] [<ffffffff811dde96>] ? final_putname+0x26/0x50 [376007.682149] [<ffffffff811d088d>] chown_common+0x16d/0x1a0 [376007.682153] [<ffffffff811f2b08>] ? __mnt_want_write+0x58/0x70 [376007.682156] [<ffffffff811d1a8f>] SyS_fchownat+0xbf/0x100 [376007...

...10 20:29:37 torsa kernel: Call Trace: [<c012b967>] [<c012bf30>] [<f8873a7a>] [<c012c01e>] [<c01298b4>] Nov 10 20:29:37 torsa kernel: [inode_setattr+38/224] [e1000:__insmod_e1000_O/lib/modules/2.4.7-10smp/kernel/drivers/net+-1259 208/96] [sd_mod:sd+2202864/45428268] [notify_change+125/496] [sd_mod:sd+2206751/45424381] [sd_mod:sd+2228154/45402978] <snip>

...readinfo=efc31000 task=f7e37730) Stack: 00000000 efc31ea0 00000001 f0cbf9c0 f5bf2000 f0cbfba0 00000001 c9be8a60 f5bf2000 00000000 00000000 00000000 c9be8a60 00000000 f0cbfa78 efc31ea0 f0cbf9c0 c047e75e e6875774 01222222 00000068 45b55d27 00000000 e6875774 Call Trace: <c047e75e> notify_change+0x164/0x300 <c0465388> do_truncate+0x54/0x6c <c047372f> may_open+0x1a8/0x1fc <c04755ad> open_namei+0x24b/0x5c3 <c04666a6> do_filp_open+0x1c/0x31 <c04667ad> do_sys_open+0x3c/0xa9 <c0466847> sys_open+0x16/0x18 <c0403d2f> syscall_call+0x7/0xb Code: fc f...

Hi, We have a Ubuntu 14.04 server with dovecot 2.2.9 If I try to run /usr/bin/doveadm search -u email at exmaple.com mailbox Junk savedbefore 30d It will dump a core file. We have a similar config on an other server and there is no problem there. Any ideas how to prevent the core dump? root at triws2:~# gdb --args doveadm search -u email at example.com mailbox Junk savedbefore 30d Reading

Hello Andrew, I patched 2.4.20 with your patch found out on http://lwn.net/Articles/17447/ and I have a big problem with: once server is booted on 2.4.20 with your patch, when I want to reboot with /sbin/reboot, server makes a Segmentation fault and it crashs. I tested it on 50-60 servers and it is the same problem. I tested kernel 2.4.20 without your patch: no problem. # uname -a Linux XXXXXX

...58> Trace; c006be04 <ext3_forget+f4/184> Trace; c006ed18 <ext3_free_branches+11c/288> Trace; c006f1c0 <ext3_truncate+33c/4c0> Trace; c0025424 <vmtruncate+148/160> Trace; c00589ac <inode_setattr+34/108> Trace; c00701c8 <ext3_setattr+144/190> Trace; c0058bc4 <notify_change+90/13c> Trace; c00398dc <do_truncate+108/1cc> Trace; c004be94 <open_namei+650/7e8> Trace; c003ad70 <filp_open+58/84> Trace; c003b25c <sys_open+4c/fc> Trace; c0003dfc <ret_from_syscall_1+0/b4> Trace; 01819404 Before first symbol Trace; 0180295c Before first symbol Tr...

...3:10 kernel: [<c01491f0>] inode_setattr [kernel] 0x24 18:03:10 kernel: [<d401f963>] ext3_setattr [ext3] 0x1c3 18:03:10 kernel: [<d401d810>] ext3_get_block [ext3] 0x0 18:03:10 kernel: [<c01281db>] do_generic_file_read [kernel] 0x2c3 18:03:10 kernel: [<c0149359>] notify_change [kernel] 0x5d 18:03:10 kernel: [<c012a2aa>] generic_file_write [kernel] 0x5c2 18:03:10 kernel: [<c01348ce>] do_truncate [kernel] 0x46 18:03:10 kernel: [<c0134bd1>] sys_ftruncate [kernel] 0x12d 18:03:10 kernel: [<c01085f7>] system_call [kernel] 0x33 I noticed that an...

...fffff810b41ee>] ? filemap_fault+0xb9/0x2f6 [ 240.599839] [<ffffffff810ca3c2>] ? __do_fault+0x38c/0x3c3 [ 240.601003] [<ffffffff810ee1ce>] ? do_sync_write+0xce/0x113 [ 240.602082] [<ffffffff81051e75>] ? current_fs_time+0x1e/0x24 [ 240.602968] [<ffffffff811009b7>] ? notify_change+0x180/0x2c5 [ 240.604245] [<ffffffff8110b7b5>] ? utimes_common+0x12d/0x14d [ 240.605355] [<ffffffff8110b856>] ? do_utimes+0x81/0xca [ 240.606558] [<ffffffff8110b9ab>] ? sys_utimensat+0x5b/0x6a [ 240.607817] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b [ 240...

...fffff810b41ee>] ? filemap_fault+0xb9/0x2f6 [ 240.599839] [<ffffffff810ca3c2>] ? __do_fault+0x38c/0x3c3 [ 240.601003] [<ffffffff810ee1ce>] ? do_sync_write+0xce/0x113 [ 240.602082] [<ffffffff81051e75>] ? current_fs_time+0x1e/0x24 [ 240.602968] [<ffffffff811009b7>] ? notify_change+0x180/0x2c5 [ 240.604245] [<ffffffff8110b7b5>] ? utimes_common+0x12d/0x14d [ 240.605355] [<ffffffff8110b856>] ? do_utimes+0x81/0xca [ 240.606558] [<ffffffff8110b9ab>] ? sys_utimensat+0x5b/0x6a [ 240.607817] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b [ 240...

..._buffer+17/d0> <===== Trace; c015f9bb <cleanup_transaction+12b/158> Trace; c015fbae <log_do_checkpoint+1c6/220> Trace; c015f86d <log_wait_for_space+8d/b0> Trace; c015c98b <start_this_handle+307/3a8> Trace; c015caa3 <journal_start+77/a0> Trace; c0152986 <ext3_notify_change+14a/360> Trace; c0120176 <do_generic_file_read+8d2/8e0> Trace; c0139638 <notify_change+40/64> Trace; c0129067 <do_truncate+5f/ac> Trace; c01329bc <open_namei+474/4d4> Trace; c0129e40 <filp_open+44/f8> Trace; c012a08e <sys_open+36/94> Trace; c010a034 <system...

...lose = 0x335a8 <mbox_storage_close>, get_status = 0x43b94 <index_storage_get_status>, sync_init = 0x3b228 <mbox_storage_sync_init>, sync_next = 0x449d8 <index_mailbox_sync_next>, sync_deinit = 0x44b50 <index_mailbox_sync_deinit>, notify_changes = 0x33650 <mbox_notify_changes>, transaction_begin = 0x3368c <mbox_transaction_begin>, transaction_commit = 0x336b0 <mbox_transaction_commit>, transaction_rollback = 0x337a8 <mbox_transaction_rollback>, keywords_create = 0x44650 <index_key...

...a>] ? unmap_mapping_range+0x59/0xf5 [69003.807987] [<ffffffff810be8f1>] ? vmtruncate+0x36/0x41 [69003.807987] [<ffffffffa0152718>] ? btrfs_setattr+0x1d5/0x230 [btrfs] [69003.807987] [<ffffffff8104b2b6>] ? current_fs_time+0x1e/0x24 [69003.807987] [<ffffffff811055e5>] ? notify_change+0x195/0x27e [69003.807987] [<ffffffff810f1f4a>] ? do_truncate+0x68/0x86 [69003.807987] [<ffffffff810fa6a4>] ? get_write_access+0x10/0x3a [69003.807987] [<ffffffff810f2059>] ? sys_truncate+0xf1/0x125 [69003.807987] [<ffffffff81009a82>] ? system_call_fastpath+0x16/0x1b [69...