similar to: total block size

If I have an image of a filesystem taken with dd, I can look at it with a hex editor and discover that an ext2/3 superblock is at offset 1024 and I can figure out a lot of info about it. I cannot figure out, however, how the superblock differs from ext2 in ext3. I can't tell them apart... the "magic number" is the same as well as the "revision" field. If I have such an

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

This is CentOS-6x. I have cloned the HDD of a CentOS-6 system. I booted a host with that drive and received the following error: checking filesystems /dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000 blocks /dev/sda1: clean, 47/120016 files, 80115/512000 blocks /dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks

On Mon, Feb 16, 2015 at 6:10 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Feb 16, 2015 at 06:00:06PM -0500, Leonard Basuino wrote: > > Hope someone can point me in the right direction. I don't know if what I > > am trying to do should work or not. > > > > I have 2 disk images. One is a VM with an ext2 boot filesystem and ext4 > >

Hi Everyone, I have a server which has a raid array on /dev/sdb. After a crash I tried to mount the array and it failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or other error dmesg reports: EXT3-fs: invalid journal inode. I tried to run e2fsck and it failed (The output can be seen below). If anyone has any suggestions on how I can restore

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

On Wed, Feb 18, 2015 at 6:52 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, Feb 17, 2015 at 01:37:55PM -0500, Leonard Basuino wrote: > > I get the following debug info: > > > > mount -o /dev/sda1 / > > [ <time> ] EXT4-fs (sda1): mounting ext2 file system using the ext4 > > subsystem > > [ <time> ] EXT4-fs (sda1): bad geometry:

As per ext4 specification: > In ext2, ext3, and ext4 (when the 64bit feature is not enabled), the > block group descriptor was only 32 bytes long and therefore ends at > bg_checksum. On an ext4 filesystem with the 64bit feature enabled, the > block group descriptor expands to at least the 64 bytes described below; > the size is stored in the superblock. Since block group

Ok, I give up... I have to ask. This is CentOS 5. I switched one of my raid1 disks, and I already thought I had succeeded. But now it seems that something is very wrong with the first partition on the new disk. Luckily my system is fully bootable with the other disk. Here's some info. The new disk is sdb. // I removed all partitions with parted, and created the first one again. // parted

Hello, I compiled xen on ubuntu, but at the bot i got the kernel panic message. I enabled the support to ext4 fs. This is kernel panic error: EXT3-fs: unable to read superblock ETX4-fs (md0): unable to read superblock FAT: unable to read boot vector Kernel panic - not syncing: VFS: Unable to read superblock(9,8) My grub.cfg generated by update-grup: menuentry ''Ubuntu, with Linux

hi all, I intend to write a snapshot module for Ext2/3 file-systems. For that i need to make sure that FS is in consistent state before taking snapshot. For ex. in case of UFS, the superblock has a fs_clean flag which is set to be FSSTABLE to tell that its in consistent state. (otherwise its set to FSACTIVE) I m not able to find any such information for Ext2/Ext3. (The

Hi All, One of my servers upon a restart today comes up with an error checking filesystems: fsck.ext3: no such file or directory while trying to open /dev/VolGroup-1/Logvol00. /dev/VolGroup-1/LogVol00. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then

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

Hope someone can point me in the right direction. I don't know if what I am trying to do should work or not. I have 2 disk images. One is a VM with an ext2 boot filesystem and ext4 filesystems with the OS loaded. I am amble to guestmount this with no issue and am able to see the files that are on the ext2 file system. I can also run guestfish on the image, mount the ext2 filesystem, and

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)

steps to reproduce: ./run guestfish -N disk:1536M <<EOF part-init /dev/sda mbr part-add /dev/sda p 1 1048577 part-add /dev/sda p 1048578 2097154 part-add /dev/sda p 2097155 -1 mkfs ext2 /dev/sda1 mkfs ext2 /dev/sda2 mkfs ext2 /dev/sda3 EOF qemu-img create -f raw test2.img 1520M ./run virt-resize --format raw --output-format raw --resize /dev/sda1=-2M --resize /dev/sda2=-8M --shrink

When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files. If I do a df -h, there is no available space yet it shows that it has a lot of used space. The fstab shows the following: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 /

I got the following error message during the boot process: EXT3-fs: unable to read superblock mount:error 22 mounting ext3 flags Freeing unused kernel memory: 260k freed Kernel panic: No init found. Try passing init = option to kernel I was using RedHat 7.3 when this problem appeared. My machine is a ThinkPad R30 Intel Celeron 900 MHz. I used "linux rescue", to get access to my hard

Hello list. I have a perfectly working PV host, with this configuration: kernel = "/boot/vmlinuz-2.6.18.8-xen-3.3.0-7mdv" ramdisk = "/boot/initrd-2.6.18.8-xen-3.3.0-7mdv.img" root = "/dev/sda1 ro" extra = "(hd0)/boot/grub/menu.lst" memory = 256 maxmem = 512 name = "sexonthebeach" uuid = "f36962f5-0dec-4708-84a0-f5b4dea48d34" disk = [

Hi! I would like to know how well ext3/(ext2) will tolerate underlaying errors (I am planning to use loop-AES backed ext3 fs). So if there is 1024 bytes corruption of data what will be the worst case: - If this data belongs to some file, this part of data(file) has been lost? - If this data belongs to superblock, I have to repair ext3 and use another superblock? - If this data belongs to