On 11/28/06, Elizabeth Schwartz <[EMAIL PROTECTED]> wrote:
Well, I fixed the HW but I had one bad file, and the problem was that ZFS was saying "delete the pool and restore from tape" when, it turns out, the answer is just find the file with the bad inode, delete it, clear the device and scrub. Maybe more of a documentation problme, but it sure is disconcerting to have a file system threatening to give up the game over one bad file (and the real irony: it was a file in someone's TRASH!)
The ZFS documentation was assuming you wanted to recover the data, not abandon it. Which, realistically, isn't always what people want; when you know a small number of files are trashed, it's often easier to delete those files and either just go on, or restore only those files, compared to a full restore. So yeah, perhaps the documentation could be more helpful in that situation.
Anyway I'm back in business without a restore (and with a rebuilt RAID) but yeesh, it sure took a lot of escalating to get to the point where someone knew to tell me to do a find -inum.
Ah, if people here had realized that's what you needed to know, many of us could have told you I'm sure. I, at least, hadn't realized that was one of the problem points. (Probably too focused on the ZFS content to think about the general issues enough!) Very glad you're back in service, anyway! -- David Dyer-Bennet, <mailto:[EMAIL PROTECTED]>, <http://www.dd-b.net/dd-b/> RKBA: <http://www.dd-b.net/carry/> Pics: <http://www.dd-b.net/dd-b/SnapshotAlbum/> Dragaera/Steven Brust: <http://dragaera.info/> _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
