Bayard, >> You wouldn't happen to have preserved output that could be used to determine >> if/where there's a bug?
Whoops - in fact, this was the gist of my email to the lists, really; that someone might be interested in diagnostic information. The short answer: After not hearing a lot of interest in that - apart from your own response - and now having deleted the datasets in question: I hope so! I certainly do have the last crash dump - intact, as the machine hasn't crashed since...(...sound of knocking on wood) Pls tell me what debug info I can provide. The fix itself turned out to be quite easy, as you've indicated. My first concern was in being a good 'Listizen' - identifying/reporting on a bug, if one exists. Thanks again for your help, Lou Picciano ----- Original Message ----- From: "Bayard G. Bell" <buffer.g.overf...@gmail.com> To: z...@lists.illumos.org Cc: firstname.lastname@example.org Sent: Tuesday, January 31, 2012 7:01:53 AM Subject: Re: [zfs] Oddly-persistent file error on ZFS root pool On Mon, 2012-01-30 at 01:50 +0000, Lou Picciano wrote: > Bayard, > > Indeed, you did answer it - and thanks for getting back to me - your > suggestion was spot ON! > > However, the simple zpool clear/scrub cycle wouldn't work in our case - at > least initially. In fact, after multiple 'rinse/repeats', the offending file > - or its hex representation - would reappear. In fact, the CHSKUM errors > would often mount... Logically, this seems to make some sense; that zfs would > attempt to reconstitute the damaged file with each scrub...(?) As the truth is somewhere in between, I'll insert my comment accordingly. You should only see the errors continue if there's a dataset with a reference to the version of the file that creates those errors. I've seen this before: until all of the datasets are deleted, the errors will continue to be diagnosed, sometimes presented without databaset names, which might be considered a bug (it seems wrong that you don't get a dataset name for clones). You wouldn't happen to have preserved output that could be used to determine if/where there's a bug? > In any case, after gathering the nerve to start deleting old snapshots - > including the one with the offending file - the clear/scrub process worked a > charm. Many thanks again! > > Lou Picciano > > ----- Original Message ----- > From: "Bayard G. Bell" <buffer.g.overf...@gmail.com> > To: z...@lists.illumos.org > Cc: email@example.com > Sent: Sunday, January 29, 2012 3:22:39 PM > Subject: Re: [zfs] Oddly-persistent file error on ZFS root pool > > Lou, > > Tried to answer this when you asked on IRC. Try a zpool clear and scrub > again to see if the errors persist. > > Cheers, > Bayard ------------------------------------------- illumos-zfs Archives: https://www.listbox.com/member/archive/182191/=now RSS Feed: https://www.listbox.com/member/archive/rss/182191/22086598-09fa5b64 Modify Your Subscription: https://www.listbox.com/member/?member_id=22086598&id_secret=22086598-86c7d407 Powered by Listbox: http://www.listbox.com
_______________________________________________ zfs-discuss mailing list firstname.lastname@example.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss