Date: Tue, 8 Dec 2015 14:30:56 -0800 From: NGie Cooper <yaneurabeya@gmail.com> To: "Ranjan1018 ." <214748mv@gmail.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Panic at shutdown Message-ID: <B7CCCB7B-AC21-4EA8-9839-2AF12CEA1DD7@gmail.com> In-Reply-To: <CACyC=qY_dwoCeNA%2BDpN2CvOVWuX0tj6wA8zgXq2adHU0MF0FLA@mail.gmail.com> References: <CACyC=qbD7dGnwmUqCA=3aVtMu5K19BC=-HjZTX4FjKbS2stkSg@mail.gmail.com> <055E0877-533A-4378-A306-FDE511543243@gmail.com> <CACyC=qY_dwoCeNA%2BDpN2CvOVWuX0tj6wA8zgXq2adHU0MF0FLA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Dec 8, 2015, at 08:09, Ranjan1018 . <214748mv@gmail.com> wrote: =E2=80=A6 > Probably the panic is caused by some memory already freed, the hex = value of 16045693110842147038 is 0xdeadc0dedeadc0de. > To solve the panic I need some tips form someone more expert than me = in ZFS code. Good investigative work! There was something reported recently about = unaligned accesses when dealing with msdosfs+zfs+etc, but it was an odd = edgecase. Definitely file a bug and assign it to freebsd-fs@ with the findings you = have made here. Thanks :)! -NGie=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B7CCCB7B-AC21-4EA8-9839-2AF12CEA1DD7>