similar to: [Documentation] add ext3.txt

Hi. While reading Documentation/filesystems/ext2.txt I noticed that the information about ext3 is outdated: The ext3 code is currently (Apr 2001) available for 2.2 kernels only, and not yet available for 2.4 kernels. Journaling (ext3) ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/ The file was touched when I applied the 2.4.7 patch from Linus, so I suspect it's maintained. --

I have ext2 compiled in the kernel (so i can mount the initrd image), all other filesystems are modules. The initrd image contains aic7xxx, jbd, and ext3 modules. /etc/mtab reports the filesystem mounted ext3 /proc/mounts reports it mounted ext2 /proc/filesystems lists ext3 If I umount other partitions that are ext3 the module becomes 'unused'. The filesystem was created

Hi, I am a student in computer science and I develop a program that tries to explain other students the mecanisms of the ext3 filesystem : we show the content of each structure and explain what it means. But I was unable to find a developper documentation for the jounalizing functionality (jbd). Could you please tell me where can I find one ? ( in english or in french ) Also a documentation

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

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

Hi, We will have to go and use SuSE (30 servers) just because ext3 filesystem cannot be increase while the filesystem is mounted. I Don't understand why RedHat do not support filesystems that can do thing that ext3 cannot do. When is RedHat going to understand that in a production environnement (30 servers that is seems will be SuSE) we need extend filesystem online. IBM JS,

Hello: We trying to configure one machine (Compaq Proliant ML760) with 8 disks (72GB each disk) with RAID. We are thinking to use ext3 and LVM in RedHat 7.2 for manage one filesystem with 500GB. This filesystems have to store near off 5.000.000 of files. Is this possible? Could I resize the filesystems/volume to 1TB? what are the ext3 and LVM limits? someone have tested sismilar environment? I

Greetings all, I am curious if anyone knows why utilities such as 'GNU shred' (part of coreutils) and 'wipe' say they are not effective on journalled file systems- especially EXT3. Is it because you can't "guarantee" that the journal has been flushed/wiped (i.e. you have the journal 'between' you and the actual data blocks on the physical disk), or because

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

After a rather severe hard boot, my machine refuses to mount homes, which are on an ext3 partition. Here is the error i get while mounting... # mount /dev/sdc1 EXT3-fs: invalid journal inode EXT3-fs: get root inode failed mount: wrong fs type, bad option, bad superblock on /dev/sdc1, or too many mounted filesystems However I am able to mount it as ext2 and continue. I am using ext3-0.0.6b on

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

Hello, I search through but I didn't find a clear answer about it. I have a rh 6.2 based box where I made many steps of upgrades. Some of them, not being available the binary rpm glibc 2.1 based, I obtained using src.rpm from rh 7.2 and then runnig #rpm --rebuild package.src.rpm and then installing the generated binary: great sw rpm!!! My rpm version is 4.0.2-6x for both rpm, rpm-devel,

My system is RH7.2 with custom 2.4.18 or 2.4.19 kernel(s), downloaded from kernel.org. My root filesystem is ext3 on ataraid. I'm using initrd. My system comes up fine with 2.4.18 kernel, but when trying to boot a new 2.4.19 kernel I get the following sequence:

Hi, ext3-0.9.18 is now available for 2.4.19-pre8. Some of the fixes in this release are already in the 2.4.19-pre8, but there are some important new fixes in the patch and users are encouraged to upgrade. This release fixes all known outstanding bug reports. The full patch against linux-2.4.19-pre8, and a tarball of the individual fixes in this patch set, is now propagating to

Consider this section: http://www.tldp.org/HOWTO/Software-RAID-HOWTO-4.html#ss4.14 I have not done this before and I'm leary about Step 11 which is resizing the filesystem after doing a mkraid command. This howto lacks any ext3 documentation. Some questions I have are: 1. Should I convert back to ext2 on all my filesystems before I do a mkraid? 2. If I leave the system at ext3, will the

After approx. two weeks of uptime. This host always has some network activity, and when it happened, it was either running or had just finished making backup of about 1200MB (from few ext3 to one ext3 filesystem). kernel was still alive to network pings and services responded, but trying to ssh failed (just hanged there before opening session but after giving last login info). telneting to pop3

I noticed that ext3 filesystems are modified if mounted read-only: # mke2fs -j /dev/hdb1 [...] # md5sum /dev/hdb1 > MD5SUM # mount -t ext3 -o ro /dev/hdb1 /mnt/test1 # umount /mnt/test1 # md5sum -c MD5SUM md5sum: MD5 check failed for '/dev/hdb1' On examination of a block-for-block copy of 'before' and 'after' images with od and diff, I believe that the changes are

Hi, If the ext3 file system maximum size updated or it is still 4TB for 2.6.* kernel? The site at http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html says that it is 4TB yet, but I would like to know if it is possible to create and use stable & easy-to-fix (or at least as stable & easy-to-fix as ext3) file systems as big as 100TB for 32 bit Linux architecture? Any experience

Is there a document anywhere offering guidance on the optimum use of ext3 filesystems? Googling shows nothing useful and the Linux ext3 FAQ is not very forthcoming. I'm particularly interested in: 1. The effect on performance of large numbers of (generally) small files One of my ext3 filesystems has 750K files on a 36GB disk, and backup with tar takes forever. Even 'find /fs -type

Hi, We have upgraded our server with RedHat 7.2 and changed the filesystem for the new Ext3 format. Since then we are having troubles with NFS and Samba file systems. Our server export directories to Windows clients through Samba and to other Linux (RedHat 7.2) through NFS. It is also connected through NFS to a RedHat 7.0 server. Since we changed for Ext3 filesystems, we experience to main