Displaying 20 results from an estimated 3000 matches similar to: "2.4.14 + latest patch != ext3 support"
2001 Nov 07
0
(no subject)
> Hello,
Hi!
> I just need a little clarification regarding applying the ext3 patch
> to the latest kernel.
> I have 2.4.7-10 that came with RH 7.2.
> I have ext3 running.
> I need to upgrade those (to get some USB device working).
> So I got the latest kernel, 2.4.14, patched it with the ext3-2.4-
>0.9.15-2414 patch, picked ext3 from 'make xconfig', built the
2001 Aug 14
8
Redhat Roswell
Hi all
i installed Redhat beta Roswell, then i updated to Kernel 2.4.8
patched him and installed the newest util-linux + e2fprogs without any
custoumized Options. Bootloader is Grub. Now when i boot he says mount -O or -0
is an invalid Option. tune2fs -j /dev/hdXX says "The filesystem already has a journal"
lsmod says that no jbd or ext3 Modules is loadet but i have pachted the Kernel
2005 Feb 04
2
Failures they e2fsck doesn't find
Hi,
I've run many time e2fsck, but in a special dir ls tells me:
ls: r?cksendung-wlan.dvi: No such file or directory
ls: baf?g_r?ckmeldung.latex: No such file or directory
ls: finpr?f.pdf: No such file or directory
$ cat finpr?f.pdf
cat: finpr?f.pdf: Datei oder Verzeichnis nicht gefunden
I don't know what to do? How can I find the failure? If I cat the files
with debugfs, I see the
2001 Nov 07
3
Problem with 2.4.14 and 9.15-2414
I just upgraded to kernel 2.4.14 and applied the ext3 patch
ext3-2.4-0.9.15-2414.gz. It appears (to me) that the patch
breaks the loop block device module (loop.o). The problem is
that the call to deactivate_page is unresolved. The routine
used to be defined in swap.c. It looks like it no longer
exists in 2.4.14.
I'm not a kernel programmer so if I'm mistaken, sorry. I do
get an
2005 May 15
3
Intermittent ext3 corruption on external firewire Micronet 1.5Tb RAID on FC3
Hi
I have a Firewire connected Micronet 1.5TB RAID with a single
large ext3 filesystem on one partition on a dual Xeon system.
I am checking out from an extremely large cvs repository
(don't ask) to this drive over the course of many days, and
intermittently I get bad blocks and the filesystem goes
read-only. This is not related to any power failure or
anything similar. The RAID is currently
2001 Oct 30
2
a silly question
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
just wondering... if i upgrade my kernel + ext3 patch, do i have
to recreate the journal? if so (or if not) how do i recreate it? i tried
to delete the .journal, reboot and mounting everything as ext2 and do a
tune2fs -j /dev/hdxx but it say "The filesystem already has a journal."
Thanks,
Mark
-----BEGIN PGP
2001 Jun 01
2
ext3 and 2.4.5: OK, but how to convert / ?
Hi. I just installed ext3 for 2.4.5 from
http://www.uow.edu.au/~andrewm/linux/ext3/ but couldn't find
anything about converting my root partition to ext3. 2
partitions are now ext3 after I umount and tune2fs, but what
should I do with / ? I tried init 1 and umount, but tune2fs
would fail because it was on read-only fs.
Another question is if I can now build ext2 as a module, and
if it's
2001 Nov 07
2
Ext3, Raid5, and Quotas on 2.4.14?
I remember that there used to be a problem with disk quotas on Ext3 and
Raid5 on the 2.4.x kernel series. I am running 2.4.14 with Ext3 and
Raid5 and am having problems with quotas and am wondering if I have
something misconfigured or if this combination doesn't work yet.
--
Daniel R. Bidwell | bidwell@andrews.edu
Andrews University Information Technology Services
If two always agree, one of
2001 Nov 16
2
ext3 patch files
Hi, i'd like to upgrade my kernel to 2.4.14.
I've obtained the corresponding kernel patch from http://www.zip.com.au/~akpm/linux/ext3/ however when I run
gunzip < ~/ext3-2.4-0.9.15-2414.gz | patch -p1
I am told that this file is not in gzip format.
This is based on the file and instructions on ext3 for 2.4 site. Am I missing something?
cheers
Simon
2001 Nov 04
3
2.4.13 kernel on Redhat 7.2
I have tried everything to compile a new kernel on my
7.2 base system. I have used 2.4.13-ac6 and 2.4.13 w/
ext3 patch. I have compiled with ext3 built-in and
with ext3 as module (with the initrd). I have a SCSI
system so I have done the previous variations with
both SCSI support built-in and modular (with the
initrd). The error I get is:
Remounting root filesystem in read-write mode: mount:
no
2001 Nov 01
3
ext3 partition still gets mounted as ext2 for me too!
Hi,
I am a new ext3 user and I am having problems similar to what many
people are facing on this list.
I have done everything as the emails suggest. I am using SuSE 7.3 with
the the 2.4.10 kernel and ext3 compiled as a module. Because it is
2.4.10 kernel, I created all my journals from a rescue disk and
everything seems to be working right for the non-root filesystems. My
fstab has all my
2014 Jan 02
1
Simple question on USB flash drive naming
I have a USB key that when inserted into a port on my CentOS-6.5 system
maounts as this:
/dev/sdb1 /media/22d773e3-8502-4196-b45f-388380dcee48 ext2
rw,nosuid,nodev,uhelper=udisks 0 0
What is the mechanism to give this thing a more human usable mount name /
volume name?
Mounting this USB key with what I guess is a UUID in place of a name was not
always the case. My sense is that the change in
2002 Jan 03
4
ext3 crash after RedHat 7.2 installation
Hi everyone,
I've been running Redhat 7.2 (new install) for about 2 weeks now
without any problems, but today I was not so lucky.
My system hung while I was trying to configure the kernel-source RPM using
'xconfig'.
After rebooting the system, it seems that my whole ext3 file system is
corrupted.
I get the message:
Mounting root filesystem
EXT3-fs: ide0(3,3):couldn't mount
2006 Aug 02
1
Free space oddities on OCFS2
Hi all,
I'm testing OCFS2 as a cluster filesystem for a mail system based on maildir, so basically the filesystem must be able to deal with lots of directories, and lots of small files.
The first "oddity", is that when I mount a newly formated ocfs2 fs, it already contains used space:
[root@ocfs1 /]# df /cgp02
Filesystem 1K-blocks Used Available Use% Mounted on
2005 Dec 14
2
Problem with dir.create (R2.2.0 Windows XP 2002 SP 2)
I've run into a problem with dir.create on R2.2.0 Windows XP 2002 SP 2.
setwd("d:/")
print(dir.create("d:\\otis-sim\\rdata", recursive=T))
print(dir.create("d:\\otis-sim\\", recursive=T))
Both return false and fail to create the directories.
setwd("c:/")
print(dir.create("d:\\otis-sim\\rdata", recursive=T))
Returns true and succesfully
2002 Jul 11
1
(no subject)
Which version should I use out of the list? Or do I install all of them, one after the other?
ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog)
ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9)
ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog)
patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))
2001 Nov 26
1
EXT3 crash: ext3_free_blocks: bit already cleared
I had a failure over the weekend of
my ext3 filesystems.
Hardware:
Dell 2550 (dual PIII 1 Ghz, 1GB ram, Acenic GigE card)
Software:
linux-2.4.14
ext3-2.4-0.9.15-2414
Trond's NFS patches (pathconf, tune,read,rpc_blk)
The filesystem is RAID0 using LVM (1.0.1-rc4).
The disks are connected using fiber channel
(qlogic 2200, qlax00-4.27beta).
I was generating high load on my nfs
2001 Oct 14
1
auto in fstab does not work
[This email is either empty or too large to be displayed at this time]
2002 Feb 25
2
3com mba 4.30 problem
Hello All,
I seem to be having a problem with PXE under the 3com MBA
once the pxe loads the standard redhat 7.2 lilo prompt and
I type my label which is a4-72 and hit enter, I get:
Loading vmlinuz...
and it stops most of the time. Sometimes it loads and once it gets to
the part of installing linux the screen turns red and I
get "interrupt handler not syncing"
Thanks
--
Otis DeWitt -
2007 Jul 14
2
's' extension Asterisk 1.2.18
how can I fix this just started ......
Jul 14 14:32:35 NOTICE[4983]: chan_zap.c:6223 ss_thread: Got event 18
(Ring Begin)...
== Starting Zap/1-1 at bell,s,1 failed so falling back to exten 's'
== Starting Zap/1-1 at bell,s,1 still failed so falling back to
context 'default'
Jul 14 14:32:35 WARNING[4983]: pbx.c:2377 __ast_pbx_run: Channel
'Zap/1-1' sent into invalid