similar to: ext3 filesystem corrupt. Which files are affected?

Hi, I have an ext3 file system on top of LVM and i use journaled mode. I would like to make a snapshot of my filesystem while the application is running in order to backup on another physical storage. For that i have to create an LVM snapshot and then to mount it in read-only for copying the content. This is not possible as far as ext3 needs to do a log replay at mount time ( AFAIK). I would

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

Hi folks, I'm in really big trouble with ext3. At about every second reboot I have files changed on my ext3 filesystem! In most cases I realize that sshd didn't start, and after examination I found that /usr/sbin/sshd or /lib/libutil-x.y.so changed. But when I reboot, everything seems OK. I looked once into the binary, and find parts of syslog in it!!! Horror! And this is a ususal

Several times recently my "mutt" email program has looped for hours at a time in the middle of a sys_ftruncate call. This happens when I use the "$" command to write changes out to my mailbox. It does eventually return from the call and everything seems to have worked ok. But in the meantime the CPU is pegged, $MAIL is locked so I can't receive new mail, and signals to

Hi. One of my ext3 partitions seems to be broken. But the problem is: fsck doesn´t recognize or repair the broken filesystem. But first let me tell how it is broken. There are some files that seems to be broken. for example /etc/resolv.conf in this case. Now, if I´ll try to read /etc/resolv.conf I get a error that /etc/resolv.conf doesn´t exists. But "ls" and so on list the file. I

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

In August I reported a problem with the sys_ftruncate call that caused me to reboot my machine. I didn't see any responses to it then on the ext3 list, and the problem is now recurring, so I thought I'd try again. I don't think I've rebooted since the last problem. In the last few days it hasn't taken as long as 17 hours, but it has sometimes taken unusual and uncomfortable

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

Hi, A problem with EVMS and Xen: I have patched a 2.6 kernel with the evms patches and then with the Xen patched, compiled and installed it. (kernel is 2.6.11.9 - which is what this server has been running for the past few months w/o the evms patches) At first everything seems to work just fine, I am able to use evms to create a new "volume", in this case it is based on MD/RAID-5 but

I have a Fedora Core 3 system at home, that was running fine, but now won't boot. Someone shut the power off on it without doing an orderly shutdown, and also I sometimes apply patches with "yum -y update" without doing a reboot immediately afterward - I suppose either of these could be related to my system not booting. I have a lot of information about the early stages of the

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

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

Doing a cursory Google scan on journaled Linux filesystems, it seems that the three ground-up journaled FSes: XFS, reiser and JFS all have their separate strong points but all compare favorably. Reiser does a better job with many small files...which would seem to be the reality of maildir formatted inboxes. Any comments on that? Any war stories, that is, any comments on reliability,

Peter Nelson wrote: > Hans Reiser wrote: > > >Are you sure your benchmark is large enough to not fit into memory, > >particularly the first stages of it? It looks like not. reiser4 is > >much faster on tasks like untarring enough files to not fit into ram, > >but (despite your words) your results seem to show us as slower unless > >I misread them.... >

I am testing EXT3 as a filesystem for a server whose power supply is failure prone. In order to do the test, I have a lever that I can control from PC1 that can press the reset button on PC2. PC2's reset button is automatically pressed once every 120 seconds (the boot sequence on PC2 takes 80 seconds). While PC2 is booted, PC1 directs email and web requests at PC2, so that the PC2 disks are

Hi, I just tried the 2.6.22-r1 candidate to test whether some bug I have hit in the past still exists. I did use 2.6.20.6 so far. So, I have cleanly rebooted to use the new kernel, after the machine came up I tried to mess with the bug, and had to reboot again to play with kernel commandline parameters. Unfortunately, on the next reboot fsck was schedules on my filesystem after 38 clean

Hello everyone, I'm new to the list and I hope I'm not repeating something that was already asked for. I had been using the stock kernel that came with Mandrake 8.1 which is kernel 2.4.8-26mdk (not sure what things are applied to a stock 2.4.8) I have my root partition /dev/hda1 on ext3 Mandrake took care of all this, by putting the ext3 module in initrd. I just dl'ed 2.4.13

-------- Original Message -------- Subject: Re: [Centos] is centos3.1 compatible with dag's el3 repo? Date: Thu, 26 Aug 2004 10:15:22 +0200 From: sophana <sophana78 at yahoo.fr> To: Dag Wieers <dag at wieers.com> References: <412B3E8B.7020805 at yahoo.fr> <Pine.LNX.4.61.0408241519120.6016 at horsea.3ti.be> Dag Wieers wrote: >Correct me if I'm wrong, but

Hi! I'm justing in the process of setting up a new fileserver for our company. I'm installing CentOS 5.3 (64 bit) on it. One of the "problems" with it is that it has a 3.5TB filesystem for the user data which I formatted during setup as an ext3. Now my experience with our current fileserver is that a 0.5TB ext3 filesystem needs approx half an hour to complete (and kicks in

I've turned my root filesystem to ext3 and also changed the filesystem type in /etc/fstab. I initiated a powerfailure and watched booting. But the kernel mounted root filesystem first read only as ext2 and does than a fsck for ext2. The over partition, /boot and /vol1 (also ext3), are handled as ext3. After booting all partitions, also /, were mounted as ext3. But why root is checked as ext2?