Re: [CentOS] Centos 7 specific cure for Spamassassin DNS lookup problem

[Gary Stainburn]

On Thursday 10 August 2017 09:21:31 Gary Stainburn wrote:
> I have the following error message in my /var/log/spamd
>
> spf: lookup failed: available_nameservers: No DNS servers available!
>
> Having Googled the error message I've found a number of responses which
> involve patching Perl or Spamassassin or other cures.
>
> Before I start changing things I was wondering if there was a Centos 7
> specific resolution. Where possible, on production machines I prefer to
> stay with RPM's rather than amending software directly.
>
> Also, many of these responses are over 10 years old, so I'm a little
> sceptical about their success today.

One of the solutions that I've found is to add dns_server entries into the 
config file. As this did not entail updating the software this is the option 
I've chosen.

This has fixed the original 'spf' error message, but now gives me a different 
error message. I now get one or more 

Use of uninitialized value $rr_type in string eq 
at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/AskDNS.pm line 592.

I'm now looking into this one, but any assistance would be appreciated.

Gary
-- 
https://fundraise.cancerresearchuk.org/page/garys-march-march
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[John Hodrien]

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

Re: [CentOS] Errors on an SSD drive

[Chris Murphy]

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 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.
> >
> > What is DID_BAD_TARGET?
>
> I have no experience on how to force a write to a specific sector and
> not cause other problems.  I suspect that this sector is in the /
> partition:
>
> Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk label type: dos
> Disk identifier: 0xc89d
>
> Device Boot  Start End  Blocks   Id  System
> /dev/sda12048 2099199 1048576   83  Linux
> /dev/sda2 2099200 4196351 1048576   82  Linux swap /
> Solaris
> /dev/sda3 4196352   468862127   232332888   83  Linux
>

LBA 17066160 would be on sda3.

dd if=/dev/sda skip=17066160 count=1 2>/dev/null | hexdump -C

That'll read that sector and display hex and ascii. If you recognize the
contents, it's probably user data. Otherwise, it's file system metadata or
a system binary.

If you get nothing but an I/O error, then it's lost so it doesn't matter
what it is, you can definitely overwrite it.

dd if=/dev/zero of=/dev/sda seek=17066160 count=1

If you want an extra confirmation, you can first do 'smartctl -t long
/dev/sda' and then after the prescribed testing time, which is listed,
check it again with 'smartct -a /dev/sda' and see if the test completed, or
if under self-test log section, it shows it was aborted and lists a number
under the LBA_of_first_error column.



> But I don't know where it is in relation to the way the drive was
> formatted in my notebook.  I think it would have been in the / partition.
>




>
> > And what do you get for
> > smartctl -x 
>
> About 17KB of output?


Can you attach it as a file to the list? If the list won't accept the
attachment, put it up on fpaste.org or pastebin or something like that.
MUA's tend to nerf the output so don't paste it into an email.





> I don't know how to read what it is saying, but
> noted in the beginning:
>
> Write SCT (Get) XXX Error Recovery Control Command failed: scsi error
> badly formed scsi parameters
>
> Don't know what this means...
>
> BTW, the system is a Cubieboard2 armv7 SoC running Centos7-armv7hl. This
> is the first time I have used an SSD on a Cubie, but I know it is
> frequently done.  I would have to ask on the Cubie forum what others
> experience with SSDs have been.
>

It's very common. I think this is just an ordinary bad sector, if that LBA
value is consistent. If it's a new SSD it's slightly concerning. You can
either keep an eye on it, or put a little pressure on the manufacturer or
place of purchase that you have a bad sector and would like to swap out the
unit.

SSD's, in particular SD Cards (which you're not using, which is noted as
/dev/mmcblk0...) store you data as a probabilistic representation, and
through a lot of magic, the probability of retrieving your data correctly
from SSD is made very high. Almost deterministic.

