search for: notify_changes

Hi! I tried to use cdrdao on 2.5.5x kernels but kernel gives me following messages. Further debugging reveals that sb is NULL in __ext3_std_error() function. I tried this on ext2 and it seems it isn't ext3 specific, on ext2 it also doesn't work. cdrdao is after this in D state and is unkillable, but the CD-ROM drive from which I tried to grab is perfectly usable. This happens to me

-------------- 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

Assertion failure in journal_add_journal_head() at fs/jbd/journal.c:1679 : "(((&bh->b_count)->counter) > 0) || (bh->b_page && bh->b_page->mapping)" ------------[ cut here ]------------ kernel BUG at fs/jbd/journal.c:1679! invalid operand: 0000 [#2] CPU: 0 EIP: 0060:[<c017637f>] Not tainted EFLAGS: 00010282 EIP is at

Hi again, Pe?a wrote: > # > i get a segfault on windows-pr if i run mulitple tails by > # threading, one thread for each host i''m tailing. > > argh, this is getting tricky. i''m getting empty records and weird characters too :) > > -------- > record_number : 20983290 > time_generated : Tue May 30 16:15:27 China Standard Time 2006 > time_written :

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

I got this.. The system was usuable, but not very. If I tried to access the ext3 volume, it would hang. Reboot hung too, complaining about too many open files. Any ideas? I have no idea what triggered it; this is a big file/web/mail server, with all of that on the ext3 volume. And I've never run ksymoops before, but I think I did it right. - Josh Assertion failure in

Hello all: I was getting a reproducible crash during an update of a xen system. The problem went away after I set SELinux to permissive, but the fact that it crashed was alarming (first one on a non-dev system that I've had in over a year). I attempted the update earlier but it crashed at the same point after attempting to update selinux. After verifying hardware (all clean) I ran it again

Several times recently my "mutt" email program has looped for hours at a time in the middle of a sys_ftruncate call. This happens when I use the "$" command to write changes out to my mailbox. It does eventually return from the call and everything seems to have worked ok. But in the meantime the CPU is pegged, $MAIL is locked so I can't receive new mail, and signals to

I already posted this in the thread "ENOSPC with mkdir and rename", but now I have a device with 100GB unallocated on the "btrfs fi sh" output, and when I run a rebalance of the form: > btrfs filesystem balance start -dusage=50 -musage=10 "$mount" I get more than 75 of such stack traces contaminating the klog. I've put some of them up in a gist here:

Sorry to parachute in here with an emergency question but I do have a big problem and I want to eliminate samba as a possibility. I have a redhat 7.2 server that has been solid until last Wed. On that day I had installed samba on it from the redhat rpms. That night it went down with a kernel oops on nfsd. I shutdown samba but left it installed. It has gone down again today but the messages

OS: Fedora Core release 4 (Stentz) KERNEL: Linux rack1.ape 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 i686 i386 GNU/Linux CLUSTER: 11 Linux kernels, mixed environment FC4,FC5,FC6 SAN: FC Infortrend storage, QLogic16 port FC switch, FC adapter LSI FC929X (21224,1):ocfs2_truncate_file:242 ERROR: bug expression: le64_to_cpu(fe->i_size) != i_size_read(inode)

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

Hello, We have about 20 - 30 embedded machines running Linux 2.4.13, which the ext3-2.4-0.9.13-2413 patch applied. These are PowerPC 7410 based systems. I am getting reports of Oops happening either during removes (rm's), or coppies (cp's). Most reports state that issuing the same command once the system boots back up, does not cause it to crash. I guess its something else leading up

In August I reported a problem with the sys_ftruncate call that caused me to reboot my machine. I didn't see any responses to it then on the ext3 list, and the problem is now recurring, so I thought I'd try again. I don't think I've rebooted since the last problem. In the last few days it hasn't taken as long as 17 hours, but it has sometimes taken unusual and uncomfortable

<20100926154324.GD21843 at redhat.com>; from Michael S. Tsirkin on Sun, Sep 26, 2010 at 17:43:24 +0200 > > > >It's vanilla 2.6.32.22, but I also reproduced this on Debian's 2.6.32-23 > > > >(based on 2.6.32.21). > > > > > > > >If offload is the only difference, I'll play with different offload > > > >options and check

<20100926154324.GD21843 at redhat.com>; from Michael S. Tsirkin on Sun, Sep 26, 2010 at 17:43:24 +0200 > > > >It's vanilla 2.6.32.22, but I also reproduced this on Debian's 2.6.32-23 > > > >(based on 2.6.32.21). > > > > > > > >If offload is the only difference, I'll play with different offload > > > >options and check

Hi, I've recently been playing about with recent ext3 0.0.6b and lvm 0.9.1 beta7 and am now able to trigger an "Attempt to refile free buffer" assertion. This seems to "only" occur when using ext3 on the root filesystem. Possibly that is related to the fact that the lvm utility I'm using to reproduce this problem is modifying data in /etc. The easist reproduction

...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_keyw...

Hi list This happened when running an iozone test over ceph, it was doing lots of random reads. I have no idea how to properly interpret this, I should find it out. Let me know if you need something else. Thanks! [69003.803272] ------------[ cut here ]------------ [69003.807987] kernel BUG at fs/btrfs/inode.c:6230! [69003.807987] invalid opcode: 0000 [#1] SMP [69003.807987] last sysfs file: