Date: Wed, 15 Jul 2015 10:16:40 -0600 From: Warner Losh <imp@bsdimp.com> To: Mattia Rossi <mattia.rossi.mailinglists@gmail.com> Cc: Ronald Klop <ronald-lists@klop.ws>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: executable gone after fsck - Fwd: Cron <root@sheeva> newsyslog Message-ID: <4CF1F0A4-9486-46DC-AF73-3E98DAB284DD@bsdimp.com> In-Reply-To: <55A652D6.7010401@gmail.com> References: <20150709200019.E7710D975C@sheeva.klop.ws> <op.x1js2ee0kndu52@ronaldradial.radialsg.local> <55A652D6.7010401@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_7DA8361D-0EEA-47D6-B7C7-83E2A840336B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jul 15, 2015, at 6:32 AM, Mattia Rossi = <mattia.rossi.mailinglists@gmail.com> wrote: >=20 > Hi Ronald, >=20 > 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=E2=80=A6 It was broken on atmel until I turned of unmapped I/O. then it was rock = solid on atmel, at least as rock solid as it is on other platforms. Ian = told me his dream plug was also broken in a similar way, but I can=E2=80=99= t recall if he tested it for me there. I crashed my Atmel AT91SAM9G20 = system about 100 times chasing unrelated bugs after this change. Before = I turned off unmapped I/O it was always a disaster (never once did fsck = do something useful on a dirty fs). Afterwards every time i was paying = attention, it just worked (and when I wasn=E2=80=99t paying attention, = it didn=E2=80=99t have the mandatory trip into single user mode). fsck definitely does unaligned direct I/O, which is what I think is = broken with unmapped I/O. I=E2=80=99m confident that I=E2=80=99ve fixed = this. The kernel Ron is using should be plenty new enough since I fixed this = back in march, iirc. Warner > 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 = ;-) >=20 > Cheers, >=20 > Mat >=20 > Am 10.07.2015 um 10:12 schrieb Ronald Klop: >> Hi, >>=20 >> 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@sjakie.klop.ws:/usr/obj-arm/arm.arm/usr/src-arm/sys/SHEEVAPLUG arm >>=20 >> 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=3D283931 >>=20 >> NB: In the case below bzip2 does not exist anymore. Which is not = something _just_ written to disk. >>=20 >> Unfortunately I don't have more information about the crash. >>=20 >> Ronald. >>=20 >>=20 >> ------- Forwarded message ------- >> From: "Cron Daemon" <root@sheeva.klop.ws> >> To: root@klop.ws >> Cc: >> Subject: Cron <root@sheeva> newsyslog >> Date: Thu, 09 Jul 2015 22:00:10 +0200 >>=20 >> 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@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --Apple-Mail=_7DA8361D-0EEA-47D6-B7C7-83E2A840336B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVpodpAAoJEGwc0Sh9sBEAogwQAKpvDlDhHAlTZeaIIKMU0CGt rhO4ANHw88qsWoE3xR9M5VlLO7nMRTlaz0xRQXWfm2z9j6hQcSKGO1K9AgQZhcuq mHnNauEo241Fke20GzEanKJwtkPttmIqE94Y1KtNO0OD2SvxAHkQ2vW1o6LJ0lpG a2JX50KT1t1kLrnTJ/w1Skb8bfpx1gxxpbyFtLYrIRCrHDfpLAWxfOniVsC6ajrg gNH3M9qzNfnDgChzdYbWGmDN9uH5QbVZZjvXZjQPjeqXVdgay6hDewIi9IwMjD/q wbXak+RhcJvzy4J0IuYy5jcHyYgXvtVyaZMk0Z0BNCmQ/msdad8uZjuFGQSnBiXC ydYfJ9hX4udlpHtjTd75hjR4eEpt5jn54537ULW9f8rhDFQrMm6iTiUhGy+MkdhA T2+BQSYWfQjQKSPu1GWrnPNCSosojqlWS1gHvR7nhT+TLa/nvnLIN3nQ4ZQyEiCG WPUMUfPuO7QfqBDBjAMiUBa2r9kH0BKhhdneo5JT3BAH1JfU23zivZClvXvkbSI3 QyT3XsoCSDKkotYhjCAKb27JF7sEzSV/LG4sw9+ymA64IW9qiZmSyWU6/xacI1Vx sTsChrxCZwXDg7FKPH/SV84oi5rGDk+1UFjbK2i9ed5+nECkR03ZrvUG05JqM0FU vX5osi0lXqxLJJupMjNM =Z/jR -----END PGP SIGNATURE----- --Apple-Mail=_7DA8361D-0EEA-47D6-B7C7-83E2A840336B--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CF1F0A4-9486-46DC-AF73-3E98DAB284DD>