[EMAIL PROTECTED] wrote:
with this, fsck won't change anything to my partition at all?
nope.
and what about this line from the output of tune2fs?
Filesystem state: clean with errors
Is it like "critical" or like "informative"?
only fsck can tell...
Since e2fsck _will_ find errors, I'll have to do an e2fsck without -n anyway.
Or should I light a candle, buy some horseshoes and hope that my / will stay
the longest possible "clean with errors", before going to HD paradise?
How useful is this system to you, when you can't even write to the disk?
I would take to system down, check the filesystems, repair them (if needed),
recover lost data from backups and get up and running again.
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...
Christoph
--
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" [EMAIL PROTECTED]
--
[email protected] mailing list
