If you have a problem like this in the future, please download and
compile the latest e2fsprogs (1.23 WIP 9-Aug-2001), and use the
command "e2image -r /dev/xxx raw-image-file". This will create a raw
image file which is a sparse file containing only the filesystem
metadata. Try running fsck on that, and see if you are continuing to
get differing results between runs. If so, then you've isolated away
from it being a hardware problem. Then, if you don't mind letting me
see the directory names/hierarchy in your filesystem, bzip2 the
resulting filesystem and send it to me, along with an indication of
the size of the filesystem.
That will allow me to debug the problem at my end, without my needing
to see any of your file data, as well as making the compressed
filesystem image small enough that it should be feasible to ship it
over the net.
Many thanks,
- Ted
-
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/