similar to: ext3 journal problems

My manual patching of the rejects in checkpoint.c didn''t work out; a delete of 10,000 files caused a panic (in any ext fs, not just Lustre). In the new checkpoint.c, two routines expected by the patch no longer exist: __cleanup_transaction and __flush_buffer. I can avoid the panic if I omit (don''t try to manually patch) the following: Index: linux-2.6.9/fs/jbd/checkpoint.c

Hi, We are running a server as an nfs head connect to a clariion, every couple of days we have our box fall over with the following msg in syslog. Has anyone had this happen to there boxen? rhel4 u4 May 8 12:23:52 ruchba kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:363: "drop_count != 0 || cleanup_ret != 0" May 8 12:23:52 ruchba kernel: ------------[ cut

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158

Hello. I found bugs on error handlings in the functions arround the ext3 file system, which cause inadequate completions of synchronous write I/O operations when disk I/O failures occur. Both 2.4 and 2.6 have this problem. I carried out following experiment: 1. Mount a ext3 file system on a SCSI disk with ordered mode. 2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT

Hello, I was wondering if we can get some help in resolving this bug. It was reported earlier and logged in bugme.osdl.org http://bugme.osdl.org/show_bug.cgi?id=4683 The problem is kernel oops at log_do_checkpoint() due to NULL buffer_head. This could be because of some race in journalling code for which I don't have much clue. There is kdump available for analysis as mentioned in the

Hello Everyone, I am used to messing with bind zones directly. With samba 4, I cannot do that. Is the following the correct way to add a TXT record for SPF to the zone using samba-tool? /usr/local/samba/bin/samba-tool dns add s4server.example.org example.org example.org TXT "v=spf1 mx -all" I am not sure it is because it is showing up with dig as "v=spf1" "mx"

A little bugfix delta. I don't believe there is a need for x86 users to upgrade. http://www.uow.edu.au/~andrewm/linux/ext3/ - Fix unaligned access on Alpha - Fix build with CONFIG_JBD=n - Speed up log_do_checkpoint() - significant benefits for journalled data mode. - Fix possible oops in log_do_checkpoint(). - Comment out unused journal_release_buffer().

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hey, I am trying to get spf working and it just doesn't want to take. On my Tiny/DJB server it was easy. Anyway here is my entry. $ORIGIN net. itadmins 14400 IN SOA ns1.itadmins.net. hostmaster.itadmins.net. ( 2012102201 16384 2048 1048576 2560 ) 14400 IN A 178.15.51.221 14400 IN

Your spf record is broken: dovecot.org. 39942 IN TXT "v=spf1 a -all" -- Jim Flowers <jflowers at ezo.net> -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

I had the following spat out by syslog on my (2.4.18-pre7-ac3) mailer / web server: Assertion failure in do_get_write_access() at transaction.c:611: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" One of its partitions froze hard--I've rebooted it, and I have an oops which the BUG() triggered which won't decode at the moment, but I'll sort that one out

Hello everybody, Could someone please explain to me what is the difference between kjournald and jbd (precisely, what does each of them do?) Thank you, Alina _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

This patch contains the following possible cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features -

Hi all i installed Redhat beta Roswell, then i updated to Kernel 2.4.8 patched him and installed the newest util-linux + e2fprogs without any custoumized Options. Bootloader is Grub. Now when i boot he says mount -O or -0 is an invalid Option. tune2fs -j /dev/hdXX says "The filesystem already has a journal" lsmod says that no jbd or ext3 Modules is loadet but i have pachted the Kernel

I have a DNS server which is not returning mx queries for some reason? The zone file is as follows: $TTL 1H @ IN SOA example.com. root.example.com. ( 1 ; serial# 3H ; refresh 1H ; retry

Hi all, We are running a new Centos-4 server, and it has kernel panicked on us 4 times in the last month. After the first kernel panic we hooked up a serial console to the server and captured the output in order to have a record of what happens. I've included the error messages from the last time it locked up... but it doesn't really mean much to me. Anybody have any ideas what might be

This patch contains the following cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL: - journal.c: journal_recover Signed-off-by: Adrian Bunk

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

I was just extracting a 96MB tar file ( tar -xWf backup.tar ), the cpu load was 99% for a long time. I then stopped it and tried again, but this time this popped up in my ssh session: -- Message from syslogd at rock at Sat Feb 18 00:47:05 2006 ... rock kernel: Assertion failure in __journal_unfile_buffer() at fs/jbd/transaction.c:1520: "jh->b_jlist < 9" -- A kernel panic dump is

http://www.sample.banga.lt/crash.gif System - fully (except kernel) updated RedHat 7.3. Filesystems - ext3 in default ordered mode. What could be the cause of the crash? Kernel update will solve the problem? Thanks, Mindaugas