From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 12:20:41 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 831099E1 for ; Thu, 19 Feb 2015 12:20:41 +0000 (UTC) Received: from mail-yh0-f51.google.com (mail-yh0-f51.google.com [209.85.213.51]) (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 45375CBC for ; Thu, 19 Feb 2015 12:20:40 +0000 (UTC) Received: by yhab6 with SMTP id b6so4411028yha.10 for ; Thu, 19 Feb 2015 04:20:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MWdCOX2wY4z1+YQ9ffUzNOQGWofGS+43VRKvkFs9pQQ=; b=Aa1GLpMjApdfB/X4d3Wjdap39RQjZBMwEF1dY0GqiKBZZzZFHZzlp5LDZkQmiDf9+G /wK8ICp/w4H1MetPR8CZnjIHZBv7m/IHMDXF2cCsV0GEc1OXM7580a3tIsg3W7CH4O7b XFFXIwFmklgx5FKgwhCFa1JY5AFvZER+BcL3p4jQC/Q9hU/Tq7U+Aimr7/NlUlZoqTWO JyGpS9GkVWl/lb3Rr317WkOzBGcM//S3r4dbfii9gBH2TnWgvcDeuIut4IL05IY+5l1f a3jKJTaLwkNMzJd5a/en8BHdHcHQoSfNvtHl/xcESKDKPfpKiLRV7LwGEuC/hdJiIcaG B5Ng== MIME-Version: 1.0 X-Received: by 10.236.41.105 with SMTP id g69mr2401720yhb.55.1424347974834; Thu, 19 Feb 2015 04:12:54 -0800 (PST) Received: by 10.170.188.1 with HTTP; Thu, 19 Feb 2015 04:12:54 -0800 (PST) In-Reply-To: <20150218191345.GA31812@coyotlan.Tlalpan> References: <20150218191345.GA31812@coyotlan.Tlalpan> Date: Thu, 19 Feb 2015 12:12:54 +0000 Message-ID: Subject: Re: ZFS root set to readonly=on temporary at boot From: krad To: =?UTF-8?B?WMSrY8Oy?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 12:20:41 -0000 Check your bootfs and the / file system actually match up. Its quite easy to get odd things happening if you have the bootfs set to a filesystem that then has an fstab which then tells / is on another fs. Also check the loader.conf on the bootfs. In my experiance its safer to have clean fstabs, and nothing in the loader.conf (in relation to this) and just relay on the bootfs pool property On 18 February 2015 at 19:13, X=C4=ABc=C3=B2 wrote: > Dear freebsd-fs, > > As I am trying to install a new small server with a most partitions on > ZFS, I am running into some little read-only troubles. At boot the root > is always set to read-only. The rest of the system is fine though: > > # zfs get all | grep readonly > zroot readonly on temporar= y > zroot/tmp readonly off inherite= d > from zroot > zroot/usr readonly off inherite= d > from zroot > [=E2=80=A6] > > I cannot seem to understand what may cause this issue. The system is a > typical manual [1] installation (used to work fine), on an empty system. > > Note that I can reset the root to readonly=3Doff with: > > # zfs set readonly=3Doff zroot > > but it is a pain to to it manually without understanding why. I also > cannot seem to get much info from the log messages: > > =3D=3D> /var/log/messages <=3D=3D > Feb 18 18:56:24 kernel: Root mount waiting for: usbus4 > Feb 18 18:56:24 last message repeated 2 times > Feb 18 18:56:24 kernel: uhub4: 8 ports with 8 removable, self powered > Feb 18 18:56:24 kernel: Root mount waiting for: usbus4 > Feb 18 18:56:24 kernel: ugen4.2: at usbus4 > Feb 18 18:56:24 kernel: uhub5: 9/0, rev 2.00/1.00, addr 2> on usbus4 > Feb 18 18:56:24 kernel: uhub5: 4 ports with 4 removable, self powered > Feb 18 18:56:24 kernel: Trying to mount root from zfs:zroot [rw]... > Feb 18 18:56:29 kernel: . > Feb 18 18:56:30 kernel: . > > There are a couple of mentions to this same problem in 2012 on this > mailing list [2] and on an unanswered forum message [3], but they did > not solve the issue (setting vfs.root.mountfrom.options=3Drw only changes > the log message). The machine starts its other services (such as SSH) > correctly though. > > Hope someone will have an idea. > > Best, > > X=C4=ABc=C3=B2 > > [1] > https://blog.gegeweb.org/article30/freebsd-9-2-en-full-zfs-sur-un-kimsufi= -ps-4g > [2] > https://lists.freebsd.org/pipermail/freebsd-fs/2012-February/013654.html > [3] > https://forums.freebsd.org/threads/zfs-readonly-on-temporary-on-boot.2894= 4/ > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"