Discussion:
CCKD errors after installing Centos 4.2 s390x
(too old to reply)
kfhickel
2005-12-09 14:52:22 UTC
Permalink
Struggling with a problem, I've reinitialized the dasd a couple times
and reinstalled, not seeing any "real" disk errors on the physical
drives. I've set up a 3390-9 using -z compression, and don't get any
errors on the volume during installation of Centos, but when it's all
installed and I reboot, I start getting errors like the ones below,
they repeat throughout, and continue after rebooting again. After
awhile the zlinux starts mounting the filesystems read only because of
the errors.

This is with Hercules 3.02 hosted on FC4.

-Kelly

CentOS release 4.2 (Final)
Kernel 2.6.9-22.EL on an s390x

hercules1 login:
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670






------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/KIlPFB/vlQLAA/TtwFAA/W4wwlB/TM
--------------------------------------------------------------------~->
Greg Smith
2005-12-09 22:41:18 UTC
Permalink
Hi Kelly,

What is the size of your disk emulation file (from ls -l)?
What messages do you get from `cckdcdsk -3 -ro <file-name>'?
It could be that `cckdcdsk -3 <file-name>' will repair the file. I
suspect the error messages are coming from the garbage collector and
cckd thinks the file is larger than it actually is. Another option is
to add a shadow file so all updates go to the shadow file:

0120 3390 <file-name> sf=<shadow-file-name_1>

Greg
Post by kfhickel
Struggling with a problem, I've reinitialized the dasd a couple times
and reinstalled, not seeing any "real" disk errors on the physical
drives. I've set up a 3390-9 using -z compression, and don't get any
errors on the volume during installation of Centos, but when it's all
installed and I reboot, I start getting errors like the ones below,
they repeat throughout, and continue after rebooting again. After
awhile the zlinux starts mounting the filesystems read only because of
the errors.
This is with Hercules 3.02 hosted on FC4.
-Kelly
CentOS release 4.2 (Final)
Kernel 2.6.9-22.EL on an s390x
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/KIlPFB/vlQLAA/TtwFAA/W4wwlB/TM
--------------------------------------------------------------------~->
Kelly F. Hickel
2005-12-10 19:43:34 UTC
Permalink
Greg,

Below is some of the info you asked for. When I was trying
to copy the cckd file (before running cckdcdsk and fixing the errors) I
got an I/O error on the file, I checked /var/log/messages, and it looks
like I have real disk errors to deal with. Anyone remember how to check
for bad blocks and map them out in ext3??



-Kelly







*********************

All the errors generated by booting the system, then halting as soon as
it came up:



HHCCD001I Readahead thread 1 started: tid=06F74BB0, pid=18812

HHCCD001I Readahead thread 2 started: tid=02662BB0, pid=18812

HHCCD002I Writer thread 1 started: tid=037C7BB0, pid=18812

HHCCD002I Writer thread 2 started: tid=0495EBB0, pid=18812

HHCCD003I Garbage collector thread started: tid=0535FBB0, pid=18812

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD125E 0120 file[0] invalid trk hdr trk -1 buf 0x531f390:1119798182

HHCCD190E 0120 file[0] offset 0x2d8d97e7 unknown space: 1119798182

HHCCD210I size free nbr st reads writes l2reads hits
switches

HHCCD211I readaheads
misses

HHCCD212I
--------------------------------------------------------------------

HHCCD213I [*] 806741396 1% 7712 2125 997 443 1898
2972

HHCCD214I 1080
387

HHCCD215I /hercules/DASD/centos42_disks/centos.120.z

HHCCD216I [0] 806741396 1% 7712 rw 2125 997 443

HHCCD210I size free nbr st reads writes l2reads hits
switches

HHCCD211I readaheads
misses

HHCCD212I
--------------------------------------------------------------------

HHCCD213I [*] 790751 0% 0 26 11245 1422 20
40

HHCCD214I 12
2

HHCCD215I /hercules_vol2/DASD/centos42_disks/centos.121.z

HHCCD216I [0] 790751 0% 0 rw 26 11245 1422

HHCCD210I size free nbr st reads writes l2reads hits
switches

HHCCD211I readaheads
misses

HHCCD212I
--------------------------------------------------------------------

HHCCD213I [*] 29551970 3% 2 21 890 48 22
39

