Messages in this thread | | | Date | Wed, 31 Oct 2007 09:16:09 -0700 | From | Zach Brown <> | Subject | Re: [patch 0/6][RFC] Cleanup FIBMAP |
| |
> The second use case is to look at the physical layout of blocks on disk > for a specific file, use Mark Lord's write_long patches to inject a disk > error and then read that file to make sure that we are handling disk IO > errors correctly. A bit obscure, but really quite useful.
Hmm, yeah, that's interesting.
> We have also used FIBMAP a few times to try and map an observed IO error > back to a file. Really slow and painful to do, but should work on any > file system when a better method is not supported.
We're getting off of this FIBMAP topic, but this interests me. Can we explore this a little? How did you find out about the error without having a file to associate with it? Drive scrubbing, or some such?
- z - 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/
| |