similar to: Software RAID & Ext3 v0.0.6b

Hi, While doing some stress testing with presto module from the intermezzo project layered over ext3, I got the following assertion failure: Jan 17 23:09:55 planck kernel: Assertion failure in jfs_prelock_buffer_check() at journal.c line 410: "bh->b_jlist == 0 || bh->b_jlist == BJ_LogCtl || bh->b_jlist == BJ_IO || bh->b_jlist == BJ_Data" Jan 17 23:09:55 planck kernel:

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

SYSTEM: rh6x based system, 2.2.19-6.2.7 rh errata kernel + 0.0.7a patch, I rebuilt rpm for i686; celeron466, 64MB, PIIX4. root fs is on software raid1 ext2, 6 additional fs's on software raid1 ext2. There's a 3rd HD, not mirrored, which is mounted ext3. EXT3-fs: mounted filesystem with ordered data mode. I enabled journal with tune2fs -j with unmounted fs. The 3 HDs are tuned with

I get 2 rejects applying 2.2.19-ext3 to latest errata rh 2.2.19 kernel. 1) fs/buffer.c Should I put "J_ASSERT(buf->b_count > 0);" before or after " *(int *)0 = 0;"? ===== ext3 0.0.7a patch --- 934,946 ---- if (buf->b_count) { buf->b_count--; + if (!buf->b_count && + (buf->b_jlist != BJ_None && buf->b_jlist

All, I know that there is no official port to Kernel 2.4.4, thus I may not get any help, however I am hoping someone could point me in the right direction for my problem. I am currently forced to use kernel 2.4.4 for reasons out of my control (embedded board). Here are the exact versions of everything I'm running: ExT3 Version: ext3-2.4-0.9.6-248 Util Version: util-linux-2.11f.tar.bz2 e2fs

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 all, I am trying to integerate 0.0.6b with our kernel RPM here and have come across an interesting conflict. I want to include the raid patch that Red Hat includes in their kernel but that patch includes the following hunk: --- linux/include/linux/fs.h.orig Tue Jan 16 13:30:09 2001 +++ linux/include/linux/fs.h Tue Jan 16 13:47:18 2001 @@ -191,6 +191,7 @@ #define BH_Req 3 /* 0 if the

I think I have this one solved, I hope. I think what Andreas and I are running into are a few different assertions. One being the LVM lvm_do_pv_flush caused assertion which is related directly to invalidate_buffers() being called which then triggers refile_buffer() on a journaled buffer, which appears clean in all other ways according to the checks in refile_buffer(). The following is what

Hello! I'm using i868 (Pentium III) machine running Windows 2000 and running Linux, installed on dedicated partition, in parallel via VMWare. Linux config is RedHat 7.0 (kernel ) As I'm pretty new to Linux, I'd like to know exact procedure how to install ext3 filesystem support (also which packages do I need). My kernel config is as follows: kernel-headers-2.2.14-5.0

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

The list has gotten pretty quiet over the last week. As I understand it, we are down to the following big ticket items: 1. Quotas on meta journaling 2. ext3 + LFS 3. Various minor bugs. Is this accurate? -- Keith Barrett Red Hat HA Team

Jun 29 11:30:05 ns kernel: Assertion failure in __journal_file_buffer() at transaction.c:1935: "jh->b_jlist < 9" Jun 29 11:30:05 ns kernel: invalid operand: 0000 Jun 29 11:30:05 ns kernel: CPU: 0 Jun 29 11:30:05 ns kernel: EIP: 0010:[__journal_file_buffer+54/400] Not tainted Jun 29 11:30:05 ns kernel: EFLAGS: 00010282 Jun 29 11:30:05 ns kernel: eax: 00000059 ebx:

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

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

Hi all! While I was having some fun, testing different filesystems at home and making some benchmarks, I hit a bug when running Postmark in an ext3 partition mounted with data=journal. I repeated this test twice and got the same results under Linux 2.5, also it was not found while mounting with data=writeback or data=ordered or under Linux 2.4. I don't know if it's a know problem or

I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 dom0. My xen-tools.conf: lvm = vg00 size = 100Gb # Disk image size. memory = 2048Mb # Memory size swap = 2G # Swap size # noswap = 1 # Don''t use swap at all for the new system. fs = ext4 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default

I think I wrote not very clearly. I say ''swap in domU will save in case lag or little mistake with balloon''. If course, there is no any kind of ballooning for dom0. Right now we running pretty much VMs for our cloud services and we use heavy memory management (it grabs and gives memory with lag less then second depends on usage in customers VM). And we have some statistics

Hi, I hope this is the right mailing list, I think this is an ext3 error. I was copying a bunch of largish files around last night (between 300MB and 5GB each), and suddenly the partition I was copying to stopped responding - any program accessing files on that partition would lock up, and not even kill -9 would terminate them. I'm not particularly experienced with tracking down

Hi List, is it possible to limit the (disc) io for a domU? Best regrads, Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I just found out the hard way that sysvol replication with rsync stoped working when I activated winbind (libnss-winbind actually) on my primary AD DC. Originally I hadn't planed to activate winbind on the primary AD DC since that machine was not meant to provide any shares. What I hadn't thought of was the fact that GPOs reside as files on the sysvol share and thus are subject