search for: ext2_fill_super

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

...e. 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 -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100...

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 unused kernel memory: 108k freed The dom0 is CentOS 5.2 and xen is version 3.1 I have tried all manner of things and have no idea how to get this working. Here is my xen config file. > kernel = "/bo...

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 ext3 (rw) However, I am unsure if the klibc warning has the potential to cause any problems. Using rootfstype=ext3 gets rid of this error, but it'd still be ni...

...blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 22 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. When mounting it as ext2 (by mistake), the kernel says: EXT2-fs warning (device md0): ext2_fill_super: mounting ext3 filesystem as ext2 When finally mounting the filesystem as ext3, the kernel says: kernel: EXT3-fs: Unsupported filesystem blocksize 8192 on md0. I don't quite understand: About any larger filesystem of today can support blocks > 4kB. What is the problem here? Kernel is 2.6...

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 memory: 184k freed unix: no version for "struct_module" found: kernel tainted. NET: Registered protocol family 1 INIT: version 2.85 booting /etc/rc.d/rc.sysinit: line 28: /dev/null: Read-...

...d: registered block device major 8 blkfront: sda1: barriers enabled XENBUS: Device with no driver: device/console/0 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 196k freed Kernel panic - not syncing: Attempted to kill init! ----------------------------------------------------------------------------------------------------------------- It would be...

...tables configured (established 131072 bind 65536) TCP reno registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 8 NET: Registered protocol family 20 Using IPI No-Shortcut mode EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 172k freed Warning: unable to open an initial console. *************************************************************** ***************************************************************...

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

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

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

Hi folks, Host - Debian Etch Guests - Debian Etch. Performed following steps to create duplicate guest, a mail server. 1) # cp /etc/xen/guest-1.cfg /etc/xen/guest-2.cfg edit guest-2.cfg changing the settings of:- disk = [''file:/vserver/domains/guest-2_directory/disk.img,hda1,w'', ''file:/vserver/domains/guest-2_directory/swap.img,hda2,w''] # Hostname name

I am setting up Xen for the first time and have run into a problem. My system was initially setup with Fedora Core 4. I was able to successfully create a File-backed VBD. When I boot the domain,I get an error message that is listed at the end of the below boot messages. I suspect the problem is casued by my fstab. However, I am not sure how it should be configured. Fstab listed also. Any pointers