similar to: problem with broken?! ext3 filesystem

hi, i have a tricky situation here and and don't know where to start with the solution. i happened to set up a linux system, but i had to install the base system on another machine. i used e2fsprogs 1.30-WIP (30-Sep-2002) for this. now the machine is up and running, but i have to use e2fsprogs 1.27 (8-Mar-2002). it's a debian system and i wanted to stay sane & stable, hence using

My UPS failed and my server took an 'unscheduled outage' a few weeks ago. The only casualty appears to be a volume I used for backup. I usually maintain data on multiple hard disks, but in this case I errantly had some data (of marginal value) on this file system. At this point, the data is not worth enough for me to send the drive out for data recovery, but it's worth enough to

Hi, I accidentally issued "mkswap" on a used ext3 fs partition (~30G) :-/ I have analyzed the behaviour of mkswap using two test files and it appears to only change "some" bytes: --8<-- --- swap2.xxd 2005-07-04 21:00:10.157261360 +0200 +++ swap1.xxd 2005-07-04 21:00:01.894517488 +0200 @@ -62,7 +62,7 @@ 00003d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, a good friend of mine had some trouble with his fs yesterday. i have some details now and wonder if you have some thoughts on it, even it may turn out not to be an ext3 issue at all. sorry, the post is a bit too long: the ext3 fs was running for several months now on a RAID controller. due to a user error, the RAID controller decided to rebuild

I noticed that ext3 filesystems are modified if mounted read-only: # mke2fs -j /dev/hdb1 [...] # md5sum /dev/hdb1 > MD5SUM # mount -t ext3 -o ro /dev/hdb1 /mnt/test1 # umount /mnt/test1 # md5sum -c MD5SUM md5sum: MD5 check failed for '/dev/hdb1' On examination of a block-for-block copy of 'before' and 'after' images with od and diff, I believe that the changes are

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

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

On Apr 29, 2004 14:15 +0200, David Mart?nez Moreno wrote: > Hello all. I'm writing to all the people in charge of ext3 fs > > Apr 29 12:21:21 arsinoe kernel: EXT3-fs error (device sda7): ext3_free_blocks: Freeing blocks not in datazone - block = 1071716394, count = 1 You need to run "e2fsck -f /dev/sda7" on the unmounted filesystem. There is some sort of corruption

Hi, Sorry if this is an old and fixed issue but I can't really seem to find a definitive explanation/fix to this in the mail lists. Ever since I upgraded to FC2 my server randomly decides that it can no longer access the disk and "aborts" the ext3 journal leaving it read-only as expected. I've seen the same errors on other mail list, explained away as disk or disk cable

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

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

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG:

I need to downgrade a system from Centos x4.2 to v3.6 (x86) due to performance problems with Arkeia Network Backup and AIT-4 tape drives. The backup database is stored on a v4.2 created ext3 partition. When accessing this partition after the downgrade, Centos complains on boot that fsck.ext3: Filesystem has unsupported feature(s) (/dev/sda5) *fsck: Get a newer version of e2fsck! [fail] If I

Peter Kjellstr?m wrote: > On Monday 23 January 2006 16:46, Plant, Dean wrote: >> I need to downgrade a system from Centos x4.2 to v3.6 (x86) due to >> performance problems with Arkeia Network Backup and AIT-4 tape >> drives. The backup database is stored on a v4.2 created ext3 >> partition. When accessing this partition after the downgrade, Centos >> complains on

Hi, after my X froze i had a fs inconsistency after the journal replay [...] EXT3-fs: 03:06: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 64k freed INIT: version 2.78 booting Loading /etc/console-tools/default.kmap.gz Activating swap... Adding Swap: 264560k

(I've already sent this message to Ted Ts'o directly. I should have sent it to this list first but I didn't know about it until today. My apologies to Ted.) Last Friday a system that I just inherited refused to mount a file system that had been working fine for about 6 months. This is on a Scientific Linux 4.3 system using a 2.6.9 kernel. This is another Linux distribution based on

I just came back after being out for the evening. Apparently there was a power failure long enough to discharge the UPS completely on my Linux box. After powering back up, I received notice that the / filesystem needed "manual fsck"ing. I booted off CD and attempted to fsck. Unfortunately, everything I've tried has proved futile and I'm _desperate_ for some help. I've

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I got an IDE-drive which decided to get broken. Part of the extended partition table was lost, but I was able to recover it, so I could reach the ext3 filesystem with a size of about 135 GB. I made a copy of it (luckily the ISP doesn't seem to need the broken drive urgently hehe) and ran fsck on that copy. The first time I ran fsck I