Date: Fri, 18 May 2012 10:18:47 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-current FreeBSD <freebsd-current@freebsd.org> Subject: Re: SUJ file system corruption. Message-ID: <20769DCB-D3EF-49C6-A791-E190A5CCECAE@lists.zabbadoz.net> In-Reply-To: <2103A722-43BF-4BCF-AEDE-2E0CB13DF620@kientzle.com>
index | next in thread | previous in thread | raw e-mail
On 13. May 2012, at 22:35 , Tim Kientzle wrote: > FYI: Saw a crash due to filesystem corruption when running SUJ. > > This is on a ARM AM335x system (BeagleBone) that is > still pretty experimental, so I certainly cannot rule out other > problems, but in case it means something to > someone, here's the scenario: > > Reset the board to reboot (which is routine for these > small embedded boards) and when it came back up > it went through SUJ recovery, and then a little later > the kernel panicked with this stack trace: > > rm: /var/run/dmesg.boot: Bad file descriptor > panic: ffs_write: type 0xc1e86660 0 (0,1024) Can you tell us if this was HEAD, stable/9 or 9.0-RELEASE? -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do!home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20769DCB-D3EF-49C6-A791-E190A5CCECAE>