I forgot to say that yes, doing a fsck -n should be reliable. It does the same checks as doing an fsck without -n, but it does not try to repair any damage.
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of James Melin Sent: Wednesday, August 03, 2005 8:47 AM To: [email protected] Subject: Re: Forcing FSCK on all DASD at IPL Ok... fsck -n can be used as a reliable health check? The reason I am asking is this: I get : itasca:~ # fsck -n /dev/dasdc1 fsck 1.28 (31-Aug-2002) e2fsck 1.28 (31-Aug-2002) Warning! /dev/dasdc1 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/dasdc1: clean, 46722/451584 files, 657516/903036 blocks but when I look in /var/log/warn I am seeing Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: EXAMINE 24: Command Reject detected - fatal error Aug 1 10:02:08 itasca kernel: dasd(eckd): Sense data: Aug 1 10:02:08 itasca kernel: dasd(eckd):device 0202 on irq 8: I/O status report: Aug 1 10:02:08 itasca kernel: dasd(eckd):in req: 22a18000 CS: 0x40 DS: 0x0E Aug 1 10:02:08 itasca kernel: dasd(eckd):Failing CCW: 22a180b8 Aug 1 10:02:08 itasca kernel: dasd(eckd):Sense(hex) 0- 7: 80 00 00 00 22 ff ff 04 Aug 1 10:02:08 itasca kernel: dasd(eckd):Sense(hex) 8-15: 00 00 00 00 00 00 00 04 Aug 1 10:02:08 itasca kernel: dasd(eckd):Sense(hex) 16-23: 23 00 32 7e 92 69 0f 04 Aug 1 10:02:08 itasca kernel: dasd(eckd):Sense(hex) 24-31: 00 00 40 e2 00 13 97 0a Aug 1 10:02:08 itasca kernel: dasd(eckd):24 Byte: 0 MSG 4, no MSGb to SYSOP Aug 1 10:02:08 itasca kernel: Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: (EXAMINE) ERP chain report for req: 22a18000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18000: c5c3d2c4 00000000 22a18000 22a18000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18010: 0177a000 0233a980 22a180a8 03000100 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18020: 00000000 ff000000 22a18078 08493400 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18030: 00000000 00000000 0000011e 1a300000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18040: bd657cca c6b67188 bd657cca c6b68568 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18050: 00000000 00000000 00000000 00000000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18060: 00000083 00000030 00000000 00000000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18070: 01694100 00000000 40cc0000 00000000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: DATA area is at: 22a18078 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18078: 40cc0000 00000000 1397000a 13970006 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18088: 00000000 00000000 00000000 00000000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18098: 06800080 1397000a 1397000a 0bb81000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: Start of channel program: Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a180a8: 63400010 22a18078 47400010 22a18098 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a180b8: 86401000 0f76b000 86401000 4585b000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a180c8: 86401000 3906c000 86401000 0c5fb000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a180d8: 86401000 50a70000 86401000 07e8f000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a180e8: 86401000 430c9000 86401000 11cfa000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a180f8: 86401000 415f4000 86401000 14db0000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18108: 86401000 23f43000 86401000 24a3b000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18118: 86401000 24a26000 86401000 25719000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18128: 86401000 13ea3000 86401000 22e67000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: 22a18138: 86401000 24679000 86401000 29779000 Aug 1 10:02:08 itasca kernel: dasd_erp(3990): /dev/dasdc ( 94: 8),[EMAIL PROTECTED]: End of channel program: I also get this for /dev/dasdd and that also reports clean for fsck -n So I am concerned..... "Fargusson.Alan" <[EMAIL PROTECTED] tb.ca.gov> To Sent by: Linux on [email protected] 390 Port cc <[EMAIL PROTECTED] IST.EDU> Subject Re: Forcing FSCK on all DASD at IPL 08/03/2005 10:23 AM Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> Most versions of fsck support the -n option, which causes them to use read-only mode. This can be done without unmounting the filesystem. You can verify the filesystem this way, but you can't repair any damage without unmounting them. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of James Melin Sent: Wednesday, August 03, 2005 7:45 AM To: [email protected] Subject: Forcing FSCK on all DASD at IPL Hey gang. Seeing some error messages about my file system that I'm concerned about. Is it possible to force an FSCK on all file systems defined to a Linux guest at IPL? I am seeing some errors in /opt/warn that are concerning me on a couple of file systems though the systems appear to be running at the moment. Typically it's been doing it after x many mounts or after x many days without being checked. Also, is it possible to run an integrity check of a file system while it is mounted with some other utility? FSCK of course warns about possibly frelling your filesystem to the center of the earth if you use it on a mounted file system. Just wondering what FS checker might be available that I don't have to schedule downtime with customers in order to use it Any ideas/thoughts will be greatly appreciated. -J ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
