[zfs-discuss] Metadata corruption following PANIC (ZFS-8000-72 error id)

J. Roeleveld joost at antarean.org
Thu Feb 1 01:23:39 EST 2018


On Tuesday, January 30, 2018 11:15:46 PM CET Celmor Smith via zfs-discuss 
wrote:
> > Stop writing to the member disks ASAP
> 
> That's what I tried by using device mapper snapshot target. I made full
> clones aka "block based" of 2 of the original disks from the pool. I had
> to use the 3rd one to prepare the Backup (as said in the original eMail
> last Backup is 4 months old). `zfs import` only didn't panic at dmu.c
> when I used the original disks and not device mapper targets which
> shouldn't happen.

Are you using ZFS ontop of LVM?



> Celmor
> 
> On 01/30/2018 03:44 PM, Gregor Kopka (@zfs-discuss) via zfs-discuss wrote:
> > Am 30.01.2018 um 01:20 schrieb Celmor Smith via zfs-discuss:
> >> Open to any suggestions.
> > 
> > Stop writing to the member disks ASAP and make block based copies of
> > them to work on.
> > Or continue to not care about the data in the pool (like with the 3rd
> > drive) and prepare a full restore from backup.
> > 
> > Gregor
> > _______________________________________________
> > zfs-discuss mailing list
> > zfs-discuss at list.zfsonlinux.org
> > http://list.zfsonlinux.org/cgi-bin/mailman/listinfo/zfs-discuss
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at list.zfsonlinux.org
> http://list.zfsonlinux.org/cgi-bin/mailman/listinfo/zfs-discuss




More information about the zfs-discuss mailing list