On Thursday, April 12, 2012 10:13:00 AM m.r...@5-cent.us wrote:
> Time to use smartctl, if not fsck -c.
Another useful fsck variation is fsck -cc which will do a nondestructive
'read-write' to trigger on-drive bad sector remapping. Takes a long time to
do, but does the work.
It's documented in
From: Rafał Radecki
>T he system was not rebooted, it just was not responsive (ssh) and has a gap
> in logfiles for 15 minutes. After 15 minutes it started responding.
Maybe also check the bios/ipmi logs...
JD
___
CentOS mailing list
CentOS@centos.org
Rafał Radecki wrote on 04/12/2012 10:32 AM:
> The system was not rebooted, it just was not responsive (ssh) and has a gap
> in logfiles for 15 minutes. After 15 minutes it started responding.
Then I'd try the smartctl suggestion from mark.
Please do not top-post.
Phil
__
The system was not rebooted, it just was not responsive (ssh) and has a gap
in logfiles for 15 minutes. After 15 minutes it started responding.
Best regards,
R.
W dniu 12 kwietnia 2012 16:08 użytkownik Phil Schaffner <
philip.r.schaff...@nasa.gov> napisał:
> Rafał Radecki wrote on 04/12/2012 03:
Phil Schaffner wrote:
> Rafał Radecki wrote on 04/12/2012 03:07 AM:
>> Hi All.
>>
>> I had today a problem with my mail server (2.6.18-274.12.1.el5 #1 SMP
>> Tue Nov 29 13:37:35 EST 2011 i686 i686 i386 GNU/Linux, CentOS release 5.7
>> (Final)). On my Cacti graphs I see that there has been much I/O
Rafał Radecki wrote on 04/12/2012 03:07 AM:
> Hi All.
>
> I had today a problem with my mail server (2.6.18-274.12.1.el5 #1 SMP Tue
> Nov 29 13:37:35 EST 2011 i686 i686 i386 GNU/Linux, CentOS release 5.7
> (Final)). On my Cacti graphs I see that there has been much I/O write on
> the disks and then
6 matches
Mail list logo
