dmesg command output

Dear All,

I am running opensuse with a SAN storage and gets following error with the “dmesg” command

TCP: Treason uncloaked! Peer 94.98.184.71:53838/58868 shrinks window 2440397230:2440411250. Repaired.
sdb: Current: sense key: Recovered Error
<<vendor>> ASC=0xe0 ASCQ=0x3ASC=0xe0 ASCQ=0x3

Any idea how to resolve this issue…

No resolution on this issue?

ghulamyaseen wrote:
> Any idea how to resolve this issue…

consider the possibility that others have encountered this error,
asked the same question, and it has been answered:

for example google the string


TCP: Treason uncloaked!

as in http://tinyurl.com/ybgn3wl

turned up: “This is just an informative message. It is not a problem
with the system. The message is informing the system administrator
that a remote system is not able to communicate correctly with the
system in question. It is a problem on the remote system. It indicates
that the system in question has received packets with incorrect TCP
information. It is caused by a remote host, or intermediate
firewall/NAT getting TCP behavior incorrectly. In the usual cases, the
only likely impact is a little performance drop on the connection.”
in a Red Hat forum http://tinyurl.com/ydso3hu which is all i need to
know, but you may (since it is YOUR machine) want to know more…

now, try this string


Current: sense key: Recovered Error

i don’t know much (anything) about it, but a quick scan tells me it
probably is something to do with a hardware error in your scsi
disk(s)…do you have a good backup plan in use?


palladium

yup, i have 80% of the data on other machine but am curious to know the resolution of it. Is it e2fsck that needs to be run on it…i have not tried it yet!

ghulamyaseen wrote:
> yup, i have 80% of the data on other machine but am curious to know the
> resolution of it. Is it e2fsck that needs to be run on it…i have
> not tried it yet!

i’m not sure which of the fsck family should be run (because i’ve
not yet seen you tell which file system you are using)…in fact, for
all i know none should be run until your backup is complete…

and, maybe the best course is complete your backup immediately and
then download the disk health checking utility ) provided by that
disk’s manufacturer…and, download it to a different drive (so as
not to overwrite data you need to keep)…

or maybe the maker’s utility says the disk is perfect–in which case
i’d guess one of the fsck routines would be in order…after the
backup is tested…


palladium