Date: Thu, 3 Jun 2010 19:09:54 -0700 (PDT) From: John Doe <lex859@ymail.com> To: Jeff Roberson <jroberson@jroberson.net> Cc: current@freebsd.org Subject: Re: Panic on current when enabling SUJ Message-ID: <441314.75942.qm@web114305.mail.gq1.yahoo.com> In-Reply-To: <alpine.BSF.2.00.1006031319290.1483@desktop> References: <703885.42640.qm@web114309.mail.gq1.yahoo.com> <alpine.BSF.2.00.1006031319290.1483@desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
________________________________
From: Jeff Roberson <jroberson@jroberson.net>
To: John Doe <lex859@ymail.com>
Cc: current@freebsd.org
Sent: Thu, June 3, 2010 7:19:59 PM
Subject: Re: Panic on current when enabling SUJ
On Thu, 3 Jun 2010, John Doe wrote:
> Boot into single user-mode
>
> # tunefs -j enable /
> # tunefs -j enable /usr
> # tunefs -j enable /tmp
> # tunefs -j enable /var
> # reboot
>
> The machine then panics.
>
> Looks like the machine is trying to write to a read-only filesystem.
Can you please give me information on the panic? What was the state of
the filesystems upon reboot? Does dumpfs show suj enabled?
I wasn't able to get a dump.
The filesystem did not have SUJ enable before booting into single user more.
It appears SUJ was correctly enable by tunefs while in single user-mode.
The problem appears to be isolated to enabling SUJ for the first time while in single user-mode, then rebooting.
Let me know if you need anymore information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441314.75942.qm>