search for: superblock

Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal usi...

I've been trying to use fsck to recover a corrupted filesystem. It appears the original superblock is corrupted too, as it has an inode count of 0. When I start fsck with -b 32760, it uses the alternate superblock and proceeds. However, it restarts from the beginning a couple of times and after the second restart it doesn't use the alternate superblock, stopping instead as it can't fin...

...ech Republic). We use LLVM for many >> projects and actually we want to create system, which will be able >> compile and profile aplication for VLIW processors in few iterations. >> We want to load profile information in 'opt' part of LLVM and use it >> for create superblocks. Note, when superblocks will be created, we >> want to use llc for our specials backends. > > I suggest looking at the problem upside-down. What optimization do you > need to enable on superblocks, and how will changing the IR help? Any > single predecessor blocks laid out seq...

...chnology (university VUT in Brno Czech Republic). We use LLVM for many projects and actually we want to create system, which will be able compile and profile aplication for VLIW processors in few iterations. We want to load profile information in 'opt' part of LLVM and use it for create superblocks. Note, when superblocks will be created, we want to use llc for our specials backends. *.ll -> opt -> llc -> *.asm | profile information We are thinking about creating superblocks in two ways: 1. Simply join basic blocks and branch instrunction in th...

...hnology (university VUT in Brno Czech Republic). We use LLVM for many projects and actually we want to create system, which will be able compile and profile aplication for VLIW processors in few iterations. > We want to load profile information in 'opt' part of LLVM and use it for create superblocks. Note, when superblocks will be created, we want to use llc for our specials backends. I suggest looking at the problem upside-down. What optimization do you need to enable on superblocks, and how will changing the IR help? Any single predecessor blocks laid out sequentially looks like a superblo...

...(university VUT in Brno Czech Republic). We use LLVM for many projects and actually we want to create system, which will be able compile and profile aplication for VLIW processors in few iterations. >>> We want to load profile information in 'opt' part of LLVM and use it for create superblocks. Note, when superblocks will be created, we want to use llc for our specials backends. >> >> I suggest looking at the problem upside-down. What optimization do you need to enable on superblocks, and how will changing the IR help? Any single predecessor blocks laid out sequentially loo...

...onditional branches and returns are marked as terminators; the MIPS backend also marks conditional branches as terminators. The MachineBasicBlock then has a helper function getFirstTerminator which iterates from the first terminator to the end of the MBB. So it seems to me that an MBB is a kind of superblock, single entrance and multiple side exits. There are also TailDuplication and BranchFolding passes. While these two are technically not part of the superblock definition, they are usually part of a superblock implementation because you want a superblock to be as big as possible. Of course, you coul...

Hi all, While developing compile-time instrumentation for ThreadSanitizer (http://code.google.com/p/data-race-test) I need to generate SEME regions without loop and call instructions (I'll call them superblocks hereafter, although some researchers do allow loops in their definition of superblocks). This is necessary to get the largest piece of IR in which the memory operations can be enumerated in order to record the addresses of the memory accesses into a fixed-size buffer. So far I was using my home-...

I've got this poor ext3-partition which I can't access. I have tried a lot of things but it doesn't seem to solve the problem. I've got quite important files on that particular partition. I can't even get the block groups from my /dev/hda3 with dumpe2fs! It all happened after a crash. GRUB wouldn't give me the graphical UI. I decided I had to get my dosbootdisk and do an

...whose size may vary. > > Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. > > > > Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range, > > thus it can't exceed the limit, otherwise the superblock would be corrupted. Raphael/Paulo: does UFS2 have a hard 64kiB limit? I know it's not installed to the first sector where the first superblock is located. > IMNSHO is including core/ldlinux_limit.pl better > than waiting for a better core/ldlinux_limit.pl This should be rendered obsol...

...system, I first created a partition with EXT3 and put some data on it. Later, I deleted the partition, and re-created another partition with the same starting block number and a higher ending block number. I intended to format it with another filesystem, but surprisingly (or maybe just to me), the superblock of the partition had not changed. I could still mount the new partition as the same old filesystem. I could see all the files which was present earlier. Doing 'df' showed me the older partition details (size, % used etc.). Shouldn't the superblock be changed/deleted once the partition...

...d working after a power outage. Before I was using mount version 2.11n-7woody1 (the stock debian 'woody' version). I upgraded to the backports.org version of mount after this problem appeared, but it didn't help. The symptom is - # mount /dev/sdb1 mount: wrong fs type, bad option, bad superblock on /dev/sdb1, or too many mounted file systems (aren't you trying to mount an extended partition, instead of some logical partition inside?) My question to you is: where to look for help, if not here. Do I need to upgrade mount? fdisk? Am I missing a kernel module? I...

.../dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks /dev/mapper/vg_voinet01-LogVol04: clean, 770219/20480000 files, 34881086/8102000 blocks fsck.ext4: Bad magic number in super-block while trying to open /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log 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 the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsk -b 8193 <device>...

It recently occurred to me, as I was partitioning a RAID with fdisk, that when I built the system, I was presented with a graphical utility that "magically" created the partitions. Now, using fdisk, I was reminded of being given superblocks. Although I haven't used data recovery techniques using superblocks, is there a way to retrieve the superblock numbers the OS has assigned to a partition? Thanks. Scott

Hi all, Somehow I managed to mess with a RAID array containing an ext3 partition. Parenthesis, if it matters: I disconnected physically a drive while the array was online. Next thing, I lost the right order of the drives in the array. While trying to re-create it, I overwrote the raid superblocks. Luckily, the array was RAID5 degraded, so whenever I re-created it, it didn't go into sync; thus, everything besides the RAID superblocks is preserved (or so I think). Now, I am trying to re-create the array in the proper order. It takes me countless attempts, through hundreds of permutation...

Hello everybody, I am new to this list, so welcome everybody. Last 2 week I had two harddisk crashes with my ext2 file system. This is what sort of happed with both of the disk: I pluged in my USB to SATA converter in my harddisk that has an ext2 filesystem. I mounted the partition, went to a directory that had a DVD image. I mounted the dvd image in the same directory and started watching the

...l centos 6.8 to an i386 mid tower, during setup of hard disk partitions, selection is for /dev/sde. if continued, after reboot, error is displayed after 'welcome to centos'. lines read: Checking filesystem fsck.ext4: no such file or directory while trying to open /dev/sda3 /dev/sda3: 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 the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -h 8193 <device&gt...

...r (should it?). When i try to mount: EXT3-fs error: ext3_check_descriptors: block bitmap for group 0 not in group (block (block 152615462) EXT3-fs: group descriptors corrupted. of course i tried e2fsck (v 1.27), but it said it could not see an ext3 on the partiiton and suggested to try another superblock (here: 8193). hopes surging, but bad luck, because block 8193 is also within the deleted area. My question therefore is, if there are any (backup) superblocks on an arbitrary ext3 partiiton which i could access to recover some data at least. I tried the formula (8192*n +1), but bad luck.....i assu...

...a Fedora 24 disk that is using XFS.  This is the error messings I get when I try: root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestmount: '/dev/sda1' could not be mounted. Did you mean one of these? /dev/sda1 (xfs) Verbose output shows: libguestfs:...

...a Fedora 24 disk that is using XFS.  This is the error messings I get when I try: root@cpdev-cn5:/var/lib/libvirt/images/base# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/${target}1 /tmp/fedora-master/ libguestfs: error: mount_options: /dev/vda1 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestmount: '/dev/sda1' could not be mounted. Did you mean one of these? /dev/sda1 (xfs) Verbose output shows: libguestfs:...