freebsd stable - Dec 2013 - FreeBSD 10.0-RC3 AMD64 UFS issues?

Hey :-)

That sed issue I reported may be related to filesystem corruption.
After fresh install and reboot I did test "pkg install" then reboot
then filesystem somehow got dirty!! I did fsck -fy and it showed lots
of problems. Now I get:

% vi
/usr/bin/vi: Exec format error. Binary file not executable.

This is really not nice for one or two reboots after fresh OS install
:-( I will retry the install and see what happens then :-)

Best regards :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

On Fri, Dec 27, 2013 at 8:56 PM, CeDeROM <cederom at tlen.pl>
wrote:
> That sed issue I reported may be related to filesystem corruption.
> After fresh install and reboot I did test "pkg install" then
reboot
> then filesystem somehow got dirty!! I did fsck -fy and it showed lots
> of problems. Now I get:
>
> % vi
> /usr/bin/vi: Exec format error. Binary file not executable.
>
> This is really not nice for one or two reboots after fresh OS install
> :-( I will retry the install and see what happens then :-)
Second full-install and things seems okay - this UFS tihng really
bothers me, maybe it is more convenient to turn-off the SU for
base/root filesystem..?

# ldd /usr/bin/sed
/usr/bin/sed:
libc.so.7 => /lib/libc.so.7 (0x800822000)
# ldd /usr/bin/vi
/usr/bin/vi:
libutil.so.9 => /lib/libutil.so.9 (0x80087c000)
libncursesw.so.8 => /lib/libncursesw.so.8 (0x800a8e000)
libc.so.7 => /lib/libc.so.7 (0x800ce3000)

Best regards! :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info