| 1 |
On 5/31/07, Jules Colding <colding@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Wed, 2007-05-30 at 08:24 -0400, Randy Barlow wrote: |
| 4 |
> > Jules Colding wrote: |
| 5 |
> > > May 30 10:29:40 omc-2 [10822.156355] sd 0:4:1:0: SCSI error: return |
| 6 |
> code = 0x00040001 |
| 7 |
> > > May 30 10:29:40 omc-2 [10822.156423] end_request: I/O error, dev sdb, |
| 8 |
> sector 97564151 |
| 9 |
> > > May 30 10:29:46 omc-2 [10827.996196] I/O error in filesystem ("sdb1") |
| 10 |
> meta-data dev sdb1 block 0x88b5ac3 ("xlog_iodone") error 5 buf count |
| 11 |
> 11776 |
| 12 |
> > > May 30 10:29:46 omc-2 [10827.996210] xfs_force_shutdown(sdb1,0x2) |
| 13 |
> called from line 960 of file fs/xfs/xfs_log.c. Return address = |
| 14 |
> 0xffffffff80398b06 |
| 15 |
> > > May 30 10:29:46 omc-2 [10827.996299] Filesystem "sdb1": Log I/O Error |
| 16 |
> Detected. Shutting down filesystem: sdb1 |
| 17 |
> > > May 30 10:29:46 omc-2 [10827.996305] Please umount the filesystem, and |
| 18 |
> rectify the problem(s) |
| 19 |
> > > May 30 10:29:46 omc-2 [10827.996983] sd 0:4:1:0: SCSI error: return |
| 20 |
> code = 0x00040001 |
| 21 |
> > > May 30 10:29:46 omc-2 [10827.996986] end_request: I/O error, dev sdb, |
| 22 |
> sector 63 |
| 23 |
> > |
| 24 |
> > Those to me look like you are having hardware issues... |
| 25 |
> |
| 26 |
> My guess too, but I'm confused by the fact that these problems continue |
| 27 |
> even though I've put the only disk reported to have errors offline. Can |
| 28 |
> an offline disk provoke errors in the remaining array? |
| 29 |
> |
| 30 |
> Thanks, |
| 31 |
> jules |
| 32 |
> |
| 33 |
> |
| 34 |
> -- |
| 35 |
> gentoo-user@g.o mailing list |
| 36 |
> |
| 37 |
> |
| 38 |
I've had those problems, and they're a real PITA. In my case i had to |
| 39 |
re-arrange my cables 15 umpteen hundred times before they would position so |
| 40 |
I didn't get any loss of contact, and turn of athcool . ( yes, athcool, if |
| 41 |
you have it, could be your problem, i didn't believe it at first myself ) |
| 42 |
|
| 43 |
A drive doesn't have to be even mounted for those errors to show up, but it |
| 44 |
sure helps. My recommendation is if you have a disk which is frequently |
| 45 |
dropping out on you like that, you switch to JFS, XFS really doesn't play |
| 46 |
nice if it thinks the drive is plugged in twice ....., and JFS has |
| 47 |
impressive recovery ability. |
| 48 |
|
| 49 |
|
| 50 |
-- |
| 51 |
Kent |
| 52 |
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| |
| 53 |
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}' |
Archives