similar to: testfoobar

Hi, This is probably way far unsupported, but here goes: I had been running ext3 0.0.3b for a while and found that I wanted to convert back to ext2 so I could still play with 2.4test kernels. Here is what I did: 1) boot the machine with kernel args init=/bin/bash 2) run debugfs on the root partition to remove the have_journal ext2 feature flag. 3) remount the root filesystem rw as ext2

Greetings, I'll keep this as brief as possible: Is Redhat going to support ext3 or reiser (or both) in the next version of Redhat (I'm not looking for a commitment, just a roadmap)? I noticed (and used) the reiser utilities in the Wolverine beta (on a test box) to make reiser paritions, but upgrading to the 7.1 release failed as it only saw ext2 partitions. I understand that ext3 is

There hasn't been any mailing list activity for almost a week. Is it that we are all happy and just waiting for meta-data journaling? -- Keith Barrett Red Hat HA Team

Hi upon booting this morning (Redhat 8.0), i received this error message Nov 17 02:55:07 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_find_entry: bad entry in directory #1111941: inode out of bounds - offset=36, inode=537868397, rec_len=12, name_len=4 I've also had these messages too Nov 3 20:25:42 jaguar kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } Nov 3

Hi RedHat 7.2, ext3 on /, kernel 2.4.18p1. whilst updatedb was running, i had these messages appear... Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory #147553: rec_len %% 4 != 0 - offset=0, inode=1651076143, rec_len=19527, name_len=85 Jan 6 22:18:42 jaguar kernel: EXT3-fs error (device ide0(3,3)): ext3_readdir: bad entry in directory

Is there any more docs on this other then the blurb on beta.redhat.com? I got a spare non-critical victim err... test machine I want to try this on and have all the RPMS, but would really like to chew on a little more detail before I leap. Regards, Henri -- "People die." --The Cynic's Book of Wisdom

I'm using RedHat 7.2 with kernel 2.4.18-26.7.xsmp and root mount using ext3. And I have simple test.pl script: #!/usr/local/bin/perl open FILE, ">testfile"; while(1){ print FILE "Test.\n" or die $!; } It's died when the file size is 2147483647 and give error message: "File size limit exceeded" and I run "cat testfile testfile >>

On Tue, 24 Jun 2003 ext3-users-request@redhat.com wrote : >Send Ext3-users mailing list submissions to > ext3-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/ext3-users >or, via email, send a message with subject or body 'help' to > ext3-users-request@redhat.com > >You can reach the person

Hello! I'm using a CompactFlash as storage device. Since those CF cards only have limited write cycles (CF does wear-levelling by itself, but you don't want to write too many timet so the card) i was wondering by what a factor the journaling of ext3 increases the write accesses to the CompactFlash compared to ext2. Thanks a lot already for your help! Sincerely Chris Braun

hi everyone, i installed the ext3 fs on a test machine and tried to use quota on the ext3 filesystem. When i use the command quotaon /dev/hdb2 (the partition with the ext3 fs) i get the message: quotaon: using /home/quota.user on /dev/hdb2: Invalid argument. I created the quota.user and quota.group files and set the permissions to 600. I use quota-2.oopre3-7a, e2fsprogs-1.20-0ext3, kernel 2.2.18

Hi. I have shifted from redhat 7.1 to 7.2, and have several machines running both versions now. I have noticed, that the memory usage patern is very different on machines using ext2 and ext3 - the ones using ext2 usually use 5-10 MB of "buff" memory, but the ones with ext3 grow to 50MB on machines with 128MB, and to 250MB with on machine with 512 MB. I have conducted a test, and changed

Hi, I'm having a problem with ext3 on my system. I'm running 2.4.13 with the appropiate ext3 patch and a software raid array with paritiions as shown below: Filesystem Size Used Avail Use% Mounted on /dev/md5 939M 237M 654M 27% / /dev/md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G

Has anyone experienced a significant degradation in ext3 performance when using it on a Multi-TeraByte RAID? As part of an experimental setup, I hooked up three 300GB drives and made an EXT3 RAID5 out of them, using the entire space one each drive, and started throwing a large number of files in the size-range 3KB to 50 KB. Then, I deleted the raid, and created a new one, but this time, I used

Hi, I''m a long ext3 user (rpmfind.net). I propagated ext3 on some of our server box (W3C webservers are ext3 based too now). I might be tempted of testing out your kernel RPMs but unavailability or the source RPM and the SMP version are definite showstoppers. Please provide them. In the meantime I will stick to my own set of kernel ext3 RPMs at ftp://rpmfind.net/pub/veillard/ext3/

New EXT3 Packages have been uploaded to ftp.beta.redhat.com today. We have expanded the packages offering by popular request :-) You may download these packages via anonymous ftp, or via the web page at http://www.beta.redhat.com/. BUGS Bugs against these packages should still be posted at bugzilla.redhat.com Product: Red Hat High Availability Server Version: beta Component: ext3

I am testing EXT3 as a filesystem for a server whose power supply is failure prone. In order to do the test, I have a lever that I can control from PC1 that can press the reset button on PC2. PC2's reset button is automatically pressed once every 120 seconds (the boot sequence on PC2 takes 80 seconds). While PC2 is booted, PC1 directs email and web requests at PC2, so that the PC2 disks are

I post a patch for comment on ext2-devel for the NFS cookie bug. Did not get any feedback yet. As Ted suggested, it set the cookie to -1 on EOF, even though it is not seek able to there. I only test it with Stephen's "readdir.c". Not have chance to run it on a NFS server yet. Do you have more information about the cache trashing bug? Regards, Chris ===== dir.c 1.5 vs edited

Hello, all. I work with lvm ( kernel 2.4.17 + ext3-2.4-0.9.17-2418p3 patch ) but i can't snapshot a ext3 fs directly # lvcreate --snap --name snap --size +1G /dev/vgtest/lvtest # mount -o ro -t ext3 /dev/vgtest/lvtest /snap /mnt/snap ext3 can't work , ext2 work If I mount readonly the etx3 filesystem, snapshot-it, and remount rw the filesystem ( and ro the snapshot ) it work

Hi there, I'm using RH7.2 (with the 2.4.9-30 kernal and it's required components) as a base for a server system running kernel 2.4.18. I've gone to this version to get around non-performing aic7xxx drivers in the stock 7.2 kernels, and updated gigabit ethernet drivers. I have a raid unit (Medea) attached to an Adaptec 3916, coming up as sdb. It has 2kb blocks, but the fault

Hi. I have shifted from redhat 7.1 to 7.2, and have several machines running both versions now. I have noticed, that the memory usage patern is very different on machines using ext2 and ext3 - the ones using ext2 usually use 5-10 MB of "buff" memory, but the ones with ext3 grow to 50MB on machines with 128MB, and to 250MB with on machine with 512 MB. I have conducted a test, and changed