Displaying 20 results from an estimated 900 matches similar to: "Kernel Ooops probably in conjunction with lvm"
2002 Jun 11
1
another oops, this time with 2.4.18-4
Back again with another oops, which looks suspiciously similiar to the one i
posted some days ago
(https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html).
Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))"
ksymoops 0.7c on i686 2.4.18-4custom. Options used
-V (default)
-k
2002 Sep 25
0
PROBLEM:
Ext3 Journal oops & RAID-1 set losing sync.
(Sent to both EXT3 and Linux-RAID since both are in use and seem
possibly relevant)
I have had a number of problems maintaining a software RAID-1 set on an
IDE box I maintain; it seems that doing raidhotadd on the drive marked
as invalid works each time though. However, I've had both errors about
trying to read past the end of the
2001 Aug 02
0
ext3 0.0.7a Assertion
Hi,
Doing the following I can generate an assertion in ext3 0.0.7a.
I have an ext3 filesystem on /foo. I export /foo via nfs. I then mount
via localhost:/foo onto /mnt. Start up a dd to generate a file on the nfs
mount. (cd /mnt; dd if=/dev/zero of=./dd.out bs=1024k), then on the
localhost filesystem /foo I rm the file. rm -f /foo/dd.out.
This results in "ext3_free_inode: bit already
2001 Nov 21
1
getting kernel version and cvs version in sync
Hello,
what is the state of the onion with the ext3 support in the upcoming 2.4.15? I don't think it will be on the current cvs level (due to linus accept policy :). So, will there be patches to place a current kernel on the cvs state?
--
Regards,
Wiktor Wodecki | http://johoho.eggheads.org
wodecki@gmx.de | IRC: Johoho@IrcNET
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 Dec 06
1
2.2.19: Assertion failure in ext3_new_block() at balloc.c line 709
Red Hat 2.2.19-6.2.12
+ 0.0.7a
+ https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html
(not tuned in /proc yet)
+ journal 4MB on each fs
+ 6 ext3 fs on raid1 (hda+hdc)
+ 1 ext3 fs on another disk not on raid1 (hdd)
While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got:
ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used
-V (default)
-k
2001 Jun 04
1
Ooops output
Here's an oops output on 2.4.5 + CVS/ext3.
This happened while trying to do a mkinitrd (on RedHat 7.1).
ksymoops 2.4.0 on i686 2.4.5-2smp. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.5-2smp/ (default)
-m /boot/System.map-2.4.5-2smp (specified)
kernel BUG at inode.c:934!
invalid operand: 0000
CPU: 1
EIP:
2005 May 03
0
several ext3 and mysql kernel crashes
Hi Ext3!
I'm running about 30 dedicated MySQL machines under quite decent loads,
and they are occassionally crashing. I've been logging console messages
recently in an effort to find the cause, and some appear to be related
to
I perused your lists and found the message I'm replying to.
If you don't mind, I've included messages and ksymoops from two crashes
that I had
2001 Jun 25
1
Oops in iput
Hi,
oops in iput - Kernel 2.2.19/i386 + ide-udma patches + ext3 patches (0.0.7a)
Intel BX chipset, SCSI Disks Symbios chipset - The crashing process
is the master process of "postfix" an MTA.
Just before the crash all processes on that machine started to segfault
in nameserver resolution (remote dns server) and after 2-3 minutes
this oops happened.
ksymoops 2.3.4 on i686 2.2.19.
2001 Nov 05
2
oops on 2.4.14-pre8
Hello!
I got oops after about 3 hours of uptime. Load was about 1,5.
This is output of ksymoops after forced reboot if it helps someone. :-)
ksymoops 2.4.0 on i686 2.4.14-pre8. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.14-pre8/ (default)
-m /boot/System.map-2.4.14-pre8 (default)
Warning (compare_maps): mismatch on
2001 Jun 21
0
oops in ext3_new_block / 2.2.19/0.0.7a
Hi,
i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a
fsck 1.21
ksymoops 2.3.4 on i686 2.2.19. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.2.19/ (default)
-m /boot/System.map-2.2.19 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the
2003 Jan 28
0
OOPS on 2.4.20-ac2
Hi,
I got the OOPS below on my laptop running vanilla 2.4.20-ac2; I had to
copy it byhand so it may not be 100% accurate. It hasn't happened
again, and this is the first problem I've had with this kernel (or any
other kernel, for that matter.) Anyway, I'm not sure, if a) this is
actually an ext3 problem, b) OOPS reports of 2.4.20-ac2 are of any
interest, so I won't bother with
2002 Apr 04
1
Ext3 related oops and a crash
We have here an knfs fileserver running ext3 on 2.4.18 kernel with three
filesystems:
<CLIP>
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 10080520 3609632 6368476 37% /
/dev/hda4 16437332 12295408 3974932 76% /home
/dev/md1 1024872060 409906136 614441636 41% /fs
</CLIP>
The /fs filesystem lives on a
2002 Jan 21
2
Assertion Failure
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
2003 Feb 14
0
[Bug 50] New: Kernel panic with netfilter
https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=50
Summary: Kernel panic with netfilter
Product: netfilter/iptables
Version: patch-o-matic
Platform: i386
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: unknown
AssignedTo: laforge@netfilter.org
2001 Nov 25
2
ext3 problem with loop devices?
Hello,
it seems I am having a problem with loop mounting on ext3. I am doing
this:
- make an ext2 filesystem in a file
- loop mount this file
- write into the loop mounted file system
- umount the file
Sometimes this works; occasionally the file remains empty after the
umount. A sync before the umount seems to help.
Is this a known problem?
Thanks,
Andreas.
2007 Apr 18
2
[Bridge] Re: [2.4.22] bad interaction between e100 and bridge: BUG at dev.c:991!
Could the problem be that the e100 can do IP receive checksumming on the board,
but the eepro driver doesn't enable it. When the board is doing checksum
offload, then the csum field isn't set.
Please try disabling receive checksumming on the e100 driver
modprobe e100 XsumRX=0
If this is the problem, it exists both 2.4 and 2.6.
On Wed, 27 Aug 2003 18:24:57 +0200
Hannes Schulz
2003 May 05
1
kjournald oops on 2.4.20
I have a NFS server with stock 2.4.20 patched with the 5 data=journal
patches, plus the 2.4 LSM and NSA's selinux.
The partition is mounted with the options:
rw,noatime,nosuid,nodev,data=journal,errors=remount-ro
The oops seems to happen when the fs is under load. I don't think I
encountered this behavior with a non LSM/selinux kernel, so it may have
something to do with those, but I
2004 Mar 03
0
consistent crash with data=journal
I've been running into a kernel panic pretty consistently when using
data=journal. This occurs during heavy IO, and is highly reproducible
(only takes about 5 minutes of IO to cause it). The applications being
used are MySQL, Postfix, and a mail filtering application which operates
on postfix queue files using mmaped IO.
Shortly before the crash, the following messages are logged:
Mar
2002 May 28
1
2.4.18rc2aa2 oops
Hi,
just got this oops on one of my production servers (4way smp + highmem).
Is it fixed in newer kernels or is it something new?
Load is steadily growing and i cant even do a 'ps ax'...
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0170396>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 0000001d ebx: 00000000 ecx: c02d5f88 edx: