HI All,
I was having a slight error with some ZFS metadata corruption on a
filesystem (thankfully, one that has no useful data on it), and in an
attempt to clear the pool of the error, I attempted to import it with force:
03:47 PM dulles[4] ~ # zpool import -fF skillet_b
This, however, returned the following error:
cannot iterate filesystems: I/O error
Pool skillet_b returned to its state as of Wed Dec 31 19:00:00 1969.
cannot iterate filesystems: I/O error
The 'cannot iterate' lines are what I got when I tried to do anything with
the affected filesystem that had the metadata error:
07:44 PM dulles[1] ~ # zpool status -v skillet_b
pool: skillet_b
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
skillet_b ONLINE 0 0 14
raidz1-0 ONLINE 0 0 56
c1t8d0 ONLINE 0 0 0
c1t9d0 ONLINE 0 0 0
c1t10d0 ONLINE 0 0 0
c1t11d0 ONLINE 0 0 0
c1t12d0 ONLINE 0 0 0
c1t13d0 ONLINE 0 0 0
errors: Permanent errors have been detected in the following files:
skillet_b/haafs2/zone:<0x0>
Perhaps there's some amusing little coding error in ZFS causing the 1969
pre-unix time date? Just something amusing I saw today.
--
Stephen Repetski
BS Applied Networking and Systems Administration, 2013
Rochester Institute of Technology, Thomas Jefferson HS S&T
skr3...@rit.edu | http://srepetsk.net
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
