On 09-10-16 00:00:16, charles zeitler wrote:
thanks for the help...
On Thu, Oct 15, 2009 at 9:14 PM, Tony Nelson
> I don't know of anything specifically intended to find the
damaged
> files. e2fsck will map out bad blocks, but doesn't (AFAIK) tell
> one which files are damaged. I think tar can be used to find such,
> files but I'm not sure. As you know of one file that has a
> problem, I suggest trying this command on the directory which
> contains that file:
>
> # tar -cf - --ignore-failed-read /path/to/bad/file's/dir \
> /dev/null
>
> Possibly -v will also be needed. In that case, the full scan
should
> probably write the messages to a file:
>
> # tar -cvf - --ignore-failed-read --one-file-system / \
> >/dev/null 2>/some/other/volume/tarfiles.txt
>
> I don't happen to have any bad blocks to try this on.
tar seems not to read files that are headed to /dev/null (?)
Lovely. Well then:
# tar -cvf - --ignore-failed-read --one-file-system / \
2>/some/other/volume/tarfiles.txt | cat >/dev/null
trying cat instead. since i am working with hundreds of
gigabytes... it could take awhile.
Good luck.
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <
http://www.georgeanelson.com/>