similar to: Corrupted journal on ext3 - improve e2fsck?

Hi I'm experiencing some problems on a harddisk (it has crashed for no known reason), and in pursuit of getting some of the data out of the disk I'm learning to use the e2fs progs package. Origianlly I used version 1.38, but after experiencing segfaults in e2fsck -which now is solved, I upgraded to 1.39, but now I have hit another problem (on another partition): The partition was

Hi I was running few tests on the Ext3 filesystem having an external journal; basically trying to check recovery in crash scenarios. I started with simple scripts doing some filesystem operations on the ext3 partition and crashed the system with a direct poweroff. On reboot, I also corrupted the journal device by "dd"ing it out with blocks of zeroes. Now, when I try to mount the

Hi, It seems one of my computers died last night and it looks like hard disk trouble. I took the disk out and attached to another system and tried to mount the partition, but the mount doesn't complete and just hangs (process is also unkillable - I had to reboot). So, I tried to run "fsck -fccp /dev/sda2" but the command just hangs after printing "/dev/sda2: recovering

On Tue, 26 Jul 2016, Gabriele Pohl wrote: > Hi, > > on all of my CentOS7 VMs on different hypervisors > the config file e2fsck.conf contains the line > > broken_system_clock = 1 > > I found this because on all of them, the > root partition was not checked triggered > by interval setting with tune2fs. > > Do you see similiar /default/ settings on > your

I have been playing with external journals some more and thought I should share some experiences. I am running 2.4.16 with the ext3 patches from Andrew Morton and e2fsprogs 1.25 I have an ext3fs filesystem on an 8 drive RAID5 array and place the journal on a partition of the mirrored pair that I boot off (all drives SCSI). I have tried pulling the power cable and seeing what happens. I finally

On 2013-06-26, at 9:38 AM, Eric Sandeen wrote: > On 6/25/13 3:13 AM, Folkert van Heusden wrote: >> >> I have a system with an ext4 filesystem with its journal on an other >> device (an SSD). >> Now this SSD dropped of the sata bus so the filesystem went r/o. >> I would like to remove the journal but it says it can't because >> needs_check is set. >

Hello, on my ext3 fs I have a file that I can not modify anymore: $ who am i root pts/0 Nov 18 19:42 (192.168.10.110) $ ls -al /mnt/path/usage_200306.html -rw-r-xrw- 1 50946 nobody 99935 Jul 1 2003 /mnt/path/usage_200306.html $ rm /mnt/path/usage_200306.html rm: remove regular file `/mnt/path/usage_200306.html'? y rm: cannot remove `/mnt/path/usage_200306.html': Operation

Hi, on all of my CentOS7 VMs on different hypervisors the config file e2fsck.conf contains the line broken_system_clock = 1 I found this because on all of them, the root partition was not checked triggered by interval setting with tune2fs. Do you see similiar /default/ settings on your machines? Is it an issue only on VMs? I have no CentOS7 host on bare metal to compare. Thanks and cheers,

Hello ext3 list, I am having an odd issue with one of my filesystems, and I am hoping someone here can help out. Yes, I do have backups. :) But as is often the case, it's nice to avoid restoring from backup if possible. If there is a more appropriate place for this question please let me know. After quite a while between reboots, I saw a report on the console that the filesystem was

e2fsck returns 1 in case of "file system errors corrected". We treat it as success in normal e2fsck, but fail if e2fsck is run by resize2fs. Change 'manual' execution of e2fsck to dedicated function call. --- daemon/ext2.c | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/daemon/ext2.c b/daemon/ext2.c index 5dd67c7..95a65ae 100644 ---

Helping a friend fix a computer that was having severe, weird troubles. Reformatted (from XP) and installed Fedora. Install went ok, on first boot, however, filesystem was READONLY for some reason. Knew hard drive was suspect, so I e2fsck'd it over and over all night long, fall asleep next to the computer. This morning, Fedora boots fine, login not a problem, so I shut down and fsck it again,

On Sun, Jun 01, 2014 at 08:54:24PM -0700, Keith Keller wrote: > > Heh, I like your understatement. :) I think this helps answer part of > my questions in my second email: I should probably try to preserve > changes from last backup before getting too deep into a tricky e2fsck. > At one point the fs was still mountable, so I could have tried to copy > files off first. (In a

* "Theodore Ts'o" <tytso@mit.edu> hat geschrieben: Hi Theodore. > That being said, it's pretty clear that portions of the inode table > and block group descriptor was badly corrupted. [...] Keith is not the first one with problems of this class and he will probably not be the last one. He later told us, that at first, mounting the file system still worked. And that

Does Automount/autofs automagically run e2fsck? If so, how does one disable this? We have an external USB connected 2TB hard drive setup to automount. Sometimes e2fsck gets fired up, I think from Automount. I have this line in the automount config: /backupdisk -fstype=ext3,nocheck :LABEL=BACKUP I believe this should prevent Automount from running e2fsck, but it still runs it. (We

We have CENTOS 5.5 run on DELL server.?? Due to power system crash, server been down and up. I would like use 'e2fsck" to check file systems. Does there has way to run "e2fsck" under following conditions: 1. file systems are all ext3 2. file systems must mount. 3. e2fsck only scan file system but NO modify Thanks.

On Wed, 27 Jul 2016 09:46:02 +0100 (BST) John Hodrien <J.H.Hodrien at leeds.ac.uk> wrote: > On Tue, 26 Jul 2016, Gabriele Pohl wrote: > > I now changed the value to 0 and rebooted. > > > > After that fsck based on Interval setting were done. > > > > Unfortunately that is not true for the root partition. > > For that I had to use maxCount settings to

* Keith Keller <kkeller@wombat.san-francisco.ca.us> hat geschrieben: Hi Keith > I have a very similar second server which has undergone a similar chain > of events, an initial ~2.5tb fs followed by a resize later. I believe > that it has been fsck'd since the resize (but don't quote me on that). > Am I likely to run into this issue with this fs? And if I do, what >

Eric, Andreas, >>> I have a system with an ext4 filesystem with its journal on an other >>> device (an SSD). >>> Now this SSD dropped of the sata bus so the filesystem went r/o. >>> I would like to remove the journal but it says it can't because >>> needs_check is set. >> >> What does it actually say? there is no needs_check flag

(There really doesn't seem to be a dedicated e2fsprogs list, so this was the next-best place I could find. I don't place much faith in the sourceforge forums..) The filesystem in question is a 480 gig ext3 partition, on a hardware RAID5 controller. It's approximately 90% full, with something like 115K files. Kernel 2.4.20-pre4, on a Duron 900. As I type this, e2fsck has used up

I posted this to the Fedora-list, but thought I might get some additional information here as well. I have a HD that refuses to mount with a 'bad magic number in super-block'. I'm running FedoraCore 6 x86_64. [root at moe ~]# fdisk -l /dev/hdc Disk /dev/hdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes