similar to: ext3 "noload" option to mount returning error in 2.4.9&2.4.18 ser ies kernel

It's already mounted rw somewhere else. This enables the needs_recovery feature which prevents an ext2 mount. -Leslie -----Original Message----- From: Christopher J. PeBenito [mailto:pebenito@ieee.org] Sent: Tuesday, April 22, 2003 11:30 AM To: kuczynski, leslie Cc: 'ext3-users@redhat.com' Subject: Re: ext3 "noload" option to mount returning error in 2.4.9 & 2.4.18 s

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:

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

Signed-off-by: Alexey Dobriyan <adobriyan at mail.ru> --- fs/ext3/resize.c | 20 ++++++++++---------- fs/ext3/super.c | 8 ++++---- include/linux/ext3_fs.h | 2 +- 3 files changed, 15 insertions(+), 15 deletions(-) Index: linux-warnings/include/linux/ext3_fs.h =================================================================== ---

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

Hi all, ext3-0.0.5c is now up at: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ The most important part of this release is the e2fsprogs: e2fsck now supports the journal changes for metadata-only journaling. Ted, I've changed around the use of jfs* include files in e2fsprogs quite heavily here. In each build directory --- the lib/ext2fs

Andreas was kind enough to point out that not neccesarily all ext3fs have htrees ready to go. I am running redhat8.0 out of the box. How can I check if ext3fs with htrees is running? I can download the kernel source, but I don't know what options were used when it was built by redhat. Thanks much for all of your help. -Parker -----Original Message----- From: Andreas Dilger

Didn't hear back from anyone regarding if there is a way to determine if I am running the ext3fs with htree. Is there a way I can do it without checking the src code since I am running the precompired redhat kernel with 8.0? Perhaps an entry under /proc somewhere? Pj -----Original Message----- From: Parker Johnson Sent: Tuesday, January 14, 2003 3:34 PM To: 'Andreas Dilger';

Bummer. Does anyone have a url that describes the 2.4 patching process? Any claims on stability? Thanks, Parker -----Original Message----- From: 'Andreas Dilger' [mailto:adilger@clusterfs.com] Sent: Wednesday, January 15, 2003 4:35 PM To: Parker Johnson Cc: 'ext3-users@redhat.com'; Ops Subject: Re: ext3fs still uses sequential search of file names in director ies? On Jan 15,

I have many systems running current ext3 code. Some of them have hardware problems that lead to frequent reboots, and the journal recovery has worked excellently. However, on the periodic forced fsck on supposedly recovered and clean filesystems, I've many times seen fsck report that i_blocks is too large in one or more inodes. I suspect that i_blocks is somehow escaping proper restoration

Hi Wayne, What would be really nice, and I imagine quite easy from a coding perspective would be to allow the user to apply a regex match on the full pathname of the files being transferred. Anyway, thanks for your confirmation - I have worked around this problem. Cheers, David Carter-Hitchin. -- Royal Bank of Scotland Interest Rate Derivatives IT 135 Bishopsgate LONDON EC2M 3TP Tel: +44 (0)

Hello, i try to copy a specified directory and the according folders and files below to a remote host. cd /dir /usr/bin/rsync -ravz -e ssh --include='*/' --include='*/00/*/*' --exclude='*' . remote_host:/tmp i want to copy in these example the directory "00" and the according folders and files below. the structure of the directory is defined by a software and

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