On 08/11/2017 02:32 PM, m.r...@5-cent.us wrote:
Robert Nichols wrote:
On 08/11/2017 12:16 PM, Chris Murphy wrote:
On Fri, Aug 11, 2017 at 7:53 AM, Robert Nichols
wrote:
On 08/10/2017 11:06 AM, Chris Murphy wrote:
On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz
Robert Nichols wrote:
> On 08/11/2017 12:16 PM, Chris Murphy wrote:
>> On Fri, Aug 11, 2017 at 7:53 AM, Robert Nichols
>> wrote:
>>> On 08/10/2017 11:06 AM, Chris Murphy wrote:
On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz
wrote:
On Aug 11, 2017, at 1:07 PM, Robert Nichols wrote:
>> Yeah he'd want to do an fsck -f and see if repairs are madestem.
>
> fsck checks filesystem metadata, not the content of files.
Chris might have been thinking of fsck -c or -k, which do various sorts of
On 08/11/2017 12:16 PM, Chris Murphy wrote:
On Fri, Aug 11, 2017 at 7:53 AM, Robert Nichols
wrote:
On 08/10/2017 11:06 AM, Chris Murphy wrote:
On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz
wrote:
On 08/09/2017 10:46 AM, Chris Murphy
On Fri, Aug 11, 2017 at 7:53 AM, Robert Nichols
wrote:
> On 08/10/2017 11:06 AM, Chris Murphy wrote:
>>
>> On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz
>> wrote:
>>
>>>
>>>
>>> On 08/09/2017 10:46 AM, Chris Murphy wrote:
If it's a bad
On 08/10/2017 11:06 AM, Chris Murphy wrote:
On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz wrote:
On 08/09/2017 10:46 AM, Chris Murphy wrote:
If it's a bad sector problem, you'd write to sector 17066160 and see if
the
drive complies or spits back a write error. It
Chris Murphy wrote:
On Wed, Aug 9, 2017, 11:55 AM Mark Haney wrote:
To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on a
couple of systems and it corrupted pretty quickly. I'd stick with xfs/ext4
if you manage to get the drive working again.
On Aug 10, 2017, at 2:17 PM, John R Pierce wrote:
>
> On 8/10/2017 1:12 PM, Warren Young wrote:
>> You want those pages to get swapped out quickly so that the precious RAM can
>> be used more productively; by the buffer cache, if nothing else.
>
> most modern virtual
On 10/08/17 21:17, John R Pierce wrote:
> On 8/10/2017 1:12 PM, Warren Young wrote:
>> It’s a bad idea to do without swap even if you almost never use it,
>> because today’s bloated apps often have many pages of virtual memory
>> they rarely or never actually touch. You want those pages to get
>>
On Aug 10, 2017, at 10:46 AM, mad.scientist.at.la...@tutanota.com wrote:
>
> is that because the drive is compressing the information?
No. I believe by “probabilistic representation” the parent poster simply means
that in any given data cell, you don’t have a hard “1” or “0”, you have some
On 8/10/2017 1:12 PM, Warren Young wrote:
It’s a bad idea to do without swap even if you almost never use it, because
today’s bloated apps often have many pages of virtual memory they rarely or
never actually touch. You want those pages to get swapped out quickly so that
the precious RAM can
On Aug 10, 2017, at 2:07 AM, John Hodrien wrote:
>
> For a well configured desktop that rarely needs to swap, I struggle to see the
> load on the SSD as being significant, and yet obviously the performance of an
> SSD would make it ideal for swap.
I agree.
It’s a bad
Chris Murphy wrote:
> On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz
> wrote:
>
>>
>>
>> On 08/09/2017 10:46 AM, Chris Murphy wrote:
>> > If it's a bad sector problem, you'd write to sector 17066160 and see
>> if
>> the
>> > drive complies or spits back a write error. It
is that because the drive is compressing the information? is there a way to
turn this off? i hate mandatory compression as losing one bit in a compressed
file tends to be a big deal compared to the same in an uncompressed file.
--
Securely sent with Tutanota. Claim your encrypted mailbox
On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz wrote:
>
>
> On 08/09/2017 10:46 AM, Chris Murphy wrote:
> > If it's a bad sector problem, you'd write to sector 17066160 and see if
> the
> > drive complies or spits back a write error. It looks like a bad sector in
> > that
On Wed, Aug 9, 2017, 11:55 AM Mark Haney wrote:
> To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on a
> couple of systems and it corrupted pretty quickly. I'd stick with xfs/ext4
if you manage to get the drive working again.
>
Sounds like a
On Thu, 10 Aug 2017, Robert Moskowitz wrote:
Other than the 17K output from smartctl -x, what do you recommend?
smartctl -a is a little easier on the eye.
jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On 08/10/2017 10:31 AM, m.r...@5-cent.us wrote:
Robert Moskowitz wrote:
On 08/09/2017 10:44 PM, mad.scientist.at.la...@tutanota.com wrote:
what file system are you using? ssd drives have different
characteristics that need to be accomadated (including a relatively slow
write process which
Robert Moskowitz wrote:
On 08/09/2017 01:48 PM, hw wrote:
Robert Moskowitz wrote:
I am building a new system using an Kingston 240GB SSD drive I pulled from my
notebook (when I had to upgrade to a 500GB SSD drive). Centos install went
fine and ran for a couple days then got errors on the
Mark Haney wrote:
To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on a
couple of systems and it corrupted pretty quickly. I'd stick with xfs/ext4
if you manage to get the drive working again.
That was merely to see if a trim operation on the whole device would bring
Robert Moskowitz wrote:
> On 08/09/2017 10:44 PM, mad.scientist.at.la...@tutanota.com wrote:
>> what file system are you using? ssd drives have different
>> characteristics that need to be accomadated (including a relatively slow
>> write process which is obvious as soon as the buffer is full),
os.org> ] On Behalf Of Robert
Moskowitz
Sent: Wednesday, August 9, 2017 17:03
To: CentOS mailing list <> centos@centos.org> >
Subject: [CentOS] Errors on an SSD drive
I am building a new system using an Kingston 240GB SSD drive I pulled
from my notebook (when I had to upgrade to a 500GB SSD dr
On 08/09/2017 01:48 PM, hw wrote:
Robert Moskowitz wrote:
I am building a new system using an Kingston 240GB SSD drive I pulled
from my notebook (when I had to upgrade to a 500GB SSD drive).
Centos install went fine and ran for a couple days then got errors on
the console. Here is an
On 08/09/2017 10:46 AM, Chris Murphy wrote:
If it's a bad sector problem, you'd write to sector 17066160 and see if the
drive complies or spits back a write error. It looks like a bad sector in
that the same LBA is reported each time but I've only ever seen this with
both a read error and a
On Thu, 10 Aug 2017, mad.scientist.at.la...@tutanota.com wrote:
what file system are you using? ssd drives have different characteristics
that need to be accomadated (including a relatively slow write process which
is obvious as soon as the buffer is full), and never, never put a swap
entOS [> mailto:centos-boun...@centos.org> ] On Behalf Of Robert
> Moskowitz
> Sent: Wednesday, August 9, 2017 17:03
> To: CentOS mailing list <> centos@centos.org> >
> Subject: [CentOS] Errors on an SSD drive
>
> I am building a new system using an Kingston 240GB SS
org>
Subject: [CentOS] Errors on an SSD drive
I am building a new system using an Kingston 240GB SSD drive I pulled
from my notebook (when I had to upgrade to a 500GB SSD drive). Centos
install went fine and ran for a couple days then got errors on the
console. Here is an example:
[168176.995064
To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on a
couple of systems and it corrupted pretty quickly. I'd stick with xfs/ext4
if you manage to get the drive working again.
Robert Moskowitz wrote:
I am building a new system using an Kingston 240GB SSD drive I pulled from my
notebook (when I had to upgrade to a 500GB SSD drive). Centos install went
fine and ran for a couple days then got errors on the console. Here is an
example:
[168176.995064] sd 0:0:0:0:
If it's a bad sector problem, you'd write to sector 17066160 and see if the
drive complies or spits back a write error. It looks like a bad sector in
that the same LBA is reported each time but I've only ever seen this with
both a read error and a UNC error. So I'm not sure it's a bad sector.
I am building a new system using an Kingston 240GB SSD drive I pulled
from my notebook (when I had to upgrade to a 500GB SSD drive). Centos
install went fine and ran for a couple days then got errors on the
console. Here is an example:
[168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result:
31 matches
Mail list logo