similar to: boot with dirty filesystem?

I've got a possibly silly question and I believe I have an answer, but I want to see if what I think is the answer is feasible. I've had to rebuild a mail server from scratch, upgrading from 4.6-STABLE to 4.8-STABLE in the process. The other mail server had crashed, with disk errors so sever it wouldn't fsck clean. I was able to get it together enough to pull my configuration files

Hi, We've got some units in client's vehicles which are running Fedora core 1. We've can log into them over ssh remotely there is no console attached to them. I suspect one of them has some filesystem corruption, and I'd like to both force a fsck at next reboot (which I think I can do with shutdown -F) but I'd also like to make this fsck not require any human intervention.

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

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, 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, I have a 1.3TB ext3 filesystem that has been in service for about 3 months. About 6 days ago the Emulex fibrechannel controller logged a SCSI error and the filesystem changed to RO. It appears that the filesystem instantly changes to RO and prevents the journal from working, therefore invalidating the filesystem. The filesystem was unmounted and a remount was attempted. The mount failed

hi All, A fault on our SAN dropped us down to a read-only filesystem and after reboot, we have an "Unexpected Inconsistency" and I am being instructed by the boot to run fsck manually without -a or -p (this was after I think processing around 15% of the filesystem) The specific message is "inode 27344909 has illegal blocks" I recall running fsck some years ago on smaller

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

Hi All. I have a CentOS server: CentOS 5.6 x86_64 2.6.18-238.12.1.el5.centos.plus e4fsprogs-1.41.12-2.el5.x86_64 which has a 11TB ext4 filesystem. I have problems with running fsck on it and would like to change the filesystem because I do not like the possibility of running long fsck on it, it's a production machine. Also I have some problems with running fsck (not enough RAM, problem with

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

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

I appear to have a broken filesystem on this box to the point where I am probably going to rebuild the system since I have lost trust in it.... I was wondering if there was any reasonable postmortum work I could do on it before it gets rebuilt. History is that the laptop has a much mauled partition set on it - initially it came with 100% win2k, I then shrunk that and added linux (a RH71 install

Hi All. I have two running servers (drbd primary, drbd secondary). When there is a problem with one of them we switch to the second one. Currently on the /dev/drbd0 (it has /xxx ext3 filesystem directly on it) we have some filesystem problems (after fsck -n). I would like to correct these errors but the filesystem should be unmounted first (I would like to avoid it if possible). Is there a way

On 2015-01-07, Gordon Messmer <gordon.messmer at gmail.com> wrote: > > Of course, the other possibility is simply that you've formatted your > own filesystems, and they have a maximum mount count or a check > interval. If Les is having to run fsck manually, as he wrote in his OP, then this is unlikely to be the cause of the issues he described in that post. There must be

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

Robin, To me, anyone else includes the kernel of the current node. Well, if it is unclear the man page should be revised. Also a big warning message on ocfs2.fsck would be nice, after all we all make mistakes. But this is only my two cents. Running fsck on any journaled filesystem will replay the journal. This will cause corruption if the filesystem is mounted read/write, even if the

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

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

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 there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ====================================================================