on 02/04/2014 19:48 R. Tyler Croy said the following: > On Wed, 02 Apr 2014 09:58:37 +0300 > Andriy Gapon <a...@freebsd.org> wrote: > >> on 01/04/2014 16:57 R. Tyler Croy said the following: >>> On Tue, 01 Apr 2014 09:41:45 +0300 >>> Andriy Gapon <a...@freebsd.org> wrote: >>> >>>> on 01/04/2014 02:22 R. Tyler Croy said the following: >> ... >>>>> Also in addition to the photo from before of the panic, here's >>>>> another reproduction photo: >>>>> <https://www.flickr.com/photos/agentdero/13472248423/> >>>> >>>> Are you or have you even been running with any ZFS-related kernel >>>> patches? >>> >>> >>> Negative, I've never run any specific ZFS patches on this machine >>> (or any machine for that matter!) >>> >>> One other unique clue might be that I'm running with an encrypted >>> zpool, other than that, nothing fancy here. >> >> Your problem looks like a corruption of on-disk data. >> I can not say how it came to be or how to fix it now. >> > > > This is concerning to me, I'm using an intel 128GB SSD which is less > than 6 months old. If there is an actual disk-level corruption, > shouldn't that manifest itself as a zpool error?
I am afraid that this is a different kind of corruption. Either a bug (possibly old, already fixes) in ZFS or a corruption that happened in RAM before a buffer was sent to a disk. -- Andriy Gapon _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