The magic is in the firmware, and so there's some possibility any given SSD
problem is related to a firmware bug. So it's worth comparing the firmware
reported by smartctl and what the manufacturer has, and then their
changelog. Most have a way to update firmware without Windows, but don't
have images that will boot an arm board, usually the "universal" updater is
based on FreeDOS funny enough. You'd need to stick the SSD in an x86
computer to do this. Hilariously perverse, I did this with a Samsung 830
SSD a while back, sticking it into a Macbook Pro, and burned that firmware
ISO onto a DVD-RW, and it booted that Mac (using the firmware's BIOS
compatibility support module) and updated the SSD's firmware without a
problem.



Chris Murphy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Robert Moskowitz]

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 is obvious as soon as the buffer is full), and
never, never put a swap partition on it, the high activity will wear it
out rather quickly.  might also check cables, often a problem
particularly if they are older sata cables being run at a possibly
higher than rated speed.

When working with a Cubieboard SoC (or most of the other armv7 boards),
you tend to have everything hanging out:
http://medon.htt-consult.com/~rgm/cubieboard/cubietower-2.JPG

I have checked the cables and they are all tight.


in any case, reformating it might not be a bad idea, and you can always
use the command line program badblocks to exercise and test it.

I will have to look into that.


Here's a thought: I've not done this, but could you use smartctl to check
the drive?


Other than the 17K output from smartctl -x, what do you recommend?


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[hw]

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 console.  Here is an 
example:

