From owner-freebsd-questions@FreeBSD.ORG Mon Sep 7 03:08:53 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2C74106566B for ; Mon, 7 Sep 2009 03:08:53 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.210.172]) by mx1.freebsd.org (Postfix) with ESMTP id 7C3EF8FC1F for ; Mon, 7 Sep 2009 03:08:53 +0000 (UTC) Received: by yxe2 with SMTP id 2so4738346yxe.3 for ; Sun, 06 Sep 2009 20:08:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=S06VSD/to5HQtTHYsOi1nr0BjF6JRtq3bD2ZrDyPSeQ=; b=MvBLmX1BzoSOg2ZyhcQ6edH1d+jV5INcKWyDpwMqDCilf9o/XH4oQjEgv/BLNi/HoY FtsJOQOwOvZETQFBQQWxFnc3QG9vQVSoMd1kMlD7zvbdxV3EbsMjKu+Kv47YOtLvqcyz JGHAHIMlzdmuIX5Eb3tZ56M+SLQ5iYaPkExCM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QCHaYE/tR4cKfbvjT1MwoDIvXq+lg/7qw36k3jm17W6Dc2HEkUCfBm9mKZqP81WIIZ hZ0lYICuHgq10WsVP+KucU8MpxB+lxeQj1i0VOMrC1DZJoTb+gXnSV0fewiQbFMVM6wC RwN6ftEcb4ZDZ4QJ05gbhaG46mbXZ7I+PhuI4= MIME-Version: 1.0 Received: by 10.150.1.18 with SMTP id 18mr21692457yba.156.1252292932533; Sun, 06 Sep 2009 20:08:52 -0700 (PDT) In-Reply-To: <25324178.post@talk.nabble.com> References: <25314145.post@talk.nabble.com> <200909060958.11114.mel.flynn+fbsd.questions@mailing.thruhere.net> <25316313.post@talk.nabble.com> <200909061238.32832.mel.flynn+fbsd.questions@mailing.thruhere.net> <25324178.post@talk.nabble.com> Date: Sun, 6 Sep 2009 22:08:52 -0500 Message-ID: <6201873e0909062008y4624d3d4y5eca6e21c82f4624@mail.gmail.com> From: Adam Vande More To: jaymax Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: Inconsistency in root partition size X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Sep 2009 03:08:53 -0000 Sun, Sep 6, 2009 at 9:24 PM, jaymax wrote: > > > > Mel Flynn-2 wrote: > > > > > > No, single user mode. Root partition in single user mode can be fsck'd > and > > repaired if mounted ro in single user. The system does fsck -p by > default, > > which skips partitions marked clean. Since you can shutdown cleanly, > > nothing > > will happen. > > Have a look at /etc/defaults/rc.conf for setting different behaviors by > > overriding the defaults in /etc/rc.conf. > > > > In single user mode I ran fsck -vy / > there were a few Salvages along the way > Rebooted but the condition remained unchanged. > rebooted again in single user mode ran fsck -vy /dev/ad0s1a > everything seemed clear - no salvage operation > Normal reboot, but discrepancy still persits > > Hope we have not reached a checkmate! > > from the logs the only things discernable, were > dmesg => > > > > ad0: 39083MB at ata0-master UDMA100 > > ad1: 76345MB at ata0-slave UDMA100 > > acd0: CDROM at ata1-master UDMA33 > > acd1: DVDR at ata1-slave UDMA33 > > ad4: 381554MB at ata2-master UDMA100 > > Trying to mount root from ufs:/dev/ad0s1a > > WARNING: /usr was not properly dismounted > > WARNING: /disk02 was not properly dismounted > > WARNING: /disk03 was not properly dismounted > > > > from /var/all.log the record for today > > Earlier mount attempt > > # grep -in ad0s1a all.log > 143:Sep 6 02:23:41 mach_1 kernel: Trying to mount root from > ufs:/dev/ad0s1a > 158:Sep 6 02:23:41 mach_1 kernel: /dev/ad0s1a: DEFER FOR BACKGROUND > CHECKING > 472:Sep 6 02:25:02 mach_1 fsck: /dev/ad0s1a: CANNOT CREATE SNAPSHOT > //.snap/fsck_snapshot: No space left on device > 474:Sep 6 02:25:02 mach_1 fsck: /dev/ad0s1a: UNEXPECTED INCONSISTENCY; RUN > fsck MANUALLY. > 985:Sep 6 03:11:21 mach_1 kernel: Trying to mount root from > ufs:/dev/ad0s1a > 1000:Sep 6 03:11:21 mach_1 kernel: /dev/ad0s1a: DEFER FOR BACKGROUND > CHECKING > 1315:Sep 6 03:13:08 mach_1 fsck: /dev/ad0s1a: CANNOT CREATE SNAPSHOT > //.snap/fsck_snapshot: No space left on device > 1317:Sep 6 03:13:08 mach_1 fsck: /dev/ad0s1a: UNEXPECTED INCONSISTENCY; > RUN > fsck MANUALLY. > > > last mount > > > 6311:Sep 6 17:39:33 mach_1 kernel: Trying to mount root from > ufs:/dev/ad0s1a > 6325:Sep 6 17:39:33 mach_1 kernel: /dev/ad0s1a: FILE SYSTEM CLEAN; > SKIPPING > CHECKS > 6326:Sep 6 17:39:33 mach_1 kernel: /dev/ad0s1a: clean, 1982 free (1966 > frags, 2 blocks, 0.8% fragmentation) > 6772:Sep 6 17:51:19 mach_1 kernel: Trying to mount root from > ufs:/dev/ad0s1a > 6786:Sep 6 17:51:19 mach_1 kernel: /dev/ad0s1a: FILE SYSTEM CLEAN; > SKIPPING > CHECKS > 6787:Sep 6 17:51:19 mach_1 kernel: /dev/ad0s1a: clean, 1968 free (1968 > frags, 0 blocks, 0.8% fragmentation) > > > and > df -k => > df -k > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad0s1a 507630 503694 -36674 108% / > > Don't know if the above can show anything > Could this be a kernel issue, tuning etc? > > Thanks! > -- > > ufs by default keeps a certain portion in reserve for use by root. 8% is the standard amount I believe so that capacity reading is technically valid. On rare occasion, I've had to run fsck multiple times. you may wish to try this also, w/ no reboot in between. -- Adam Vande More