similar to: e2fsck run under "read only mode"???

Hi I got a strange error, happening on two of my ext3 partitions. What can be wrong? And why does e2fsck error out, instead of displaying an error message? Best regards keld fsck /dev/hda6 fsck 1.38 (30-Jun-2005) e2fsck 1.38 (30-Jun-2005) Warning... fsck.ext3 for device /dev/hda6 exited with signal 11. also From my dmesg: <1>general protection fault: e7a8 [#3] Modules linked in:

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

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

On Tue, 26 Jul 2016 16:21:00 +0100 (BST) John Hodrien <J.H.Hodrien at leeds.ac.uk> wrote: > On Tue, 26 Jul 2016, Gabriele Pohl wrote: > > > on all of my CentOS7 VMs on different hypervisors > > the config file e2fsck.conf contains the line > > > > broken_system_clock = 1 > > > > Do you see similiar /default/ settings on > > your machines? Is

Hi, Somehow I've managed to get e2fsck to seg fault.. The filesystem in question started acting very strangely (e.g. filenames changing from music to MuSiC etc) so I rebooted, and since when fsck has crashed every time it has been run. I'm not really sure what any of this means, so I didn't know what debugging output to include, but below is the output of e2fsck. (I would have

I have a large (1.5TB) partition with millions of files on it. e2fsck has been running nearly 12 hours and is still on "Checking directory structure". Any tips for speeding this along? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100831/8653d551/attachment-0002.html>

Hi there, I started getting errors on one of my 2 drives, so I got a warranty one. Then I made an exact copy of the failing one onto the new one with dd, and swapped them. I ran fsck on all the affected partitions, and things looked good. Then I started using the striped RAID device (ext3) which had some minor data loss (mostly under big files), and I got the problems with the journal. The

Hi, yesterday I ran e2fsck -n on a mounted file system and got: /dev/sdb1 contains a file system with errors, check forced. According to Ted, the lines that followed were not to be trusted due to the fact that the file system was mounted. But this error statement suggests to run a check with the fs unmounted. Today, we scheduled a downtime and ran the check. It came of completely clean: ~:

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

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,

I've run ext3 filesystems for the last few years and I've never seen this question answered..... If a system shutsdown hard, even with journaling is it at all necessary to run e2fsck? Just curious.... Thanks -- Sam Williams samurai at acm.org +----------------------------------------------------------------------+ +"It is easy to be

Hi. I'm using Debian. Is this a Redhat-only list, or is it only hosted by RedHat? I recently changed my filing systems over to ext3, but deliberately left the forced boot check parameters alone so my system checks after 20 mounts. I notice that the fsck takes a good ten times longer than under ext2, to perform the cleanly unmounted check. (On the occasion where I did unmount dirtily, the

How big is a file that e2fsck considers it to be a large file? 814611 blocks used (42.79%) 0 bad blocks 1 large file <----- that Thanks John Nelson

I found a thread that has almost the exact same symptoms as me, but didn't seem to come to a resolution: https://listman.redhat.com/archives/ext3-users/2004-December/msg00018.html I have an LVM(2) array that I've just lvextend'd and want to resize2fs, but I can't get through the e2fsck. I get these errors when fsck-ing: Group 3125's inode table at 102400545 conflicts with

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,

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

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

Hallo List, after rebooting one of our systems one of the ext3 filesystems, that was cleanly unmounted, fsck stopped the boot process due to critical errors in that filesystem. Running fsck -y manually returned, that one of the i-nodes is "too big" an was truncated. After this about three million i-nodes were orphaned an moved to lost+found. # strings /sbin/e2fsck | grep -i

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No-one out there who can give me any tips for this? (Then the space to do experiments will finally be used in other ways. And I hope this mail won't be consired to impolite...) On Mon, 6 Dec 2004 15:23:15 +0100 Milan Holz?pfel <lists at mjh.name> wrote: > Hello, > > I got an IDE-drive which decided to get broken. Part of

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