[168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK
[168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0 00 00 
08 00
[168177.011615] blk_update_request: I/O error, dev sda, sector 17066160
[168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK
[168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 b0 00 00 
08 00
[168487.551206] blk_update_request: I/O error, dev sda, sector 17066160
[168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET 
driverbyte=DRIVER_OK
[168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 b0 00 00 
08 00
[168787.830544] blk_update_request: I/O error, dev sda, sector 17066160

Eventually, I could not do anything on the system.  Not even a 'reboot'.  I had 
to do a cold power cycle to bring things back.

Is there anything to do about this or trash the drive and start anew?


Make sure the cables and power supply are ok.  Try the drive in another machine
that has a different controller to see if there is an incompatibility between
the drive and the controller.

You could make a btrfs file system on the whole device: that should say that
a trim operation is performed for the whole device.  Maybe that helps.


This is a Centos7-armv7hl install which is done by dd the provided image onto a 
drive, so really can't alter the provided file systems much other than to 
resize them.  What I have is:


Perhaps there´s some incompatibility on this architecture.

BTW, that the cables sit tight doesn´t mean they are good.




Model: ATA KINGSTON SV300S3 (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End SizeType File system Flags
 1  1049kB  1075MB  1074MB  primary  ext3
 2  1075MB  2149MB  1074MB  primary  linux-swap(v1)
 3  2149MB  240GB   238GB   primary  ext4






If the errors persist, replace the drive.  I´d use Intel SSDs because they
seam to have the least problems with broken firmwares.  Do not use SSDs with
hardware RAID controllers unless the SSDs were designed for this application.





___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 7 specific cure for Spamassassin DNS lookup problem

[Paul Heinlein]

On Thu, 10 Aug 2017, Gary Stainburn wrote:


I have the following error message in my /var/log/spamd

spf: lookup failed: available_nameservers: No DNS servers available!

Having Googled the error message I've found a number of responses 
which involve patching Perl or Spamassassin or other cures.


Before I start changing things I was wondering if there was a Centos 
7 specific resolution. Where possible, on production machines I 
prefer to stay with RPM's rather than amending software directly.


I run SpamAssassin on CentOS 7; the SPF plugin is loaded via 
/etc/mail/spamassassin/init.pre. I have no trouble with spf at all.


Is it possible the problem is with local DNS resolution?

--
Paul Heinlein <> heinl...@madboa.com <> https://www.madboa.com/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Chris Murphy]

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 hardware problem. Btrfs is explicitly optimized for SSD, the
maintainers worked for FusionIO for several years of its development. If
the drive is silently corrupting data, Btrfs will pretty much immediately
start complaining where other filesystems will continue. Bad RAM can also
result in scary warnings where you don't with other filesytems. And I've
been using it in numerous SSDs for years and NVMe for a year with zero
problems.

On CentOS though, I'd get newer btrfs-progs RPM from Fedora, and use either
an elrepo.org kernel, a Fedora kernel, or build my own latest long-term
from kernel.org. There's just too much development that's happened since
the tree found in RHEL/CentOS kernels.

Also FWIW Red Hat is deprecating Btrfs, in the RHEL 7.4 announcement.
Support will be removed probably in RHEL 8. I have no idea how it'll affect
CentOS kernels though. It will remain in Fedora kernels.

Anyway, blkdiscard can be used on an SSD, whole or partition to zero them
out. And at least recent ext4 and XFS mkfs will do a blkdisard, same as
mksfs.btrfs.


Chris Murphy






> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=icon
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=link
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Wed, Aug 9, 2017 at 1: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 example:
> >>
> >> [168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result:
> >> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> >> [168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0
> >> 00 00 08 00
> >> [168177.011615] blk_update_request: I/O error, dev sda, sector 17066160
> >> [168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result:
> >> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> >> [168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 b0
> >> 00 00 08 00
> >> [168487.551206] blk_update_request: I/O error, dev sda, sector 17066160
> >> [168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result:
> >> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> >> [168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 b0
> >> 00 00 08 00
> >> [168787.830544] blk_update_request: I/O error, dev sda, sector 17066160
> >>
> >> Eventually, I could not do anything on the system.  Not even a 'reboot'.
> >> I had to do a cold power cycle to bring things back.
> >>
> >> Is there anything to do about this or trash the drive and start anew?
> >>
> >
> > Make sure the cables and power supply are ok.  Try the drive in another
> > machine
> > that has a different controller to see if there is an incompatibility
> > between
> > the drive and the controller.
> >
> > You could make a btrfs file system on the whole device: that should say
> > that
> > a trim operation is performed for the whole device.  Maybe that helps.
> >
> > If the errors persist, replace the drive.  I悲 use Intel SSDs because they
> > seam to have the least problems with broken firmwares.  Do not use SSDs
> > with
> > hardware RAID controllers unless the SSDs were designed for this
> > application.
> >
> >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> >
>
>
> --
> [image: photo]
> Mark Haney
> Network Engineer at NeoNova
> 919-460-3330 <(919)%20460-3330> (opt 1) • mark.ha...@neonova.net
> www.neonova.net 
>   
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] E-invoicing to OpenPeppol with Oxalis on CentOS anyone ?

[Paul Schoonderwoerd]

Hello list,

I'm desperately trying to get the latest Oxalis software
(https://github.com/difi/oxalis )
to run in Tomcat on CentOS 6.9 but I'm getting a obscure Java error. Something 
about a a method not found:

Java.lang.NoSuchMethodError: 
sun.security.provider.certpath.OCSP.check(Ljava/security/cert/X509Certif 

Has anyone succesfully implemented this on CentOS 6.x ?

Tomcat is running fine behind Apache. All software up to date.
Tried many things already, also install Oxalis from source but that fails with 
different problems.
I found that OSCP checking is default disabled in Java (true ?) and tried to 
enable it with by adding the commandline switches:
java -Dcom.sun.security.enableCRLDP=true \
-Dcom.sun.net.ssl.checkRevocation=true

but no luck

I filed a bug report on github, details about the exact error:
https://github.com/difi/oxalis/issues/297

Any help appreciated.

-- 
Paul
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Centos 7 specific cure for Spamassassin DNS lookup problem

[Gary Stainburn]

I have the following error message in my /var/log/spamd

spf: lookup failed: available_nameservers: No DNS servers available!

Having Googled the error message I've found a number of responses which 
involve patching Perl or Spamassassin or other cures. 

Before I start changing things I was wondering if there was a Centos 7 
specific resolution. Where possible, on production machines I prefer to stay 
with RPM's rather than amending software directly.

Also, many of these responses are over 10 years old, so I'm a little sceptical 
about their success today.

Gary
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[John Hodrien]

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
partition on it, the high activity will wear it out rather quickly.


I know this is common doctrine, but is this still generally held true?

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.


might also check cables, often a problem particularly if they are older sata
cables being run at a possibly higher than rated speed.  in any case,
reformating it might not be a bad idea, and you can always use the command
line program badblocks to exercise and test it.


Exercising an SSD?

smartctl will give you sensible information on what the drive thinks of
itself, and will give you actual figures on wear levelling and such like.


keep in mind the drive will invisibly remap any bad sectors if possible.  if
the reported size of the drive is smaller than it should be the drive has
run out of spare blocks and dying blocks are being removed from the storage
place with no replacements.


Coo, I've never seen a disk actually shrink due to failed sectors.  I don't
think I've got an SSD into a worn state yet to see this.

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] gluster-containers with CentOS and Gluster 3.11

[Christopher Schmidt]

Hi,

I am trying to get a glusterfs container based on CentOS and GlusterFS
version 3.11 (https://github.com/gluster/gluster-containers)

But there is no centos-release-gluster311 package, right?
Or have I missed something?

How can I yum install version 3.11?

best Christopher
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 7 specific cure for Spamassassin DNS lookup problem

[Phil Perry]

On 10/08/17 15:37, Paul Heinlein wrote:

On Thu, 10 Aug 2017, Gary Stainburn wrote:


I have the following error message in my /var/log/spamd

spf: lookup failed: available_nameservers: No DNS servers available!

Having Googled the error message I've found a number of responses 
which involve patching Perl or Spamassassin or other cures.


Before I start changing things I was wondering if there was a Centos 7 
specific resolution. Where possible, on production machines I prefer 
to stay with RPM's rather than amending software directly.


I run SpamAssassin on CentOS 7; the SPF plugin is loaded via 
/etc/mail/spamassassin/init.pre. I have no trouble with spf at all.


Is it possible the problem is with local DNS resolution?



Same here, no issues with spamassassin and SPF.

In addition to Paul's question which seems like the most obvious initial 
avenue of investigation, I assume you have perl-Mail-SPF and 
perl-Net-DNS installed? They should be as both are deps for the 
spamassassin package.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Warren Young]

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 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 be used more productively; by the buffer cache, if nothing 
else.

I once used a web application server on a headless VPS that still had GUI 
libraries linked to its binary because one of the underlying technologies it 
uses was also used in a GUI app, and it was too difficult to tear all that GUI 
code out, even if it was never called.  Because the VPS technology didn’t 
support swap, I directly paid the price for those megs of unused (and 
unusable!) libraries in my monthly VPS rental fees.

> Coo, I've never seen a disk actually shrink due to failed sectors.  I don't
> think I've got an SSD into a worn state yet to see this.

Me, neither.  I’m pretty sure the spare sector pool’s size isn’t reported to 
the OS, and the drive isn’t allowed to dip into the sectors it does expose 
externally for spares.  

When the spare pool is used up, the drive just starts failing in a way that 
even SMART can see.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] BIND 9.9 RRL

[Leon Fauster]

> Am 10.08.2017 um 21:00 schrieb Mark Haney :
> 
> I can't seem to find anything clear on this, but is the C7 version of BIND 
> 9.9 built with Request Rate Limiting?


_Response_ Rate Limiting - I think its possible since EL6:

https://access.redhat.com/errata/RHSA-2013:0550

--
LF




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[John R Pierce]

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 be used more productively; by the buffer cache, if nothing 
else.


most modern virtual memory OS's don't swap out unused pages, instead, 
they swap IN accessed pages directly from the executable file.  only 
thing written to swap are 'dirty' pages that have been changed since 
loading.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Warren Young]

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 
voltage potential which can be interpreted as some number of 1 or 0 bits, often 
3 bits or more.

Between that fact and wear-leveling, you can’t take a simple voltage 
measurement on a data cell and say, “This cell contains 011.”  You need more 
smarts about what’s going on to turn the voltage reading into the correct value.

As the drive’s data cells wear out, the drive’s ability to do that correctly 
and reliably degrade.  Thus cell death, thus drive death, thus filesystem 
death, thus backups, else sadness.

And please don’t top-post.

A: Yes.

Q: Are you sure?

A: Because it makes the flow of conversation more difficult to read.

Q: Why shouldn’t I top-post?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[J Martin Rushton]

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
>> swapped out quickly so that the precious RAM can be used more
>> productively; by the buffer cache, if nothing else.
> 
> most modern virtual memory OS's don't swap out unused pages, instead,
> they swap IN accessed pages directly from the executable file.  only
> thing written to swap are 'dirty' pages that have been changed since
> loading.
> 
Modern?  They've been doing that since I did my VMS theory 30-odd years ago.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Warren Young]

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 memory OS's don't swap out unused pages, instead, they 
> swap IN accessed pages directly from the executable file.  only thing written 
> to swap are 'dirty' pages that have been changed since loading.

Is that not a distinction without a difference in my case?

Let’s say I have a system with 256 MB of free user-space RAM, and I have a 
binary that happens to be nearly 256 MB on disk, between the main executable 
and all the libraries it uses.

Question: Can my program allocate any dynamic RAM?

The OS’s VMM is free to use addresses beyond 0-256 MB, but since we’ve said 
there is no swap space, everything swapped in must still be assigned a place in 
physical RAM *somewhere*.

Is there a meaningful distinction between:

Scenario 1: The application’s first few executable pages are loaded from disk, 
a few key libraries are loaded, then the application does a dynamic memory 
allocation, then somehow causes all the rest of the executable pages to be 
loaded, running the system out of RAM.

Scenario 2: The application is entirely loaded into RAM, nearly filling it, 
then the application attempts a large dynamic memory allocation, causing an OOM 
error.

Regardless of the answer to these questions, I can tell you that switching that 
web site to a more efficient web application stack allowed us to shrink the VPS 
from a 256 MB plan, under which it would occasionally crash and require a 
reboot, to a 64 MB plan, under which the site has been rock-solid.  Same VPS 
provider, same web site content, same user-facing functionality.

If I’d had the ability to assign swap space, I probably could have gotten away 
with a 64 MB VPS plan with the inefficient web technology, too.  They gave me 
plenty of disk space with that plan.

(And no, swapon /some-file is no solution here.  The VPS technology simply 
didn’t allow swap space, even from a swap file on one of the system disks.  It 
wasn’t simply an inability to add a swap partition.)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Acroread9 crash in CentOS7

[Ian Mortimer]

On Fri, 11 Aug 2017, wwp wrote:


I'm still using acroread on CentOS6 (other computers than this C7 one)
and never had a single problem.


It might be still usable but it isn't secure.


---
Ian
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[mad.scientist.at.large]

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 today!
https://tutanota.com

10. Aug 2017 10:06 by li...@colorremedies.com:


> On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz <> r...@htt-consult.com> > 
> wrote:
>
>> 
>>
> SSD's, in particular SD Cards (which you're not using, which is noted as
> /dev/mmcblk0...) store you data as a probabilistic representation, and
> through a lot of magic, the probability of retrieving your data correctly
> from SSD is made very high. Almost deterministic.
>
> The magic is in the firmware, and so there's some possibility any given SSD
> problem is related to a firmware bug. So it's worth comparing the firmware
> reported by smartctl and what the manufacturer has, and then their
> changelog. Most have a way to update firmware without Windows, but don't
> have images that will boot an arm board, usually the "universal" updater is
> based on FreeDOS funny enough. You'd need to stick the SSD in an x86
> computer to do this. Hilariously perverse, I did this with a Samsung 830
> SSD a while back, sticking it into a Macbook Pro, and burned that firmware
> ISO onto a DVD-RW, and it booted that Mac (using the firmware's BIOS
> compatibility support module) and updated the SSD's firmware without a
> problem.
>
>
>
> Chris Murphy
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] BIND 9.9 RRL

[Anand Buddhdev]

On 10/08/2017 21:00, Mark Haney wrote:

> I can't seem to find anything clear on this, but is the C7 version of
> BIND 9.9 built with Request Rate Limiting?

Run "named -V" and it will output the features it was compiled with. See
if RRL is in there.

Regards,
Anand
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Centos7 - Mate : screensaver troubles after Freeipa-config

[johan . vermeulen7]

Hello All, 

these days one of my tasks is connecting some Centos7 laptops to Freeipa, also 
running on Centos7. 
After doing that, some users report nog being able to unlock their screens. 
Only after reboot are they able to login again. 

I see this em in /var/log/secure: 

Aug 10 13:34:37  mate-screensaver-dialog: pam_sss(mate-screensaver:auth): 
authentication failure; logname= uid=382900663 euid=382900663 tty=:0.0 ruser= 
rhost= user=* 
Aug 10 13:34:37  mate-screensaver-dialog: pam_sss(mate-screensaver:auth): 
received for user **: 17 (Fout tijdens het instellen van 
legitimatiegegevens van gebruiker) 
Aug 10 13:34:37  mate-screensaver-dialog: gkr-pam: the password for the 
login keyring was invalid. 

Out of the 50 people or so I now have connected to Freeipa, I received some 5 
reports. 
All users are on fully updated Centos7 machines configured with epel-provided 
Mate desktop. 

I see a lot of these problems when googling this, but none in Centos. 

Help would be very much appreciated. 

Greetings, J. 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[m . roth]

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), and
>> never, never put a swap partition on it, the high activity will wear it
>> out rather quickly.  might also check cables, often a problem
>> particularly if they are older sata cables being run at a possibly
>> higher than rated speed.
>
> When working with a Cubieboard SoC (or most of the other armv7 boards),
> you tend to have everything hanging out:
> http://medon.htt-consult.com/~rgm/cubieboard/cubietower-2.JPG
>
> I have checked the cables and they are all tight.
>
>> in any case, reformating it might not be a bad idea, and you can always
>> use the command line program badblocks to exercise and test it.
>
> I will have to look into that.
>
Here's a thought: I've not done this, but could you use smartctl to check
the drive?

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[hw]

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 some
improvement.

I have the system on SSDs at home and data on spinning disks, so far no problems
with btrfs.  Do I need to worry now?





Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Aug 9, 2017 at 1: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 example:

[168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168177.011615] blk_update_request: I/O error, dev sda, sector 17066160
[168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168487.551206] blk_update_request: I/O error, dev sda, sector 17066160
[168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168787.830544] blk_update_request: I/O error, dev sda, sector 17066160

Eventually, I could not do anything on the system.  Not even a 'reboot'.
I had to do a cold power cycle to bring things back.

Is there anything to do about this or trash the drive and start anew?



Make sure the cables and power supply are ok.  Try the drive in another
machine
that has a different controller to see if there is an incompatibility
between
the drive and the controller.

You could make a btrfs file system on the whole device: that should say
that
a trim operation is performed for the whole device.  Maybe that helps.

If the errors persist, replace the drive.  I悲 use Intel SSDs because they
seam to have the least problems with broken firmwares.  Do not use SSDs
with
hardware RAID controllers unless the SSDs were designed for this
application.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos







___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Acroread9 crash in CentOS7

[wwp]

Hello Ian,


On Thu, 10 Aug 2017 02:59:36 + Ian Mortimer  wrote:

> On Tue, 2017-08-08 at 23:13 +0200, wwp wrote:
> 
> > I'm getting a crash with acroread on my CentOS7
> > (AdobeReader_enu-9.5.5-1.i486).
> > I install the official rpms from
> > ftp://ftp.adobe.com/pub/adobe/reader/unix/,
> > tried 9.5.5, and former v9, v8, v7.  
> 
> Support for AdobeReader on Linux ended more than 4 years ago. It would
> be better to use evince, atril or okular.

Well, yes, I've set Atril, which is installed by default, to be the
default app now. Thanks :-)

I'm still using acroread on CentOS6 (other computers than this C7 one)
and never had a single problem.


Regards,

-- 
wwp


pgp93LtbNd_qm.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] BIND 9.9 RRL

[Mark Haney]

I can't seem to find anything clear on this, but is the C7 version of 
BIND 9.9 built with Request Rate Limiting?



--
Mark Haney
Network Engineer at NeoNova
919-460-3330 option 1
mark.ha...@neonova.net
www.neonova.net

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[m . roth]

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 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.
>> >
>> > What is DID_BAD_TARGET?
>>
>> I have no experience on how to force a write to a specific sector and
>> not cause other problems.  I suspect that this sector is in the /
>> partition:
>>
>> Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 sectors
>> Units = sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disk label type: dos
>> Disk identifier: 0xc89d
>>
>> Device Boot  Start End  Blocks   Id  System
>> /dev/sda12048 2099199 1048576   83  Linux
>> /dev/sda2 2099200 4196351 1048576   82  Linux swap /
>> Solaris
>> /dev/sda3 4196352   468862127   232332888   83  Linux
>>
>
> LBA 17066160 would be on sda3.
>
> dd if=/dev/sda skip=17066160 count=1 2>/dev/null | hexdump -C
>
> That'll read that sector and display hex and ascii. If you recognize the
> contents, it's probably user data. Otherwise, it's file system metadata or
> a system binary.

Yeah, I was going to suggest you find out what that's part of. Try this link
, which is about
identifying what an unreadable sector is part of.

 mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 7 specific cure for Spamassassin DNS lookup problem

[Gordon Messmer]

On 08/10/2017 01:21 AM, Gary Stainburn wrote:

I have the following error message in my /var/log/spamd

spf: lookup failed: available_nameservers: No DNS servers available!



Try starting spamassassin later.  Run "systemctl edit 
spamassassin.service" and insert two lines:


[Unit]
After=network-online.target

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Robert Moskowitz]

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 UNC error. So I'm not sure it's a bad sector.

What is DID_BAD_TARGET?


I have no experience on how to force a write to a specific sector and 
not cause other problems.  I suspect that this sector is in the / partition:


Disk /dev/sda: 240.1 GB, 240057409536 bytes, 468862128 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xc89d

   Device Boot  Start End  Blocks   Id  System
/dev/sda12048 2099199 1048576   83  Linux
/dev/sda2 2099200 4196351 1048576   82  Linux swap / Solaris
/dev/sda3 4196352   468862127   232332888   83  Linux

But I don't know where it is in relation to the way the drive was 
formatted in my notebook.  I think it would have been in the / partition.




And what do you get for
smartctl -x 


About 17KB of output?  I don't know how to read what it is saying, but 
noted in the beginning:


Write SCT (Get) XXX Error Recovery Control Command failed: scsi error 
badly formed scsi parameters


Don't know what this means...

BTW, the system is a Cubieboard2 armv7 SoC running Centos7-armv7hl. This 
is the first time I have used an SSD on a Cubie, but I know it is 
frequently done.  I would have to ask on the Cubie forum what others 
experience with SSDs have been.





Chris Murphy

On Wed, Aug 9, 2017, 8:03 AM 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: [sda] tag#14 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168177.011615] blk_update_request: I/O error, dev sda, sector 17066160
[168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168487.551206] blk_update_request: I/O error, dev sda, sector 17066160
[168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168787.830544] blk_update_request: I/O error, dev sda, sector 17066160

Eventually, I could not do anything on the system.  Not even a
'reboot'.  I had to do a cold power cycle to bring things back.

Is there anything to do about this or trash the drive and start anew?

Thanks

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Robert Moskowitz]

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 example:


[168176.995064] sd 0:0:0:0: [sda] tag#14 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 
b0 00 00 08 00

[168177.011615] blk_update_request: I/O error, dev sda, sector 17066160
[168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 
b0 00 00 08 00

[168487.551206] blk_update_request: I/O error, dev sda, sector 17066160
[168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result: 
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 
b0 00 00 08 00

[168787.830544] blk_update_request: I/O error, dev sda, sector 17066160

Eventually, I could not do anything on the system.  Not even a 
'reboot'.  I had to do a cold power cycle to bring things back.


Is there anything to do about this or trash the drive and start anew?


Make sure the cables and power supply are ok.  Try the drive in 
another machine
that has a different controller to see if there is an incompatibility 
between

the drive and the controller.

You could make a btrfs file system on the whole device: that should 
say that

a trim operation is performed for the whole device.  Maybe that helps.


This is a Centos7-armv7hl install which is done by dd the provided image 
onto a drive, so really can't alter the provided file systems much other 
than to resize them.  What I have is:


Model: ATA KINGSTON SV300S3 (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End SizeType File system Flags
 1  1049kB  1075MB  1074MB  primary  ext3
 2  1075MB  2149MB  1074MB  primary  linux-swap(v1)
 3  2149MB  240GB   238GB   primary  ext4






If the errors persist, replace the drive.  I´d use Intel SSDs because 
they
seam to have the least problems with broken firmwares.  Do not use 
SSDs with
hardware RAID controllers unless the SSDs were designed for this 
application.



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]

[KM]

 
Never saw this emailDid anyone get it?  anyone know how to fix this?thanks 
again.

  From: KM 
 To: CentOS mailing list  
 Sent: Monday, August 7, 2017 11:26 AM
 Subject: Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
  
All,This happens on all of our CentOS 7 VMs.  but as stated in the email trail, 
the file softlockup_thresh does not exist.  Should it be added?  What is the 
best way to get rid of this behavior.
Thanks in advance and sorry if I missed something along the way.KM

  From: correomm 
 To: CentOS mailing list  
 Sent: Thursday, August 18, 2016 1:55 PM
 Subject: Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
  
Yes, I tried it, but does not exists:

vmguest # cat /proc/sys/kernel/softlockup_thresh
cat: /proc/sys/kernel/softlockup_thresh: No such file or directory

On Thu, Aug 18, 2016 at 2:06 PM, Carlos A. Carnero Delgado <
carloscarn...@gmail.com> wrote:

> 2016-08-18 12:39 GMT-04:00 correomm :
>
> > This bug is reported only on the VM's with CentOS 7 running on on VMware
> > ESXi 5.1.
> > The vSphere performance graph shows high CPU consume and disk activity
> only
> > on VM's with CentOS 7. Sometimes I can not connect remotely with ssh
> > (timeout error).
> >
>
> I'm also seeing those errors in several servers, running under 5.5.
> Currently investigating if this
>  do?language=en_US=displayKC=1009996>
> has anything to do (the resource overcommit bit).
>
> HTH,
> Carlos.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


   

|  | Virus-free. www.avg.com  |



   

   
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Errors on an SSD drive

[Robert Moskowitz]

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), and never, never put a swap partition 
on it, the high activity will wear it out rather quickly.  might also check 
cables, often a problem particularly if they are older sata cables being run at 
a possibly higher than rated speed.


When working with a Cubieboard SoC (or most of the other armv7 boards), 
you tend to have everything hanging out: 
http://medon.htt-consult.com/~rgm/cubieboard/cubietower-2.JPG


I have checked the cables and they are all tight.


in any case, reformating it might not be a bad idea, and you can always use the 
command line program badblocks to exercise and test it.


I will have to look into that.


   keep in mind the drive will invisibly remap any bad sectors if possible.  if 
the reported size of the drive is smaller than it should be the drive has run 
out of spare blocks and dying blocks are being removed from the storage place 
with no replacements.

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

9. Aug 2017 18:44 by elie...@ngtech.co.il:



I have yet to see a SSD read\write error which wasn't related to disk issues
like a bad sector but the controller might have an issue with the drive.
To verify it you will need to burn some read\write IOPS of the drive but if
it's under warranty then it's better to verify it now then later.

Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: > elie...@ngtech.co.il



-Original Message-
From: CentOS [> 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 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:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168177.004050] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168177.011615] blk_update_request: I/O error, dev sda, sector 17066160
[168487.534510] sd 0:0:0:0: [sda] tag#17 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168487.543576] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168487.551206] blk_update_request: I/O error, dev sda, sector 17066160
[168787.813941] sd 0:0:0:0: [sda] tag#20 FAILED Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[168787.822951] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 01 04 68 b0
00 00 08 00
[168787.830544] blk_update_request: I/O error, dev sda, sector 17066160

Eventually, I could not do anything on the system.  Not even a
'reboot'.  I had to do a cold power cycle to bring things back.

Is there anything to do about this or trash the drive and start anew?

Thanks

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos