similar to: when is fsck required?

Hey! I have some RHEL6 hypervisors and the VMs are in raw qemu image files in a local raid array linux raid + lvm + ext3. When a kernel update is installed a reboot is necessary, usually it has been more than 180 days since the last reboot and the file system is fsck'd and this takes 2-3 hours. I am curious to know if there is any documentation that addresses the pro's and con's of

Hello everybody, Could someone please explain to me what is the difference between kjournald and jbd (precisely, what does each of them do?) Thank you, Alina _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

Hey folks, I searched the list archives and found this : echo "AUTOFSCK_TIMEOUT=5" > /etc/sysconfig/autofsck echo "AUTOFSCK_DEF_CHECK=yes" >> /etc/sysconfig/autofsck http://lists.centos.org/pipermail/centos/2006-November/029837.html http://lists.centos.org/pipermail/centos/2009-September/thread.html#81934 Will this do all disks? I want to do a reboot of a couple

Hi people, I ran into one of these silly issues I'd like to share as I think the reason behind it may be a flaw in the current initrds. The setup; Dual-Xeon Intel-chipset motherboard. SATA-disk attached to ICH, onboard Adaptec SCSI-controller. Installed system, updated packages, no problems. Basic, non-LVM partition setup - OS-disk is /dev/sda, single filesystem-partition /dev/sda1 is

Hi - I've been asked to turn on autofsck on ext3 filesystems for CentOS 4 and 5 servers on reboot after a crash by adding AUTOFSCK_TIMEOUT=5 AUTOFSCK_DEF_CHECK=yes to the file /etc/sysconfig/autofsck Is this necessary for ext3 filesystems? Is this a safe thing to do for a ext3 filesystems? I haven't used autofsck since the ext2 days. -- Agile --

excuse the newbie nature of the post, we recently inherited a linux server which has ext3 on it and we have encountered problems before being afforded the opportunity to properly educate ourselves... We had a situation where the server froze and required a hard restart. On reboot we get the following notices which were captured in the dmesg log EXT3-fs: INFO: recovery required on readonly

Hi, I am trying out ext3 with an external journal (on a battery backed RAM card). I use data=journal, and sync nfs writes go nice and fast :-) But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot get my filesystem back. It is only a test filesystem so I don't need the data. But I want this to work before I put real data on it. If I "fsck /dev/md1", it

I have worked quite a bit with CentOS 4.x with SAN, multipathing, LVM etc. The way I mount my file systems is using a script that is called during startup that runs fsck, imports the physical volumes, and volume groups, activates the logical volumes, creates the mount point if needed then mounts the volume, I mainly made it for software iSCSI due to the iscsi stack loading after the system mount

Hi, I've downloaded and installed kernel-2.4.9 from rawhide in order to use ext3 support (I've also upgraded the necessary packages). I've used tune2fs to make the current ext2 partitions (incluind /) and changed fstab to reflect that. In order to test if everything is ok (this is a test machine) I've switched off with no shutdown. Except the / all other partitions accused

Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message:

Greetings. Total newbie with Ext3. I selected when I upgraded my system to RH7.2. I upgraded my system again to RH8.0. Here is some info: [root@world root]# cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 none /dev/shm tmpfs rw 0 0 none /dev/pts devpts rw 0 0 /dev/hdd1 /mnt/genericdata1 ext2 rw 0 0 Ok, so

I have a test 4.x-stable system that I recently rebooted into. The last time I had updated it was May 3rd. I cvsup'ed it, did the buildworld/installworlds, and everything seemed fine. I then thought I would update all the ports. When upgrading XFree86, the /usr partition ran out of disk space. Now the partition shows up as: (21) df -k Filesystem 1K-blocks Used Avail Capacity

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii Howdy - we have a bunch of dual processor Compaqs with 180GB RAID partitions for email, running with ext2 for the last year or so. I thought I'd try out ext3 (on our development machine :-) to see whether it was a practical proposition for this kind of thing yet. Appears to be working so far, with a

Hi, I thought that I would attempt a quick little patch that will make btrfsck into a No-op when called as fsck.btrfsck. The reasoning is that the FAQ states that it is recommended and safe to do so, and the current 12.04 version of Ubuntu just symlinks fsck.btrfsck to btrfsck instead of /bin/true. PS - Apologies if I mess this git send-email up! Dan McGrath (1): btrfs-progs: No-op when

Dear All My CentOS server got file system inconsistency , asking for "type Ctrl-D for normal boot or give root password for maintenance to run fsck manually". I tried for manually run fsck , as the followings : #fsck -s /dev/hda3 But after rebooting the server it will come back again at the similar prompt asking for "give root password for maintenance" . Can you please do me

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.

The 03/07/13, Jamie Fargen wrote: > Hey! > > I have some RHEL6 hypervisors and the VMs are in raw qemu image files in a > local raid array linux raid + lvm + ext3. When a kernel update is installed > a reboot is necessary, usually it has been more than 180 days since the > last reboot and the file system is fsck'd and this takes 2-3 hours. > > I am curious to know if

Hi, we have CentOS ftp server (vsftpd) which has a lot of users who are writing and reading a lot of small files from/into its own accounts (and other servers - using samba client - are reading these files and putting them into outside database). Since this server is under heavy load its availability is important. >From time to time we "crash" this server (don't ask why ...) but

Hello Everyone, I just ran fsck.ocfs2 on /dev/drbd0 which is a one gig partition on a vm with limited resource (100meg of ram). I am worried that the process crashed because it has not responded in the past hour or so? fsck.ocfs2 /dev/drbd0 fsck.ocfs2 1.6.4 [RECOVER_CLUSTER_INFO] The running cluster is using the cman stack with the cluster name ASTCluster, but the filesystem is configured for