On Mon, 8 Aug 2005, [EMAIL PROTECTED] wrote:
How useful is this system to you, when you can't even write to the disk?
I can write to the system again... The system couldn't write from 3 AM to 8
AM, after that, It was ok again. That's why I'm not really enthousiast to
tune my fs. "If it's not broken, don't fix it.
But it is broken...
I would take to system down, check the filesystems, repair them (if
needed), recover lost data from backups and get up and running again.
Yes, I would do that too, if I could :-(
Read my other post about how to do this remotely.
Things are a little more complicated for you, since you don't seem to have
full access to the machine. Talk to your vendor/sysadmin who is responsible
for the (physical) machines. I'm not familiar with your particular
situation...
I've attached the output of e2fsck -n. Could you please tell me how bad it
looks? Are there questions to which answering yes is dangerous?
Disclaimer: You should have backups of the system!
I've found that fsck is actually pretty damn good at being safe. I've
never had fsck fail to repair a non-hardware filesystem corruption. The
most likely thing you'll need to do after a repair here is to reboot the
machine, which is the sweating time.
If you can possibly get someone onsite from that office to watch the
reboot you should be fine.
Christopher Fisk
--
"Listen, Bender, where's your bathroom?" -Fry
"Bath what?" -Bender "Bathroom." -Fry
"What room?" -Bender "Bathroom!" -Fry
"What what?" Bender "Ah, nevermind." -Fry
--
gentoo-user@gentoo.org mailing list
