search for: forcefsck

...user mode 2. start checkdisk for all disks 3. once done, reboot into runlevel 3 i've did a certain script that force checkdisk at night if there's a bad sector using the badblocks command though that's not enough. PS: i was thinking of something of this sort: 1 4 * sat /bin/touch /forcefsck;reboot 1 1 * sun rm /forcefsck Would the above work? for all disks? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110228/773e54ee/attachment.html>

About two weeks ago i was whining about an inode that got lost, now i'm going to whine more about strange things happening here. A matroxfb just oopsed on me (thats not strange), the machine got unusuable, so i logged in from another and got the idea to touch /forcefsck. Upon reboot, fsck said that some inodes are in use but have dtime set and that some files are illegal sockets. Now this just doesn't sound healty to me ... Should I be worried? Something fishy is going on here ... memtest says it's not ram, harddrive is IBM IC35 (i thought that only GXF75...

...smtp, status=4.4.2, rstatus=(null), host=inet08.hamilton.harte-lyne.ca., lastuse=Tue Nov 25 07:41:32 2014\n: 1 Time(s) I have not seen this sort of thing before and I am wondering what it means? Googling has not provided anything useful. In case this was an incipient HDD error I rebooted with /forcefsck but on CentOS-5 one obtains no log of the rc report. I am also not entirely clear on whether or not /forcefsck actually repairs any errors. Thus it may not mean much to have done this. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Har...

If I have the 6th column in fstab (the pass column) set to 0, does that mean disk checks will never be forced at boot regardless of anything like File System State, Mount Count, and Check Interval on the file system itself, or are there exceptions to this? I know `man fstab` says: If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does

...:32 2014\n: 1 > Time(s) From what kind of logfile are those lines? That's not Sendmail log style. > I have not seen this sort of thing before and I am wondering what it means? > Googling has not provided anything useful. In case this was an incipient HDD > error I rebooted with /forcefsck but on CentOS-5 one obtains no log of the rc > report. I am also not entirely clear on whether or not /forcefsck actually > repairs any errors. Thus it may not mean much to have done this. The first system in question simply does not support TLS and it fails while testing. 250-inet04.mis...

...7932336 2262672 5260064 31% / tmpfs 961044 0 961044 0% /dev/shm /dev/vda1 487652 139473 322579 31% /boot . . . This indicated that a bad sector on the underlying disk system might be the source of the problem. The guests were all shutdown, a /forcefsck file was created on the host system, and the host system remotely restarted. However, this action did not remove the error. The host system log files had this to say about fsck: /var/log/messages:Mar 9 08:34:48 vhost03 kernel: EXT4-fs (dm-6): warning: maximal mount count reached, running e2fsck...

...on this. The last time I did anything like this I ended up having to boot into recovery mode from an install cd and do this by hand. This is not an option in the present circumstance as the unit is a headless server in a remote location. If I do this: echo '-c' > /fsckoptions touch /forcefsck shutdown -r now Will this repair the bad block and bring the system back up? If not then what other options should I use? The bad block is located in an LV assigned to a libvirt pool associated with a single vm. Can this be checked and corrected without having to deal with the base system? If so...

...ut it all settled down and seemed to be working... Then TSM (backup program) started bombing out (had done some successful backups). The error message was ANS1028S Internal program error. Please see your service representative. which helps little :-) I decided to force a fsck, so did touch /forcefsck and rebooted The fsck threw up many thousands of errors, all of the form INODE nnnn i_blocks is 32, should be 16 with the i_blocks & should-be values various multiples of 8. I suspect that parted has screwed up, and so ext3 has been running on a losing wicket ever since... however even af...

On Thu, March 9, 2017 09:46, John Hodrien wrote: > On Thu, 9 Mar 2017, James B. Byrne wrote: > >> This indicated that a bad sector on the underlying disk system might >> be the source of the problem. The guests were all shutdown, a >> /forcefsck file was created on the host system, and the host system >> remotely restarted. > > fsck's not good at finding disk errors, it finds filesystem errors. If not fsck then what? > > If it was a real disk issue, you'd expect matching errors in the host > logs. Yes, ther...

...g like this I ended > up having to boot into recovery mode from an install cd and do this by > hand. This is not an option in the present circumstance as the unit > is a headless server in a remote location. > > If I do this: > > echo '-c' > /fsckoptions > touch /forcefsck > shutdown -r now > > Will this repair the bad block and bring the system back up? If not > then what other options should I use? > > The bad block is located in an LV assigned to a libvirt pool > associated with a single vm. Can this be checked and corrected > without havi...

Sep 13 12:18:56 sfe fsck: /dev/VolGroup00/LogVol00 is mounted. Sep 13 12:18:56 sfe fsck: e2fsck: Cannot continue, aborting. Sep 13 12:18:56 sfe rc.sysinit: Checking root filesystem failed I had updated the box a few days ago but I had not rebooted with the new kernel. After the reboot, I get the root filesystem is not marked clean message and also that it was not mounted read-only. I supplied

VFS: brelse: Trying to free free buffer buffer layer error at fs/buffer.c:1182 Pass this trace through ksymoops for reporting Call Trace: [<c01468f0>] [<c0146aa9>] [<c0146b57>] [<c0146b84>] [<c0175a17>] [<c023cbfa>] [<c023d2f1>] [<c0175c90>] [<c01728e9>] [<c01ad7d6>] [<c014d215>] [<c0154c68>] [<c0154f79>]

...or directory ls -la mtab: ?--------- ? ? ? ? ? mtab messages full of errors: EXT3-fs error (device cciss/c0d2p1): ext3_lookup: unlinked inode 847444 in dir #846977 I would like to fsck / partition, but, obviously, can't do it on a live system. The plan is to touch /forcefsck and to force fsck during reboot. Please let me know if you see a problem with my plan or have any other suggestions. Thank you, Asya

Hi, My Centos 5.2 server (5.1 suffered the same problem as well) has a logical volume on a RAID 10 array (4 SATA harddisks on a Highpoint RR2310 controller). /etc/fstab has an entry for this array as below /dev/raid_vg0/raid_lv0 /mnt/raid ext3 defaults 0 0 Normally it works OK. But, file system of "this volume" once in a while goes "read only"

This may or may not be ext3 related but I am trying to find any pointers which might help me. I got a number of HP Proliant DL380 g5 with a P400 controller and also two qla2400 cards. The OS is RedHat EL4 U5 x86_64. Every time during reboot these systems panic after the last umount and I believe before the cciss driver is getting unloaded. The last messages I am able to see are: md: stopping

Hi, I have set-up the ups shutdown feature provided by Red Hat /etc/rc.d/init.d/halt script, which will issue a "upsdrvctl shutdown" command just before powering off the system. It appears that this command fails as if the driver is not available. I wonder whether the usb driver / stack is still available at this very late stage ? If not available then does it mean one cannot

A user running gnome came in this morning, clicked on the application menu... and it was much shorter than he expected. He could get to firefox, and googled about refreshing that... and found something that told him to reboot. And that's it: I cannot get X up, at all. I just get the "oh, no, something failed, please log out and try again". Fully updated CentOS 7, [AMD/ATI] Oland