Displaying 14 results from an estimated 14 matches similar to: "ext3 0.0.7a Assertion"
2002 Jul 30
1
Disk Hangs with 2.4.18 and ext3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Background:
Large NFS/mail server. Dual PIII/1GHZ. 4GB memory.
Mylex AcceleRAID 352 RAID controller (uses DAC960 driver).
Intel eepro100 network cards.
RedHat 7.3 with all errata. Kernel-2.4.18-5smp.
2GB of memory is used by a RAM disk for mail queue.
ext3 filesystems (switched to ext2 to see if that helps).
one large (100GB data partition).
2001 Nov 14
1
Oops on 2.4.13 w/ ext3-2.4-0.9.13-2413
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
2003 Oct 04
0
chattr +j ==> Oops
[sent this to ext2-devel but haven't seen any other traffic there, so
cc-ing it here]
[Last week] while configuring a new box I came across a site suggesting:
chattr -R -S +j +A /var/spool/postifx
to improve postfix's speed on ext3, in lieu of mounting a separate fs
there w/ data=journal.
So I tried it. Both on the new box (2.4.21-7um) and on my laptop
(about three csets shy of the
2001 Sep 07
4
ext3-2.4-0.9.9
Patches against 2.4.10-pre4 and 2.4.9-ac9 are at
http://www.uow.edu.au/~andrewm/linux/ext3/
It's a fairly large change. The most significant parts are
* the inclusion of Stephen's error-handling work, which is designed to
remount the fs read-only in the presence of software and hardware
errors, rather than forcing a panic.
* Stephen's fix for the journal_revoke assertion
2001 Aug 14
1
[BUG] linux-2.4.7-ac7 Assertion failure in journal_revoke() at revoke.c:307
Greetings all,
I have hit a kernel BUG in revoke.c in kernel 2.4.7-ac7 twice today while
attempting to perform the same operation (patching stock 2.4.8 kernel src
with "patch -p1 < patch-2.4.8-ac4"). Syslog entries follow. Please
email me if you want/need my kernel config or any other information.
Thanks,
jtp
2007 Jun 27
1
making new initrd, how to do it?
I have installed the xen 3.1.0 x86_64 tarball
compiled for RHEL5 on a RHEL5 system. The system in question
was able to boot with the xen kernel that came with RHEL5.
I untarred the tarball, and did
cd /boot
mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen
The command exited properly and made a initrd image.
The machine booted with a grub.conf entry like this:
title Xen 3.1.0
root
2001 May 04
1
LVM 0.9.1beta7 and ext3 0.0.6b
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
2001 Aug 18
2
ext3 0.9.6 for kernel 2.4.9
This is just a rediff and retest - no ext3 changes in this release.
http://www.uow.edu.au/~andrewm/linux/ext3/
The latest diff is against linux-2.4.9. The version of ext3 in
-ac kernels is current.
-ac's ext3 has the "buffer tracing" debug code removed from the
non-ext3 files, so the 2.4.9 diff is more useful for bug hunting.
I should generate a diff against -ac to enable
2001 Jul 30
1
ext3-0.9.5-247/2.4.8-pre3/PPC Oops bits
Okay, after playing around a bit more, I'm getting two oopes in a row
when running dbench 16 or dbench 32. Decoded, here they are:
Assertion failure in unmap_underlying_metadata() at buffer.c:1530: "!buffer_jlist_eq(old_bh, 3)"
kernel BUG at buffer.c:1530!
Oops: Exception in kernel mode, sig: 4
NIP: C003BB34 XER: 00000000 LR: C003BB34 SP: CF881E00 REGS: cf881d50 TRAP: 0700
Using
2006 Apr 21
0
HANGUPCAUSE on SIP channels
Hopefully I'm not just missing some little detail here. We're trying to
set the HANGUPCAUSE on SIP channels to have our softswitch play the proper
recording instead of answering the call on Asterisk to play the message.
It appears that no matter what the HANGUPCAUSE is set to, Asterisk always
just sends "603 Declined".
I looked through the source code briefly and it appears
2003 Oct 03
1
4.9-rc + usb + asus a7n8x == bad news
Hi! Just before we start, this is not the "USB hang on boot" problem. OK?
This post got rather long, so I'll summaries it all in a sentence here:
With FreeBSD 4.9-rc on an ASUS A7N8X with a cheapo memory stick, simply
plugging it in and taking it out a couple of times is a guaranteed panic.
I use only one USB device, a cheapo USB memory stick, which I recently
bought on a
2008 Mar 07
2
Multihomed question: want Lustre over IB andEthernet
Chris,
Perhaps you need to perform some write_conf like command. I''m not sure if this is needed in 1.6 or not.
Shane
----- Original Message -----
From: lustre-discuss-bounces at lists.lustre.org <lustre-discuss-bounces at lists.lustre.org>
To: lustre-discuss <lustre-discuss at lists.lustre.org>
Sent: Fri Mar 07 12:03:17 2008
Subject: Re: [Lustre-discuss] Multihomed
2013 Jan 16
1
Samba AD Auth Stops After Patches
Hello, I have an issue that I can't sort out.
Issue: Just applied the latest round of patches that brought me up to this
Samba version and
suddenly end-users are being prompted for authentication when attempting to
access shares
on this CentOS box from their Windows Vista, 7x86, and 7x64 workstations.
Problem: I am new to Samba and seem to not be connecting the dots
Layer 1: I can ping
2012 Feb 12
0
Bug#659642: xen-hypervisor-4.0-amd64: outl segfaults when restoring monitor from sleep with DPMS
Package: xen-hypervisor-4.0-amd64
Version: 4.0.1-4
Severity: normal
Tags: squeeze
When the monitor is being restored from power saving mode via DPMS, X will lock
up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5
-xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and
2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround