Messages in this thread | | | Date | Mon, 24 Nov 2003 16:34:43 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | Re: data from kernel.bkbits.net |
| |
On Mon, 24 Nov 2003, Theodore Ts'o wrote:
> On Mon, Nov 24, 2003 at 03:05:24PM -0500, Richard B. Johnson wrote: > > Attempt to copy the raw drive to /dev/null. If that works, the > > drive is likely okay, but the fs got fsucked up by software. You > > might be able to mount the drive on a 2.4.22 machine if you have a > > spare. Then you might be able to selectively copy important stuff > > to another drive, after which you can make a new file-system as > > a "repair". > > The error messages Larry reported were obviously reported by the > hardware, and were **not** filesystem errors. > > - Ted
Yes but an attempt to read beyond the limits of the physical drive will provide you with a lot of **interesting** hardware errors. This happens if the file-system gets corrupt.
And I'm not implying that the software screwed up either. The software doesn't know if an "extra" bit was set during a write to the drive. These things happen asd a result of bad RAM, bad DMA, and other hardware-corrupting things....
So, the first check is to see if the drive can be read without any reference to its contents. Since Read/Write is usually the software implimentation detail of a direction bit, if you can read, you can usually write.
Cheers, Dick Johnson Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips). Note 96.31% of all statistics are fiction.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |