Help needed! ZFS I/O error recovery?
Solon Lutz
solon at pyro.de
Wed Oct 14 16:47:39 UTC 2009
>>> >> > As I understand the values 13462283 and 13462284 were showing errors?
>>> >> > Yes, just try to import the pool and set vfs.zfs.maxtxg back to zero
>>> >> > afterwards.
>>> >> 13462283 and 13462284 were showing errors.
>>> >> vfs.zfs.maxtxg was at -1 before I changed it.
>>> > So does it work now?
>>> radium# zpool import -f temp
>>> cannot iterate filesystems: I/O error
>>> radium# ll /temp/
>>> ls: backup: Input/output error
>>> total 9
>>> drwxr-xr-x 2 root wheel 2 May 16 2007 audio
>>> drwxr-xr-x 2 root wheel 2 May 16 2007 misc
>>> drwxr-xr-x 2 root wheel 2 May 16 2007 video
>>> drwxr-xr-x 8 dhcpd dhcpd 11 Jul 8 10:36 www
>>> radium# ll /temp/audio/
>>> total 0
>>> radium# ll /temp/misc/
>>> total 0
>>> radium# zfs unmount temp
>>> cannot iterate filesystems: I/O error
>> Can you show 'zpool status'?
>> It might be worth trying to go even more in the past with maxtxg.
> sysctl vfs.zfs.maxtxg=13462260
> pool: temp
> 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
> temp ONLINE 0 0 9
> da0 ONLINE 0 0 36
> errors: Permanent errors have been detected in the following files:
> temp:<0x0>
> temp:<0x49681>
> temp:<0x499a4>
> temp:<0x495fd>
> temp/space1:<0x0>
> temp/space2:<0x0>
> temp/space3:<0x0>
> temp/space4:<0x0>
> temp/space5:<0x0>
I just tried it with more TXGs, even with a jump of -300, but it always gives
an "cannot iterate filesystems: I/O error" error if I try to import the pool.
Also because of mounting the pool, the TXg has gone up to 13445935 from
initially 13462284.
solon
More information about the freebsd-fs
mailing list