similar to: ssh in while in fsck

Hi all, Has anyone seen something like this before: I want to use a laptop as a KVM console. Basically when a technician goes to one of our datacentres, or clients he has to look for a free LCD, keyboard & mouse to connect to a server (no network access, reinstall, troubleshoot failed kernel / HDD, etc). And then hopefully there's an open power socker in that cabinet. So I'm

Hello, Are there any KVM over IP switches that are not thousands of dollars? Ideally a 3-4 port switch for a few hundred seems reasonable to me. Mike -- Michael B Allen Java Active Directory Integration http://www.ioplex.com/

Hi, I'd like to keep all emails coming from alom-alert at anydomain and not forward those but rest of the emails will be kept and forwarded as well. I put following in the .dovecot.sieve if header :contains "Sender" "alom-alert@" { keep; if not header :contains "Sender" "alom-alert@" { redirect "my at emailid on server"; redirect "xyz

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

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:

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.

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

Hi, can anyone give me an example of when an fsck would repair something that the ext3 driver would not? with full "data=journal" journaling, would fsck ever need to be run if all the partitions were ext3? the ext3 mini-howto refers to "certain rare hardware failure cases (e.g. hard drive failures)" that would require a filesystem check, but doesn't go into details.

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

fsck (Red Hat Enterprise Linux AS 2.1) returns an exit code 127 on an ext3 file system when run from a shellscript started by cron. Here is the pertinent part of the script: ... fsck -p /dev/${BK_SLICE} 1>/dev/null 2>&1 STATUS=$? if [ ${STATUS} -ne "0" ] then echo "${MIR_PID}: file system check of /dev/${BK_SLICE} failed, status = ${STATUS}" >>${LOG}

Thanks for a great file system! I have a two-node cluster working as a HA NFS server. This system has worked fine for almost a year, but recently I found that an ocfs2 file system had been corrupted and needed to be repaired with fsck.ocfs2. Even though I don't think that any data was lost I found that 4 of my 14 ocfs2 partitions had some errors which were corrected by fsck.ocfs2. I then

I'm trying to do an fsck on an ext3 partition but I'm seeing abysmally slow disk throughput; monitoring with "dstat" (like vmstat) shows ~1200-1500KB/s throughput to the disks. Even with 24hrs of fsck-ing I only get ~3% (still in pass1). The filesystem is ext3 running "e2fsck -C0 /dev/sda3" and about 3.7TB on an x86_64-based system with 4GB RAM. e2fsprogs is 1.41.9.

Hi Guys, I have a xen set up with two domu VM''s. One of these VM has recently crashed and was running lot of web services. When I tried to xm shutdown and xm create -c domainname, it directly starts fsck and ends up with the following: INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd[    2.724077] udevd version 125 started . Synthesizing the initial hotplug

Hello I have a newbie question, given a centos 5 installation, An 5 very large disk arrays ( 2.5Tbytes each ) - Is there a way to suspend or stop the fsck during the boot up? The system seems to pick the most inopportune time to decide to reach the check count limit... and with this many disks, a reboot takes several hours... which is an eternity when your boss is looking over your shoulders

System info: ------------ [root@angel root]# cat /etc/issue Red Hat Linux release 7.2 (Enigma) Kernel \r on an \m [root@angel root]# uname -a Linux angel 2.4.9-34 #1 Sat Jun 1 06:25:16 EDT 2002 i686 unknown This problem occured after upgrade to kernel 2.4.18-17.7, backed out to previous version now (2.4.9-34). All other system RPMs are up to date according to RHN, and nothing, aside from

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

I am building a new server. It will be a temporary firewall of sorts. I am well into the config, made a lot of changes; almost ready to set it up in the target networks, but now.... The system hangs trying to start sendmail. I was thinking hard about disabling sendmail, but thought I needed it for internal functions, so did not. yet. So is there someway to get the system working so I can

Hi, After our big ext3 file server crashes, I notice the fsck spends some time replaying the journals (about 5-10 mins for all volumes on the server in question). I guess it must do this should you want to mount the volumes as ext2. My question--is it (theoretically) possible to tell fsck only to replay half-finished and to knock out incomplete transactions from the journals, leaving the kernel

Hi there, I am newbie and recently started using btrfs. Now facing a weird problem. FWIW, I am on archlinux, kenel v3.8.0, having Btrfs v0.20-rc1. After an abnormal reboot, getting these errors while boot: systemd.fsck[289]: checking extents systemd.fsck[289]: checking fs roots systemd.fsck[289]: checking root refs systemd.fsck[289]: found 23728128 bytes used err is 0 systemd.fsck[289]: total