HHCCD214I 6
2

HHCCD215I /hercules/DASD/centos42_disks/centos.122

HHCCD216I [0] 29551970 3% 2 rw 21 890 48

HHCCD210I size free nbr st reads writes l2reads hits
switches

HHCCD211I readaheads
misses

HHCCD212I
--------------------------------------------------------------------

HHCCD213I [*] 34140270 3% 1 22 1007 33 22
39

HHCCD214I 7
3

HHCCD215I /hercules_vol2/DASD/centos42_disks/centos.123

HHCCD216I [0] 34140270 3% 1 rw 22 1007 33

HHCCD210I size free nbr st reads writes l2reads hits
switches

HHCCD211I readaheads
misses

HHCCD212I
--------------------------------------------------------------------

HHCCD213I [*] 786971 0% 0 22 11322 1236 21
39

HHCCD214I 6
4

HHCCD215I /hercules/DASD/centos42_disks/centos.124.z

HHCCD216I [0] 786971 0% 0 rw 22 11322 1236

HHCCD210I size free nbr st reads writes l2reads hits
switches

HHCCD211I readaheads
misses

HHCCD212I
--------------------------------------------------------------------

HHCCD213I [*] 791848 0% 0 24 10941 1377 20
39

HHCCD214I 7
2

HHCCD215I /hercules_vol2/DASD/centos42_disks/centos.125.z

HHCCD216I [0] 791848 0% 0 rw 24 10941 1377

HHCCD011I Readahead thread 1 stopping: tid=06F74BB0, pid=18812

HHCCD011I Readahead thread 2 stopping: tid=02662BB0, pid=18812

HHCCD013I Garbage collector thread stopping: tid=0535FBB0, pid=18812

HHCCD012I Writer thread 1 stopping: tid=037C7BB0, pid=18812

HHCCD012I Writer thread 2 stopping: tid=0495EBB0, pid=18812





*********************

output of cckdcsdk -3 -ro



[***@pillar centos42_disks]# cckdcdsk -3 -ro centos.120.z

cckdcdsk: read error track 6071: Success

l2[23,183] offset 0x19c8357 len 27060

cckdcdsk: track 13328 invalid header 0x1f24482ab0

l2[52,16] offset 0x2d8e03f7 len 14080

cckdcdsk: track 13330 invalid header 0xfb6bc89963

l2[52,18] offset 0x2d8dcfb7 len 13376

cckdcdsk: track 20651 invalid header 0x1119798182

l2[80,171] offset 0x2d8d97e7 len 14288

cckdcdsk: trk 20665 uncompress error, rc=-3;010561000a

l2[80,185] offset 0x2d2430e9 len 10731

cckdcdsk: read error track 49546: Success

l2[193,138] offset 0x2644fae0 len 15967

cckdcdsk: errors detected on read-only file

size 806741396 used 797272001 free 9469395 first 0x2ec7e number 7712

[***@pillar centos42_disks]#



*********************

output of ls -l



[***@pillar centos42_disks]# ls -l centos.120.z

-rw-r----- 1 root root 806741396 Dec 10 13:27 centos.120.z



*********************

syslog errors on host, "real" disk errors



Dec 10 13:32:51 pillar1 kernel: sd 0:0:1:0: SCSI error: return code =
0x8000002

Dec 10 13:32:51 pillar1 kernel: sdb: Current: sense key: Medium Error

Dec 10 13:32:51 pillar1 kernel: Additional sense: Read retries
exhausted

Dec 10 13:32:51 pillar1 kernel: Info fld=0x3425e5d

Dec 10 13:32:51 pillar1 kernel: end_request: I/O error, dev sdb, sector
54681175

Dec 10 13:32:58 pillar1 kernel: sd 0:0:1:0: SCSI error: return code =
0x8000002

Dec 10 13:32:58 pillar1 kernel: sdb: Current: sense key: Medium Error

Dec 10 13:32:58 pillar1 kernel: Additional sense: Read retries
exhausted

Dec 10 13:32:58 pillar1 kernel: Info fld=0x3425e5d

Dec 10 13:32:58 pillar1 kernel: end_request: I/O error, dev sdb, sector
54681176

Dec 10 13:35:51 pillar1 kernel: sd 0:0:1:0: SCSI error: return code =
0x8000002

