On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb@xxxxxxxxxxxxx> wrote: > > On Thu, March 9, 2017 09:46, John Hodrien wrote: >> >> fsck's not good at finding disk errors, it finds filesystem errors. > > If not fsck then what? badblocks(8). _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos
Re: CentOS-6.8 fsck report Maximal Count
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: CentOS-6.8 fsck report Maximal Count
- From: Warren Young <warren@xxxxxxxxxxx>
- Date: Fri, 10 Mar 2017 08:52:43 -0700
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <c3aef89cfae9ead8656e7ac7a2af5520.squirrel@webmail.harte-lyne.ca>
- References: <mailman.10.1489147203.26295.centos@centos.org> <c3aef89cfae9ead8656e7ac7a2af5520.squirrel@webmail.harte-lyne.ca>
- Follow-Ups:
- Re: CentOS-6.8 fsck report Maximal Count
- From: Valeri Galtsev
- Re: CentOS-6.8 fsck report Maximal Count
- References:
- Re: CentOS-6.8 fsck report Maximal Count
- From: James B. Byrne
- Re: CentOS-6.8 fsck report Maximal Count
- Prev by Date: Re: CentOS-6.8 fsck report Maximal Count
- Next by Date: Re: CentOS-6.8 fsck report Maximal Count
- Previous by thread: Re: CentOS-6.8 fsck report Maximal Count
- Next by thread: Re: CentOS-6.8 fsck report Maximal Count
- Index(es):
 |