similar to: information on block size in ext2

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

It's both in 2.6 and recent 2.6 (for RH ASS2.1 you'll probably need to copy the latest 2.4 defintion, but I don't care for obsolete junk). Index: src/super.c =================================================================== --- src/super.c (revision 1014) +++ src/super.c (working copy) @@ -799,7 +799,7 @@ /* get first two blocks */ for (i=0; i<2; i++) { - bhs[i] = getblk

In the bang head and repeat mode here. The live usb partition is /dev/sda1 Reboot / power on It auto mounts the /dev/sda2 as ext4 on /mnt/disc/sda2 $ umount /mnt/disc/sda2 $ mkdir /root/foo $ mke2fs /dev/sda2 $ mount /dev/sda2 /root/foo Kernel panic Snip from the kernel panic: ?????? list_del+0xb/0x71 cache_alloc_refill+0xf1/0x186 ext2_fill_super+0x0/0xa37 .... system_call+0x7e/0x83 --

Hello, When I am booting my gentoo domU I get the following output to the console and then it just hangs: (full boot output can be found at http://pastecode.com/19771) NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing

I must profane ignorance of complicated filesystem stuff, so feel free to call me out here. Booting a root ext3 drive produces the following message at boot: kinit: trying to mount /dev/root on /root with type ext2 EXT2-fs warning (device hda3): ext2_fill_super: warning: mounting ext3 filesystem as ext2 When remounted rw by init, everything looks fine: $ mount | grep hda3 /dev/hda3 on / type

Hi, I made an ext3 filesystem with 8kB block size: # mkfs.ext3 -T largefile -v -b 8192 /dev/md0 Warning: blocksize 8192 not usable on most systems. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=8192 (log=3) Fragment size=8192 (log=3) 148480 inodes, 18940704 blocks 947035 blocks (5.00%) reserved for the super user First data block=0 290 block groups 65528 blocks per group,

As part of adding support for OCFS2 to mount huge volumes, we need to check that the sector_t and page cache of the system are capable of addressing the entire volume. An identical check already appears in ext3 and ext4. This patch moves the addressability check into its own function in fs/libfs.c and modifies ext3 and ext4 to invoke it. Signed-off-by: Patrick LoPresti <lopresti at

When booting a CentOS4 domU, I''m getting some errors in the /etc/sysinit file. I''ve read that some edits are required in this file, but cannot find any specific references. Has anyone seen this before? Is there a workaround? EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel

Hello, I am trying to boot a FC6 domU on Xen 3.2 (compiled on a FC6 system). After compiling Xen 3.2 successfully on FC6 and making the ramdisk, I modified the conf.grub as shown below. With this, I was able to boot xen. ------------------------------ --------------------------------------------------------------------------------- # grub.conf generated by anaconda # # Note that you do not have

hello, Chris In the next several months, I will have a lot of spare time. I will be happy if you assign some work to me. I have learn linux kernel for years but only fix a few small bugs in IP stack. In the past few months, I read some EXT4/VFS codes. I began reading source of btrfs ten days ago and have read it twice now. Regards YZ

ocfs2_read_virt_blocks() does BUG when we try to read a block from a file beyond its end. Since this can happen due to filesystem corruption, it is not really an appropriate answer. Make ocfs2_read_quota_block() check the condition and handle it by calling ocfs2_error() and returning EIO. Reported-by: Tristan Ye <tristan.ye at oracle.com> Signed-off-by: Jan Kara <jack at suse.cz> ---

Another simple question. How do I calculate the size of the volume from the superblock? Do I just use the two fields: u_int32_t s_blocksize_bits; /* Blocksize for this fs */ u_int32_t s_clustersize_bits; /* Clustersize for this fs */ What is the formula to use? Thanks, John

Hi, I found one weird thing: I heard RAMDISK is not required for domU, but it seems I have to add RAMDISK to my domU config file, otherwiese the domU will hang up when it is booting. Please see the message below, the domU booting hangs up after "Continuing..." Does anyone have any clue for this issue? BTW, xen-friendly glibc is already installed. Thanks, Liang ---Begin of domU

From: Wade Cline <clinew@linux.vnet.ibm.com> This patch is only an RFC. My internship is ending and I was hoping to get some feedback and incorporate any suggestions people may have before my internship ends along with life as we know it (this Friday). The filesystem should mount/umount properly but tends towards the explosive side when writes start happening. My current focus is on

Fix "h_buffer_credits<0" assert failure during truncate. The bug occurs when the "i_blocks" count in the file's inode overflows past 2^31. That works fine most of the time, because i_blocks is an unsigned long, and should go up to 2^32; but there's a place in truncate where ext3 calculates the size of the next transaction chunk for the delete, and that mistakenly

ocfs2_queue_orphans() has an open coded readdir loop which can easily just use a directory accessor function. Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com> --- fs/ocfs2/dir.c | 28 +++++++++++-- fs/ocfs2/dir.h | 7 +-- fs/ocfs2/journal.c | 118 +++++++++++++++++++-------------------------------- 3 files changed, 70 insertions(+), 83 deletions(-) diff --git

hi, after rebooting my host, i can''t have anymore the networking: here''s my output of /etc/init.d/networking restart Reconfiguring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. done. cat

Hi Linus, Here are some 2.6.20 fixes for ocfs2. The patch by Zhen Wei isn't really a fix, but a very small amount of support for a feature which is mostly implemented in ocfs2-tools. Considering it's just a single attribute export via configfs, I'd say it's pretty safe to merge. Please pull from 'upstream-linus' branch of

Hi, I have uploaded ext3-0.0.5b.tar.gz to ftp.*.kernel.org:/pub/linux/kernel/people/sct/fs/ext3/test/ and ftp.uk.linux.org:/pub/linux/sct/fs/jfs/test/ New in this release is a functionally complete implementation of metadata-only journaling: data writes will no longer have to be written to the journal. Journaling still imposes some extra serialisation points between interacting processes, so

hello hpa, please pull git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for those changes: Kyle McMartin (1): klibc-utils: add dmesg maximilian attems (2): klibc comment fix fstype: add ocfs2 support with the following diffstat README | 2 usr/Kbuild | 2 usr/kinit/fstype/fstype.c | 15 +++++++