Date: Wed, 13 Aug 2008 09:47:41 -0700 (PDT) From: Nate Eldredge <neldredge@math.ucsd.edu> To: Kostik Belousov <kostikbel@gmail.com> Cc: Nate Eldredge <neldredge@math.ucsd.edu>, Alexander Leidinger <Alexander@leidinger.net>, freebsd-hackers@freebsd.org Subject: Re: Debugging reboot with Linux emulation Message-ID: <Pine.GSO.4.64.0808130937300.11980@zeno.ucsd.edu> In-Reply-To: <20080813141059.GH1803@deviant.kiev.zoral.com.ua> References: <Pine.GSO.4.64.0808122344020.11980@zeno.ucsd.edu> <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> <20080813115413.GF1803@deviant.kiev.zoral.com.ua> <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> <20080813141059.GH1803@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Aug 2008, Kostik Belousov wrote: > Then, the issue of mixing our reboot(2)/linux fcntl(2) is irrelevant. > The original reporter said that system "just rebooted", and I believe > that filesystems where not synced and not unmounted properly. Our > reboot(2) does not have flag combination that could cause such > behaviour, I think. You are right, file systems were not unmounted, and I doubt that they were synced either. They had to be fscked when the system came back up. > Also, I doubt that the program being run is statically linked or > run by root. Confirmation ? I did not run it as root. Sorry, I should have said that before. It is a little hard to trace their maze of shell scripts to figure out which binary was being run, but if I am looking at the right one, it is dynamically linked and branded SVR4. I will make sure later today. > Overall, this looks like a nasty bug, hopefully in the linuxolator. Indeed. -- Nate Eldredge neldredge@math.ucsd.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0808130937300.11980>