Dec 10 13:35:51 pillar1 kernel: sdb: Current: sense key: Medium Error

Dec 10 13:35:51 pillar1 kernel: Additional sense: Read retries
exhausted

Dec 10 13:35:51 pillar1 kernel: Info fld=0x3425e5d

Dec 10 13:35:51 pillar1 kernel: end_request: I/O error, dev sdb, sector
54681176



_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Greg Smith
Sent: Friday, December 09, 2005 4:41 PM
To: hercules-390-***@public.gmane.org
Subject: Re: [hercules-390] CCKD errors after installing Centos 4.2
s390x



Hi Kelly,

What is the size of your disk emulation file (from ls -l)?
What messages do you get from `cckdcdsk -3 -ro <file-name>'?
It could be that `cckdcdsk -3 <file-name>' will repair the file. I
suspect the error messages are coming from the garbage collector and
cckd thinks the file is larger than it actually is. Another option is
to add a shadow file so all updates go to the shadow file:

0120 3390 <file-name> sf=<shadow-file-name_1>

Greg
Post by kfhickel
Struggling with a problem, I've reinitialized the dasd a couple times
and reinstalled, not seeing any "real" disk errors on the physical
drives. I've set up a 3390-9 using -z compression, and don't get any
errors on the volume during installation of Centos, but when it's all
installed and I reboot, I start getting errors like the ones below,
they repeat throughout, and continue after rebooting again. After
awhile the zlinux starts mounting the filesystems read only because of
the errors.
This is with Hercules 3.02 hosted on FC4.
-Kelly
CentOS release 4.2 (Final)
Kernel 2.6.9-22.EL on an s390x
HHCCD130E 0120 file[0] read incomplete, offset 0x19bc0b8: read 57160
expected 98670
Philipp Brenner
2005-12-12 15:28:26 UTC
Permalink
Post by Kelly F. Hickel
Greg,
Below is some of the info you asked for. When I was trying
to copy the cckd file (before running cckdcdsk and fixing the errors) I
got an I/O error on the file, I checked /var/log/messages, and it looks
like I have real disk errors to deal with. Anyone remember how to check
for bad blocks and map them out in ext3??
fsck.ext3 -cf /dev/sdb
This will check for bad blocks and run even if the fs is marked 'clean'.
Remember to unmount the device first! You might want to see how the drive
is doing with something like http://smartmontools.sourceforge.net/
or some tool supplied by the drive's manufacturer.

HTH
Philipp



------------------------ Yahoo! Groups Sponsor --------------------~-->
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/2jUsvC/tzNLAA/TtwFAA/W4wwlB/TM
--------------------------------------------------------------------~->
Alessandro Brezzi
2005-12-12 16:27:04 UTC
Permalink
... smartmontool use the SMART protocol of almost all the modern disk; the
SATA drives are not currently supported.
To examine and repair the ext2/3 fs refer to chkfs (man chkfs)

HTH

Alessandro
Post by Philipp Brenner
Post by Kelly F. Hickel
Greg,
Below is some of the info you asked for. When I was trying
to copy the cckd file (before running cckdcdsk and fixing the errors) I
got an I/O error on the file, I checked /var/log/messages, and it looks
like I have real disk errors to deal with. Anyone remember how to check
for bad blocks and map them out in ext3??
fsck.ext3 -cf /dev/sdb
This will check for bad blocks and run even if the fs is marked 'clean'.
Remember to unmount the device first! You might want to see how the drive
is doing with something like http://smartmontools.sourceforge.net/
or some tool supplied by the drive's manufacturer.
HTH
Philipp
http://groups.yahoo.com/group/hercules-390
http://www.conmicro.cx/hercules
------------------------------
YAHOO! GROUPS LINKS
- Visit your group "hercules-390<http://groups.yahoo.com/group/hercules-390>"
on the web.
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/>.
------------------------------
--
Alessandro Brezzi


