similar to: how to tell ext2 from ext3 at byte-level?

Dewet Diener wrote: > > Hi all > > After umounting a removable ext3 partition from my work PC, and > trying to remount it at home, I've run into the following error > trying to mount it as both ext2 and ext3: > > EXT2-fs: ide1(22,65): couldn't mount because of unsupported optional features (10000). > EXT3-fs: ide1(22,65): couldn't mount because of

Hi, One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system. These are the first errors in the log: kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is

Hi folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000)

Enhance fstype so it properly takes into account whether or not the ext4 and/or ext4dev filesystems are present, and properly handles the test_fs flag. The old code also has some really buggy checks --- for example, where it compared the set of supported ro_compat features against the incompat feature bitmask: (sb->s_feature_incompat & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP) I

In an ext2/ext3 superblock, there is a total block count (the second 4-byte word), but it doesn't give me the same number as I get with the 'df' command. The numbers are close, but not exactly the same. What makes up for the difference? It's not the "reserved block count"... I checked that. Thanks! -Jeff Meininger

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 hpa, nothing too exciting, again syncing latest Debian upload and subsequent patch emails. plus wanting to get the ext4dev in line for the Lenny release. :) please review. thanks -- maks please pull git pull git://git.debian.org/~maks/klibc.git maks for the changes: Arthur Loiret (1): Makefile (ARCH): Support sh4 as sh. David H?rdeman (1): [klibc] mount: allow multiple fs

ext4 no longer requires a journal. Compare: http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commitdiff;h=a90f5391dda78f7bc4a8196a78355584ace0adf5 Signed-off-by: Colin Watson <cjwatson at ubuntu.com> --- usr/kinit/fstype/fstype.c | 8 -------- 1 files changed, 0 insertions(+), 8 deletions(-) diff --git a/usr/kinit/fstype/fstype.c b/usr/kinit/fstype/fstype.c index 69e0e30..bf63b1b

I am linking a program to be loaded in an ARM Cortex-M0+ based microcontroller. In the linker script, I have a section allocated for the stack which roughly looks like the following. .stack : { . += __stack_size__; } > ram Using the linker in the gcc arm toolchain, arm-none-eabi-ld, this section is automatically set to type NOBITS, however, when linking with version 10.0.0 of ld.lld, the

I often get the message: EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2 I have googled for a reason and a way to solve this - but not found something I could use. Maybe somebody here konws what to do? best regards keld

Hi guys, a user at Gentoo Bugzilla, reported that he archives files with a artificial timestamp of 1970-01-01 on an ext3 partition on his amd64 box. After remounting that partition, the file date becomes 2106-02-07. I confirmed this bug and also tested it on several other partitions (xfs, reiserfs) and they don't have this problem, just ext2 and ext3 have it. This problem also

Hi, I have installed Red Hat Linux 7.3 with ext2 file system and I have multiple partition. I converted them to ext3 using following command. tune2fs -j -i 0 /dev/hdaX And I modified /etc/fstab as below. LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts

Dear All Greetings. I have a question regarding ext3 file system. I have installed Red Hat linux 8 with ext2 file system and I have multiple partition. Now I want to convert them to ext3 file system without distrubing my data. If any one got the idea, please let me know. Thanks Muhammad Noman -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi! Is it possible to merge two ext3/ext2 partitions into ONE ext3/ext2 partition? -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt at charite.de Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916 IT-Zentrum Standort Campus Mitte AIM. ralfpostfix

hi all I want to know wt does s_log_blocksize represent in ext2's superblock structure in memory.. Is is 1024 for 1kb block size in ext2 file system.. Also wt does s_blocksize and s_blocksize_bits members of VFS superblock represent.. BTW are there any ext2 file system specific mailing lists.. bye a Linux lover

Can ext2 or ext3 filesystem manage sparse files? And so, in which way? Does it use extents? Thanks in advance. Daniele

Hello, I'd like to read superblock's information on Redhat 7.3, but I don't know how to do it. For example, Input : "/dev/sdj2" Output : ext2_super_block struct's s_wtime (I saw it at "/usr/include/ext2fs/ext2_fs.h") Input : "/dev/sdj1" Output : ext3_super_block struct's s_wtime (I saw it at

We are testing Red Hat Advanced Server 2.1. I have a simple benchmark program that issues synchronous writes/reads to a file. When I ran it on a file system that was created by default as ext2, the elapsed time was about 5 seconds. After using tune2fs to convert the file system to ext3, the same run took about 10 seconds. I've tried all three of the journaling modes and it doesn't seem to

Hello, I am using kernel version 2.4.7-10 I upgraded one of the ext2 partition to ext3. the partitions are nearly empty. I ran a program to create empty files, having names in lexicographical order. The time taken to create empty files (100 .. 100000) is same on an ext2 partition and a ext3 partition. Can anyone pls. tell me why there is no difference in the time taken. Is the htree algo.

Hi, I try to convert my RedHat 7.3. partitions from ext3 to ext2. I have found a thread dealing with this issue. Thus: "tune2fs -O ^has_journal /dev/foo" and "e2fsck /dev/foo" will do the magic! This works fine for "/boot" but when I try to convert "/" my kernel panics? The kernel panics message appears shortly after the attempt to startup kjournald. How