similar to: building ext3 as a module

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter

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

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

We've just started getting this. We're running 5.10, kernel 2.6.32-358.18.1.el6.x86_64. Anyone else seen anything like this, or have any ideas? mark Nov 1 14:34:21 <server> kernel: WARNING: at block/ll_rw_blk.c:543 blk_do_ordered() Nov 1 14:34:21 <server> kernel: Nov 1 14:34:21 <server> kernel: Call Trace: Nov 1 14:34:22 <server> kernel:

Under xen, either stock xen-2.0.1+linux-2.6.9 or Fedora''s latest (2.6.10-1.1109_FC4), drdb (<http://www.drbd.org/>),as soon as I try to write to one of its devices, causes "Badness" in the kernel and, ultimately, a spontaneous reboot. Under non-xen 2.6.10-1.1109_FC4 and 2.6.9-1.678_FC3, drbd works fine. The error: Jan 25 21:01:23 turing kernel: Badness in blk_plug_device

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:

From: Rusty Russell <rusty@rustcorp.com.au> Lguest block driver A simple block driver for lguest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Cc: Jens Axboe <jens.axboe@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/block/Makefile | 1 drivers/block/lguest_blk.c | 271

From: Rusty Russell <rusty@rustcorp.com.au> Lguest block driver A simple block driver for lguest. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Cc: Jens Axboe <jens.axboe@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/block/Makefile | 1 drivers/block/lguest_blk.c | 271

Regardless of the filesystem (i''ve used reiserfs, xfs, ext3), whenever I mount a fresh DRBD partition I get some nasty kernel messages. This is under Debian Sarge, Xen kernel 2.6.11.12-xen0 (dom0) using DRBD v0.7.11 (pulled from Debian "testing"). This is what I did to create the partition. On both nodes I created a new LVM storage device and started DRBD: # lvcreate

Hi, Well, this might not be the right place to pose this question. But, I'm sure that there are people who can answer this. My question is regarding how disk errors are reported to ext3. From my basic understanding of the block driver routines, it seems that all the different types of disk errors (like sector failures, scsi bus timeout, etc) are converted into one single error code (EIO) and

Hi, with being exposed to more and more failed hard disks reports, I've accumulated several questions of the logged messages in /var/log/messages file: like how to identifying failed disks(partitions), where is the exact failed sector(s) on the hard disk, and why badblocks reports OK to the reported disk failure. Let me explained the above with the following several example. scenario #1, a

Lo, Is there already a patch out for latest 2.4.6-ac release? I'm pretty sure that the ext3 patch -ac2 can not be applied on this release. Bye. -- the trees the birds the air the grass the water the flies the trees

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

When memory is low, ext3 gets a bit sluggish cursor getting jumpy etc. I say ext3 because I don't see a similar behavior with ext2. What are the ext3 tuning variables that I can try? For example, I see a message like "commit interval 5 seconds" in /var/log/dmesg.

One of my servers appears to have some filesystem corruption. I'm running Red Hat 6.2 with kernel 2.2.19pre6 and ext3 0.5e. That server currently has e2fsprogs-1.20-WIP-0117 installed. Is it OK to upgrade to the latest e2fsprogs (i.e.: 1.22) prior to running the e2fsck on the filesystem? --Shawn

On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> wrote: >On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: > >> On 04/18/2017 12:54 PM, H wrote: >> > A couple of days ago I submitted a request to ElRepo and kmod-jfs >is >> now available for CentOS 7 as well. >> > >> >> Did not have a need to

On 10/26/2017 08:01 PM, Akemi Yagi wrote: > On Thu, Oct 26, 2017 at 4:17 PM, H <agents at meddatainc.com> wrote: > >> On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> wrote: >>> On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: >>> >>>> On 04/18/2017 12:54 PM, H wrote: >>>>> A couple

Thank you, installed it and it worked fine. Now I am looking for the same for CentOS 7... It did not look like you have that in your repository? On 3/13/2017 1:09 PM, Nux! wrote: > yum -y install http://mirrors.coreix.net/elrepo/elrepo/el6/x86_64/RPMS/kmod-jfs-0.0-1.el6.elrepo.x86_64.rpm > > (that's for 64bit, adjust the url accordingly for 32bit) > > it won't hose your

Hello all, I'm relatively new to CentOS, but I've been using linux as my main operating system on both the desktop and server ends for the past 4 years. I currently have a PIII server with two 160GB IDE hard drives in it, in a virtual RAID 1 array. At the time of installation, the only FS choices for the largest partition, 120GB, were ext2 and ext3. I chose ext3, but now am wishing

Hello everyone. The following patches are for Fedora 10(**). The distro-independent package will be put to kernel.org a bit later. I. Loading kernels from btrfs volumes Now you can load kernels and initrds from btrfs volumes composed of many devices. WARNING!!! Make sure that all components of your loading btrfs volume(*) are visible to grub. Otherwise, you''ll end with