[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/KIlPFB/vlQLAA/TtwFAA/W4wwlB/TM
--------------------------------------------------------------------~->
Kelly F. Hickel
2005-12-13 21:14:46 UTC
Permalink
FYI, I don't know now if this disk is bad, or if something odd is going
on with the file structures (although I suspect the former). I've fsck
-ck'd the drive twice now, and I keep seeming to end up with a block
owned by multiple files. I'm going to repair the cckd file and copy it
to another drive, then remove the questionable drive, but I wanted to
post the output of the fsck pass here, in case something "more subtle"
is going on.....



[***@pillar1 /]# e2fsck -ck /dev/sdb1

e2fsck 1.38 (30-Jun-2005)

Checking for bad blocks (read-only test): done
091

Pass 1: Checking inodes, blocks, and sizes



Running additional passes to resolve blocks claimed by more than one
inode...

Pass 1B: Rescanning for multiply-claimed blocks

Multiply-claimed block(s) in inode 6802449: 7032768 7032777

Pass 1C: Scanning directories for inodes with multiply-claimed blocks.

Pass 1D: Reconciling multiply-claimed blocks

(There are 1 inodes containing multiply-claimed blocks.)



File /hercules/DASD/centos42_disks/hercules1_mq53_centos.120.z (inode
#6802449,

mod time Tue Dec 13 10:27:44 2005)

has 2 multiply-claimed block(s), shared with 1 file(s):

<The bad blocks inode> (inode #1, mod time Tue Dec 13 14:59:08
2005)

Clone multiply-claimed blocks<y>? yes



Error reading block 7032777 (Attempt to read block from filesystem
resulted in

hort read). Ignore error<y>? yes



Force rewrite<y>? yes



Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

Free blocks count wrong for group #0 (22503, counted=22501).

Fix<y>? yes



Free blocks count wrong for group #214 (7767, counted=7769).

Fix<y>? yes





/sdb: ***** FILE SYSTEM WAS MODIFIED *****

/sdb: 36/8928192 files (5.6% non-contiguous), 608398/8922091 blocks
--
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh-zEt/***@public.gmane.org

_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Alessandro Brezzi
Sent: Monday, December 12, 2005 10:27 AM
To: hercules-390-***@public.gmane.org
Subject: Re: [hercules-390] CCKD errors after installing Centos 4.2
s390x



... smartmontool use the SMART protocol of almost all the modern disk;
the
SATA drives are not currently supported.
To examine and repair the ext2/3 fs refer to chkfs (man chkfs)

HTH

Alessandro
Post by Philipp Brenner
Post by Kelly F. Hickel
Greg,
Below is some of the info you asked for. When I was
trying
Post by Philipp Brenner
Post by Kelly F. Hickel
to copy the cckd file (before running cckdcdsk and fixing the errors)
I
Post by Philipp Brenner
Post by Kelly F. Hickel
got an I/O error on the file, I checked /var/log/messages, and it
looks
Post by Philipp Brenner
Post by Kelly F. Hickel
like I have real disk errors to deal with. Anyone remember how to
check
Post by Philipp Brenner
Post by Kelly F. Hickel
for bad blocks and map them out in ext3??
fsck.ext3 -cf /dev/sdb
This will check for bad blocks and run even if the fs is marked
'clean'.
Post by Philipp Brenner
Remember to unmount the device first! You might want to see how the
drive
Post by Philipp Brenner
is doing with something like http://smartmontools.sourceforge.net/
or some tool supplied by the drive's manufacturer.
HTH
Philipp
http://groups.yahoo.com/group/hercules-390
http://www.conmicro.cx/hercules
------------------------------
YAHOO! GROUPS LINKS
- Visit your group
"hercules-390<http://groups.yahoo.com/group/hercules-390>"
Post by Philipp Brenner
on the web.
hercules-390-unsubscribe-***@public.gmane.org<hercules-390-***@yahoog
roups.com?subject=Unsubscribe>
Post by Philipp Brenner
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/>.
------------------------------
--
Alessandro Brezzi


[Non-text portions of this message have been removed]
Gregg C Levine
2005-12-13 22:13:44 UTC
Permalink
Hello from Gregg C Levine
Kelly, obviously you know what you are doing. I'm not questioning
that. However, given the fluid nature of the files that Hercules
creates, I am questioning the ability of your host OS to manage the
files, and the disk drive. First off all which distribution is this?
And second of all, who makes your disk drive? And third can you repost
your Hercules configuration file, and of course which OS you are
running with Hercules.
--
Gregg C Levine hansolofalcon-XfrvlLN1Pqtfpb/***@public.gmane.org
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi
-----Original Message-----
On Behalf Of Kelly F. Hickel
Sent: Tuesday, December 13, 2005 4:15 PM
Subject: RE: [hercules-390] CCKD errors after installing Centos 4.2
s390x
FYI, I don't know now if this disk is bad, or if something odd is going
on with the file structures (although I suspect the former). I've fsck
-ck'd the drive twice now, and I keep seeming to end up with a block
owned by multiple files. I'm going to repair the cckd file and copy it
to another drive, then remove the questionable drive, but I wanted to
post the output of the fsck pass here, in case something "more
subtle"
is going on.....
e2fsck 1.38 (30-Jun-2005)
Checking for bad blocks (read-only test): done
091
Pass 1: Checking inodes, blocks, and sizes
Running additional passes to resolve blocks claimed by more than one
inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 6802449: 7032768 7032777
Pass 1C: Scanning directories for inodes with multiply-claimed
blocks.
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)
File /hercules/DASD/centos42_disks/hercules1_mq53_centos.120.z
(inode
#6802449,
mod time Tue Dec 13 10:27:44 2005)
<The bad blocks inode> (inode #1, mod time Tue Dec 13
14:59:08
2005)
Clone multiply-claimed blocks<y>? yes
Error reading block 7032777 (Attempt to read block from filesystem
resulted in
hort read). Ignore error<y>? yes
Force rewrite<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (22503, counted=22501).
Fix<y>? yes
Free blocks count wrong for group #214 (7767, counted=7769).
Fix<y>? yes
/sdb: ***** FILE SYSTEM WAS MODIFIED *****
/sdb: 36/8928192 files (5.6% non-contiguous), 608398/8922091 blocks
--
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
_____
On Behalf Of Alessandro Brezzi
Sent: Monday, December 12, 2005 10:27 AM
Subject: Re: [hercules-390] CCKD errors after installing Centos 4.2
s390x
... smartmontool use the SMART protocol of almost all the modern disk;
the
SATA drives are not currently supported.
To examine and repair the ext2/3 fs refer to chkfs (man chkfs)
HTH
Alessandro
Post by Philipp Brenner
Post by Kelly F. Hickel
Greg,
Below is some of the info you asked for. When I was
trying
Post by Philipp Brenner
Post by Kelly F. Hickel
to copy the cckd file (before running cckdcdsk and fixing the errors)
I
Post by Philipp Brenner
Post by Kelly F. Hickel
got an I/O error on the file, I checked /var/log/messages, and it
looks
Post by Philipp Brenner
Post by Kelly F. Hickel
like I have real disk errors to deal with. Anyone remember how to
check
Post by Philipp Brenner
Post by Kelly F. Hickel
for bad blocks and map them out in ext3??
fsck.ext3 -cf /dev/sdb
This will check for bad blocks and run even if the fs is marked
'clean'.
Post by Philipp Brenner
Remember to unmount the device first! You might want to see how the
drive
Post by Philipp Brenner
is doing with something like http://smartmontools.sourceforge.net/
or some tool supplied by the drive's manufacturer.
HTH
Philipp
------------------------------
--
Alessandro Brezzi
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/KIlPFB/vlQLAA/TtwFAA/W4wwlB/TM
--------------------------------------------------------------------~->
Kelly F. Hickel
2005-12-13 22:17:40 UTC
Permalink
(question everything!)

The host OS is Fedora Core 4, the guest OS is CentOS 4.2 s390x, the
drive is an IBM SCSI drive.

Here's the config file....



ARCHMODE ESAME

CPUSERIAL 00686A # CPU serial number

CPUMODEL 2084 # CPU model number

MAINSIZE 384 # Main storage size in megabytes

XPNDSIZE 0 # Expanded storage size in megabytes

CNSLPORT 3270 # TCP port number to which consoles connect

NUMCPU 1 # Number of CPUs

IODELAY 800

#LOADPARM 0120.... # IPL parameter

OSTAILOR LINUX # OS tailoring

PANRATE SLOW # Panel refresh rate

HTTPPORT 8081



# .-----------------------Device number

# | .-----------------Device type

# | | .---------File name and parameters

# | | |

# V V V

#--- ---- --------------------

001F 3270

0120 3390 /hercules/DASD/centos42_disks/hercules1_mq53_centos.120.z

0400 3088 CTCI /dev/net/tun 1500 192.168.200.1 192.168.200.2
255.255.255.0

0401 3088 CTCI /dev/net/tun 1500 192.168.200.1 192.168.200.2
255.255.255.0

#0581 3480 /hercules_vol2/DASD/centos42_disks/centos.tdf
--
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh-zEt/***@public.gmane.org

_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org]
On Behalf Of Gregg C Levine
Sent: Tuesday, December 13, 2005 4:14 PM
To: hercules-390-***@public.gmane.org
Subject: RE: [hercules-390] CCKD errors after installing Centos 4.2
s390x



Hello from Gregg C Levine
Kelly, obviously you know what you are doing. I'm not questioning
that. However, given the fluid nature of the files that Hercules
creates, I am questioning the ability of your host OS to manage the
files, and the disk drive. First off all which distribution is this?
And second of all, who makes your disk drive? And third can you repost
your Hercules configuration file, and of course which OS you are
running with Hercules.
--
Gregg C Levine hansolofalcon-XfrvlLN1Pqtfpb/***@public.gmane.org
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi
-----Original Message-----
On Behalf Of Kelly F. Hickel
Sent: Tuesday, December 13, 2005 4:15 PM
Subject: RE: [hercules-390] CCKD errors after installing Centos 4.2
s390x
FYI, I don't know now if this disk is bad, or if something odd is
going
on with the file structures (although I suspect the former). I've
fsck
-ck'd the drive twice now, and I keep seeming to end up with a block
owned by multiple files. I'm going to repair the cckd file and copy
it
to another drive, then remove the questionable drive, but I wanted
to
post the output of the fsck pass here, in case something "more
subtle"
is going on.....
e2fsck 1.38 (30-Jun-2005)
Checking for bad blocks (read-only test): done
091
Pass 1: Checking inodes, blocks, and sizes
Running additional passes to resolve blocks claimed by more than one
inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 6802449: 7032768 7032777
Pass 1C: Scanning directories for inodes with multiply-claimed
blocks.
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)
File /hercules/DASD/centos42_disks/hercules1_mq53_centos.120.z
(inode
#6802449,
mod time Tue Dec 13 10:27:44 2005)
<The bad blocks inode> (inode #1, mod time Tue Dec 13
14:59:08
2005)
Clone multiply-claimed blocks<y>? yes
Error reading block 7032777 (Attempt to read block from filesystem
resulted in
hort read). Ignore error<y>? yes
Force rewrite<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (22503, counted=22501).
Fix<y>? yes
Free blocks count wrong for group #214 (7767, counted=7769).
Fix<y>? yes
/sdb: ***** FILE SYSTEM WAS MODIFIED *****
/sdb: 36/8928192 files (5.6% non-contiguous), 608398/8922091 blocks
--
Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
_____
On Behalf Of Alessandro Brezzi
Sent: Monday, December 12, 2005 10:27 AM
Subject: Re: [hercules-390] CCKD errors after installing Centos 4.2
s390x
... smartmontool use the SMART protocol of almost all the modern
disk;
the
SATA drives are not currently supported.
To examine and repair the ext2/3 fs refer to chkfs (man chkfs)
HTH
Alessandro
Post by Philipp Brenner
Post by Kelly F. Hickel
Greg,
Below is some of the info you asked for. When I was
trying
Post by Philipp Brenner
Post by Kelly F. Hickel
to copy the cckd file (before running cckdcdsk and fixing the
errors)
I
Post by Philipp Brenner
Post by Kelly F. Hickel
got an I/O error on the file, I checked /var/log/messages, and it
looks
Post by Philipp Brenner
Post by Kelly F. Hickel
like I have real disk errors to deal with. Anyone remember how
to
check
Post by Philipp Brenner
Post by Kelly F. Hickel
for bad blocks and map them out in ext3??
fsck.ext3 -cf /dev/sdb
This will check for bad blocks and run even if the fs is marked
'clean'.
Post by Philipp Brenner
Remember to unmount the device first! You might want to see how
the
drive
Post by Philipp Brenner
is doing with something like http://smartmontools.sourceforge.net/
or some tool supplied by the drive's manufacturer.
HTH
Philipp
------------------------------
--
Alessandro Brezzi
Loading...