executable gone after fsck - Fwd: Cron <root at sheeva> newsyslog

[Mattia Rossi]

Hi Ronald,

I might have missed some information on the list about the topic, and 
unless the unmapped i/o was the cause, fsck is pretty much broken at 
least on the Dreamplug.. and I would suspect also on the Sheevaplug. Wih 
the first few fsck you do you will lose random files, later on you won't 
be able to boot anymore, as fsck won't be able to fix fs errors anymore...

I'm currently using the fix suggested by Ian at the time: set the dump 
and pass values of your root fs in fstab to 0 0 and live with a dirty fs 
after a crash. Unless the system is crashing often, you'll be quite fine ;-)

Cheers,

Mat

Am 10.07.2015 um 10:12 schrieb Ronald Klop:
> Hi,
>
> I used fsck after a panic on my sheevaplug.
> FreeBSD sheeva.klop.ws 11.0-CURRENT FreeBSD 11.0-CURRENT #8 r284499M: 
> Wed Jun 17 12:54:02 CEST 2015 
> root at sjakie.klop.ws:/usr/obj-arm/arm.arm/usr/src-arm/sys/SHEEVAPLUG arm
>
> If I did not made a mistake somewhere I'm running with the unmapped 
> i/o turned off.
> http://www.secnetix.de/olli/FreeBSD/svnews/index.py?r=283931
>
> NB: In the case below bzip2 does not exist anymore. Which is not 
> something _just_ written to disk.
>
> Unfortunately I don't have more information about the crash.
>
> Ronald.
>
>
> ------- Forwarded message -------
> From: "Cron Daemon" <root at sheeva.klop.ws>
> To: root at klop.ws
> Cc:
> Subject: Cron <root at sheeva> newsyslog
> Date: Thu, 09 Jul 2015 22:00:10 +0200
>
> newsyslog: execl(`/usr/bin/bzip2 -f /var/log/console.log.0'): No such 
> file
> or directory
> newsyslog: `bzip2 -f /var/log/console.log.0' terminated with a non-zero
> status (1)
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"