Hey,

Using the steps on
http://www.opensolaris.org/jive/thread.jspa?messageID=39450&tstart=0confirms
that it's the iso file.
Removing the file does work, I'll just download the file again and let a
scrub clean up the error message.

Steve

On 5/15/07, eric kustarz <[EMAIL PROTECTED]> wrote:


On May 15, 2007, at 9:37 AM, XIU wrote:

> Hey,
>
> I'm currently running on Nexenta alpha 6 and I have some corrupted
> data in a pool.
>
> The output from sudo zpool status -v data is:
>
>   pool: data
>  state: ONLINE
> status: One or more devices has experienced an error resulting in data
>     corruption.  Applications may be affected.
> action: Restore the file in question if possible.  Otherwise
> restore the
>     entire pool from backup.
>    see: http://www.sun.com/msg/ZFS-8000-8A
>  scrub: none requested
> config:
>
>     NAME        STATE     READ WRITE CKSUM
>     data        ONLINE       0     0    10
>       c2d0      ONLINE       0     0     0
>       c1d0      ONLINE       0     0     0
>       c3d0      ONLINE       0     0     0
>       c4d0      ONLINE       0     0     0
>       c0d1      ONLINE       0     0    10
>
> errors: The following persistent errors have been detected:
>
>           DATASET  OBJECT  RANGE
>           1c8      10a5    lvl=0 blkid=1919
>
> When accessing the file I'll get an I/O error, is it possible to
> clear the error and overwrite the corrupted data with all zeroes? I
> don't know how much data that is corrupted but it's from the Ubuntu
> 7.04 iso which is downloaded with a torrent and my client hangs at
> 34% in checking it. If I could just clear the corrupted data the
> client would pick it up and just redownload that part.
>
> Kind regards,
> Steve

hey steve,

So you already figured out which file was corrupted by translating
the object number to an actual filepath?  and its the Ubuntu 7.04 iso
file?

Can you just remove the file or does that error out?

If you can upgrade your bits, then 'zpool status -v' will be more
informative:
http://blogs.sun.com/erickustarz/entry/damaged_files_and_zpool_status

From your output, just one block is corrupted (blkid 1919).

eric


_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to