| To: | Joe Kaiser <jlkaiser@xxxxxxxx> |
|---|---|
| Subject: | Re: kernel debugger and Infortrend and bad blocks |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | 24 Feb 2004 18:08:08 -0600 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1077665271.1051.21.camel@nietzsche.fnal.gov> |
| Organization: | Eric Conspiracy Secret Labs |
| References: | <1077665271.1051.21.camel@nietzsche.fnal.gov> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Details please, what did the kernel say... xfs knows nothing about bad blocks on the disk, but it does know about I/O errors. -Eric On Tue, 2004-02-24 at 17:27, Joe Kaiser wrote: > Hi, > > I have a number of Infortrends that cause XFS to go into the kernel > debugger and unmount the XFS filesystem whenever a bad block is found on > the disk. A remount and then a dismount and an xfs_repair is then > required to fix the problem. Is there anyway to avoid this? Why is XFS > even getting bad block information from the disk? > > I am using XFS1.3.1 on 2.4.20-20.9..... > > Thanks, > > Joe -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc. 651-683-3102 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: dm_write_invis() blocking problem, Dean Roehrich |
|---|---|
| Next by Date: | TAKE 904196 - add missing 2.4 bits, Nathan Scott |
| Previous by Thread: | kernel debugger and Infortrend and bad blocks, Joe Kaiser |
| Next by Thread: | Re: kernel debugger and Infortrend and bad blocks, Joe Kaiser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |