On Wed, 20 Sep 2000, John Summerfield wrote:
>> Losing important data due to an untimely crash or powerdown is also an
>> issue in serious applications.
>
>
>Hear Hear!!
>
>Just went throughh that yesterday, RHL 6.3. I'm not competent to run that
>wretched program in manuam mode, and I doubth that anyone on this list is.
What is so hard about fsck? Has anyone actually read the
manpage? If not, then I can see it being difficult, but after
being bitten once by it, I'd assume a competant admin would do a
"man fsck", "man e2fsck". It really isn't hard at all.
>Certainly nobody's going to take the time to give a considered reply to each
>and every of the thousands (maybe tens of thousands) of questions it asked me.
>I held "y" down and still it took an hour or so.
Nobody would have to if they read the manpage. ;o)
>I did NOT like the look of what was in lost+found and could not delete it.
>There were file dates going back to 1943 and into the future at least to 2005
>(or was it 2025?).
Disk corruption. Equivalent to FILE000.CHK in MSDOS after a
SCANDISK. Linux's fsck messages are the equivalent of SCANDISK
asking you to repair lost clusters and other similar
problems. It puts recovered files in /lost+found. Again, read
the manpages.
>I fixed it by dd bs=2048k if=/dev/zero of=/dev/hdc5 followed by mkfs.ext2.
Well, I wouldn't call that a fix, but if it works for you and is
less time consuming than reading a manpage or two and learning
how the fsck program works, then by all means it is a good
solution.
>I didn't actually have much important there; I'd just created it and copied
>data from elsewhere, but I sure was lucky.
What I'd do is print out the manpages. That way you have
reference material next time. fsck is _not_ hard to use if you
read the manuals and get used to it. If this is a home system,
or similar, then not knowing how to use fsck is just a user
problem. If it is a business system or business server, whoever
admins it should know how to use fsck, or else money could be
lost. I'd recommend hiring a competant admin if it is an
important server for sure. You don't want a crash to wipe out a
server just because someone didn't know how to run fsck...
Trust me, read the manpages. If you have any questions as to
what any of the options do, I'd be glad to help. fsck may look
complex, but most of the info it dumps to the screen is just gory
details. If you don't grok them, just ignore, but forsure, read
the manpages.
Good luck!
Take care,
TTYL
--
Mike A. Harris - Linux advocate - Open source advocate
Copyright 2000 all rights reserved
----------
Red Hat Linux: http://www.redhat.com
Download for free: ftp://ftp.redhat.com/pub/redhat/redhat-6.2/
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
