Eric Schrock wrote:
Well the fact that it's a level 2 indirect block indicates why it can't simply be removed. We don't know what data it refers to, so we can't free the associated blocks. The panic on move is quite interesting - after BFU give it another shot and file a bug if it still happens.
I'm still seeing the panic (build 42) when trying to 'mv' the file with corrupt indirect blocks. The problem looks like 6424466 and 6440780, the panic string is "data after EOF". Email me offline if you would like to collect the core from my system.
- Eric _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
