From owner-freebsd-arm@freebsd.org Wed Jul 22 10:08:45 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49D159A69E3 for ; Wed, 22 Jul 2015 10:08:45 +0000 (UTC) (envelope-from mattia.rossi.mailinglists@gmail.com) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D25C9115B for ; Wed, 22 Jul 2015 10:08:44 +0000 (UTC) (envelope-from mattia.rossi.mailinglists@gmail.com) Received: by wicgb10 with SMTP id gb10so90803435wic.1 for ; Wed, 22 Jul 2015 03:08:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=brMEL+FnJxSmJH2gFG2N6EWlQ9tsoWFwE+ZYVTi5ReY=; b=G2HeBfZGO3Lwl29thB/NnW4q1gFl3yJV72V6xGcDBp2VzwP5JSAGJ5lZM7JKVB9vH7 dEwq1Zmr4S35WVNXSPh7mIYKaC3HlfDovMR1vX8T9v4OZx1ORoqJ55zkrHtAmvv9zRu0 bkFPk8l8AOa/C7/9wGhefjIELYsxl2alNBnLVQolSUJ/bcHRphaYP6otUBcjL9kJHEXh R+VrtgAwtx6pRGie+9zeZxZYwp8mQeHhOzB3Zl99a/9NIZJn79O5cj5FSTugwLpj2lgH lgslVenBPofjgT00aGKVFzP6xloPRwka7D14tZ98m+Gt2PMVyEGL/20fvS7yDRXx9fex 4cPg== X-Received: by 10.194.185.180 with SMTP id fd20mr3371634wjc.16.1437559723287; Wed, 22 Jul 2015 03:08:43 -0700 (PDT) Received: from [192.168.10.177] ([88.208.109.142]) by smtp.googlemail.com with ESMTPSA id gb16sm2599926wic.5.2015.07.22.03.08.41 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Jul 2015 03:08:42 -0700 (PDT) Message-ID: <55AF6BA5.4070400@gmail.com> Date: Wed, 22 Jul 2015 12:08:37 +0200 From: Mattia Rossi User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Warner Losh CC: Ronald Klop , "freebsd-arm@freebsd.org" Subject: Re: executable gone after fsck - Fwd: Cron newsyslog References: <20150709200019.E7710D975C@sheeva.klop.ws> <55A652D6.7010401@gmail.com> <4CF1F0A4-9486-46DC-AF73-3E98DAB284DD@bsdimp.com> In-Reply-To: <4CF1F0A4-9486-46DC-AF73-3E98DAB284DD@bsdimp.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 10:08:45 -0000 Hi Warner, thanks for fixing this. I can confirm that fsck works on the Dreamplug. Cheers, Mat Am 15.07.2015 um 18:16 schrieb Warner Losh: >> On Jul 15, 2015, at 6:32 AM, Mattia Rossi wrote: >> >> 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… > 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’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’t paying attention, it didn’t 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’m confident that I’ve 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 ;-) >> >> 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@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" >>> To: root@klop.ws >>> Cc: >>> Subject: Cron 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@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> _______________________________________________ >> 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"