similar to: RE: ext3 "noload" option to mount returning error in 2.4.9 & 2.4. 18 s eries kernel

I have an ext3 filesystem that I want to mount without loading the journal. I tried the "noload" option with both 2.4.9 and 2.4.18 series kernels and get the errors listed below. [root@host]# mount -t ext3 -o noload /dev/sdf1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdf1, or too many mounted file systems /var/log/messages: Apr 18 13:30:23 host kernel: ext3:

I have an ext3 filesystem that I want to mount without loading the journal. I tried the "noload" option with both 2.4.9 and 2.4.18 series kernels and get the errors listed below. [root@host]# mount -t ext3 -o noload /dev/sdf1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdf1, or too many mounted file systems /var/log/messages: Apr 18 13:30:23 host kernel: ext3:

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

The following patch fixes the function checks in configure for getseuserbyname() and get_default_context_with_level(). These functions are in libselinux, and since -lselinux is not added to LIBS, these functions could never be found. Please apply. configure.ac | 3 +++ 1 file changed, 3 insertions(+) --- openssh-4.4p1.orig/configure.ac 2006-09-24 15:08:59.000000000 -0400 +++

I decided that I would try out 2.5.44, and I noticed that htree was merged. If I don't do the tune2fs -O dir_index, and e2fsck -D, the (exisintg) fs won't use htree, right? Once I do the tune2fs and e2fsck, will I still be able to go back to a non-htree kernel if needed? (Will a htree-ized fs work on a non-htree kernel?) I'm guessing that it won't. I've seen a 2.4 htree

Can someone please describe how to use the "noload" option and what the expected results are? -Leslie

Hi all, I've been told that part of best practices is to noload all modules that you don't use. Adsi being one of them (are there actually people using adsi & asterisk?) I noloaded it in /etc/asterisk/modules.conf: noload => res_adsi.so noload => app_adsiprog.so When I start * (this is cvs head of today by the way) I get: [app_voicemail.so]Aug 31 17:25:49 WARNING[4961]:

Hello I'm using Asterisk 1.4.20, and can't have Asterisk not load modules I don't need: ================ > cat modules.conf noload => codec_speex.c ip04*CLI> reload ip04*CLI> show modules codec_speex.so ================ Just to check, I added the actual filename (.so): ================ > cat modules.conf noload => codec_speex.c noload => codec_speex.so

Well, I had the first use of the recovery mode on the RH 8.0 install CD today on a dev system. I changed the mount option for the root partition to data=writeback to see what all the claimed speed increases are about, and the system failed to mount the partition r/w, so the resulting boot failed. After search usenet, it seems other RH folks have had this problem, possibly because it is

Hello, I'm using RedHat 7.2. I needed to mount my root fs to QNX 6.1. QNX supports ext2 only but I tried that anyway. It was mounted wrong (e.g. the /root directory was symbolic link to non-existing file). When I wanted to boot from the RedHat again, these errors occured: ... Mounting root filesystem EXT3: failed to open journal device unknown-block(0,0):-19 mount: error 22 mounting ext3

I am doing some SELinux testing under 2.6.0-test4 on PPC with an ext3 partition. It uses the extended attributes and security labels. After using the SELinux setfiles utility, which sets all of the security labels in the filesystem, I get some strange behavior from e2fsck. When I fsck it, it gets a pair of problems with all of the symlinks on the system, like these: Symlink /usr/bin/ptx (inode

Author: prafull Repository: /hg/zfs-crypto/gate Revision: 95c55f804e6251aa87677ff29f6de677f407d04d Log message: 6375481 eri driver doesn''t reset promiscuous mode correctly (fix lint) Files: update: usr/src/uts/sun/io/eri.c

Author: prafull Repository: /hg/zfs-crypto/gate Revision: 7ac25aab4161d85ef853d069b51eb9f7f7ad9d90 Log message: 6244642 eri driver panics if ndd command is run with the wrong instance number. 6375481 eri driver doesn''t reset promiscuous mode correctly 6394546 eri is passing packets to the upper layer even when it shouldn''t Files: update: usr/src/uts/sun/io/eri.c

Does anyone know if there's a patch out there for 2.4.9-ac10? I'm investigating what's involved to go from ext2 to 3. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20060816/cf899f58/attachment.htm>

Hi, I am using an ASUS CUV4X-E mother board with a scsi adapter Adaptec AIC-7881U, with one QUANTUM ATLAS_V_18_WLS and MAXTOR 4K040H2, ATA DISK drive connected with a VIA vt82c686a (rev 22) IDE UDMA66 controller. The instalation from original kernel 2.4.7 was ok, but when I upgrade to kernel 2.4.9-31, almost every day I got an error in many process, including apacha, qmail and many

Is there a patch for 2.4.9 out there. I saw the ac one on http://www.uow.edu.au/~andrewm/linux/ext3/ but cant fond one for the main branch Regards Robert Stanford

Hello, I am going to set up a new file server ("smb" and "nfs") machine for the local network of my former school. Therefore I've just downloaded and successfully compiled "linux-2.4.9-ac5" (including "disk quota support" and, of course, support for "ext3 file system"). I've read the statement: | ... | | The quota code in the -ac

Hey all. I was wondering if an official patch vs 2.4.9 is in the works yet. I managed to apply it locally, but there was one or two changes that didn't apply cleanly. (mm/vmscan.c has had some stuffs moved around). I think I did it right, but an official patch is always nice. :) -- Tom Rini (TR1265) http://gate.crashing.org/~trini/

Hello, where do you had downloaded the ocfs-2.4.9-e-1.0.9-8.src.rpm -Package and where can I find a working combination of fw-kernel and ocfs? We are testing under SLES8 and had linux-2.4.20rc2-orafw Kernel downloaded from otn and try to compile the ocfs-sourcen also downloaded from otn. Problem is, that Suse SLES8 works with kernel 2.4.19, so we can't recompile the ocfs-sourcen for kernel

Hi all, I had a very simple samba-2.2.3a installation running. Not as domain master or such. Now after upgrading to 2.4.9-31 kernel, I am unable to start nmbd. smbd starts okay. Does anyone know of any selection in the config for a newly compiled kernel that could prevent nmbd from running? Is there a confict with this kernel downloaded from ftp.redhat.com? TIA Bob -- Bob