similar to: Probs with the Superblock

Hi again, I have the following scenario: I've got a partition which has exactly 14659312 blocks: $ fdisk -l /dev/hda Disk /dev/hda: 28.5 GB, 28520497152 bytes 255 heads, 63 sectors/track, 3467 cylinders Units = Zylinder of 16065 * 512 = 8225280 bytes Ger?t Boot Start End Blocks Id System (...) /dev/hda4 1643 3467 14659312+ 83 Linux (...)

On 09/20/2014 12:07 AM, Andreas Dilger wrote: > On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@gmail.com> wrote: >> I am reporting this on the advice of the Fedora Users Mailing List Member. >> >> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. >> >> I am reporting this per

Hi, hoping that someone on this list can help me here is the Problem. After a crash it seems the journal could not be recovered. This is what mount gives: root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt mount: wrong fs type, bad option, bad superblock on /dev/hdb2, or too many mounted file systems and this is the corresponding logfile-entry: Nov 27 11:16:13 wuehlkiste kernel: attempt to

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

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

On 2013-08-29, at 7:48 PM, Richards, Paul Franklin wrote: > Strange behavior with fsck.ext3: how to remove a long orphaned inode list? > > After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting

Hello, sorry if the question was asked a couple of times before but I couldn't find any useful hinds to this problem using google and the listman search-engine of the archive of this list. Somehow the ext3 filesystem on one of my machines died an after a reboot grub wouldn't come up again. What I did so far: fsck -y /dev/hda4 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004)

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

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 using the

i posted on rhel list about proper creating of 6tb ext3 filesystem and tuning here.......http://www.redhat.com/archives/nahant-list/2006-November/msg00239.html i am reading lots of ext3 links like...... http://www.redhat.com/support/wpapers/redhat/ext3/ http://lists.centos.org/pipermail/centos/2005-September/052533.html http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html ............but

Hi Ted and all, I have a couple of questions near the end of this message, but first I have to describe my problem in some detail. The power failure on Thursday did something evil to my ext3 file system (box running RH9+patches, ext3, /dev/md0, raid5 driver, 400GB f/s using 3x200GB IDE drives and one hot-spare). The f/s got corrupt badly and the symptoms are very similar to what Eddy described

Hi Guys, When I try to create an ext3 journal on a new fs, I receive the following error. This is all under Kernel v2.4.17 and e2fs tools v1.25: File size limit exceeded Running e2fsck on it afterwords gives: e2fsck -y /dev/sdc1 e2fsck 1.25 (20-Sep-2001) Superblock has a bad ext3 journal (inode 8). Clear? yes *** ext3 journal has been deleted - filesystem is now ext2 only *** Superblock

I used ddrescue to copy /dev/md1 to a disk of sufficient size, and re-ran e2fsck, and still get the error message that there's no root file system (I've tried most every superblock): # fsck -y -b 7962624 /dev/sdf fsck 1.36 (05-Feb-2005) e2fsck 1.36 (05-Feb-2005) Superblock has a bad ext3 journal (inode 8). Clear? yes *** ext3 journal has been deleted - filesystem is now ext2 only ***

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,

Hi, I zero-filled first 10MiB of my SSD(dd if=/dev/zero of=/dev/sda bs=10M count=1). As expected, this wiped my primary GPD header and first partition. Before the wipe, GPT was following: Disk /dev/sda: 250069680 sectors, 119.2 GiB Logical sector size: 512 bytes Disk identifier (GUID): 2EFD285D-F8E6-4262-B380-232E866AF15C Partition table holds up to 128 entries First usable sector is 34, last

Hello, I come to you beacause i have something that i dont understand : i m using udev on a debian sid with 2.6.15.1 kernel. I have created an deprecated raid at /dev/md0 when i tried doing mkfs.ext3 /dev/md0 i have got : mke2fs 1.39-WIP (29-Mar-2006) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 4643968 inodes, 9277344 blocks 463867 blocks (5.00%)

Hi all I am having some trouble using the ext2online utility, I have reduced the problem down to its simplist form, and it goes soemthing like this: Start with a regular msdos labelled disk (I have tried lvm volumes): Command (m for help): p Disk /dev/sdb: 18.3 GB, 18351967232 bytes 64 heads, 32 sectors/track, 17501 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot

Hi I work on this harddrive for 3 days now ... I had noticed errors in kernel while working on a harddrive (120 gigas) but all continue to work fine (archives/directory).. So i have unmounted the driver and try e2fsck... bad ! e2fsck 1.34 (25-Jul-2003) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/hdc1 So i have tried to create 1 image of this

I'm happy to announce the release of e2fsprogs 1.42. You can download the tarball from here: http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.42.tar.gz Or you can download it from the git repository on git.kernel.org. git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git. Or, you can wait for your favorite distribution to package it. :-) The release notes are attached

Hi there, For years I've been using the ext3 file system without to think that it can ever gets broken so bad. This was until last week when a box that I have running Linux from a SanDisk CF went down. Since then I am struggling with this CF trying to understand what is happening. The CF is SanDisk ultra II 1GB. On this I have 4 partitions all of them with ext3: boot / swap