From owner-freebsd-fs@FreeBSD.ORG Sun Oct 30 06:46:19 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5FCBB106566C for ; Sun, 30 Oct 2011 06:46:19 +0000 (UTC) (envelope-from haroldp@internal.org) Received: from pluto.internal.org (mail.internal.org [64.191.53.117]) by mx1.freebsd.org (Postfix) with ESMTP id 1755C8FC13 for ; Sun, 30 Oct 2011 06:46:18 +0000 (UTC) Received: from [10.0.0.79] (99-46-24-87.lightspeed.renonv.sbcglobal.net [99.46.24.87]) by pluto.internal.org (Postfix) with ESMTPA id CB60CEC9BE for ; Sat, 29 Oct 2011 23:46:16 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) From: Harold Paulson In-Reply-To: <20111023140222.GG1697@garage.freebsd.pl> Date: Sat, 29 Oct 2011 23:46:15 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <0D7D4701-925D-4BFC-A2BE-51892CD08B45@internal.org> References: <4D8047A6-930E-4DE8-BA55-051890585BFE@internal.org> <20111023140222.GG1697@garage.freebsd.pl> To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.1084) Subject: Re: Damaged directory on ZFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2011 06:46:19 -0000 Pawel,=20 On Oct 23, 2011, at 7:02 AM, Pawel Jakub Dawidek wrote: > On Mon, Oct 17, 2011 at 05:17:31PM -0700, Harold Paulson wrote: >> Hello,=20 >>=20 >> I've had a server that boots from ZFS panicking for a couple days. I = have worked around the problem for now, but I hope someone can give me = some insight into what's going on, and how I can solve it properly. =20 >>=20 >> The server is running 8.2-STABLE (zfs v28) with 8G of ram and 4 SATA = disks in a raid10 type arrangement: >>=20 >> # uname -a =20 >> FreeBSD jane.sierraweb.com 8.2-STABLE-201105 FreeBSD = 8.2-STABLE-201105 #0: Tue May 17 05:18:48 UTC 2011 = root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >>=20 >> And zpool status:=20 >>=20 >> NAME STATE READ WRITE CKSUM >> tank ONLINE 0 0 0 >> mirror ONLINE 0 0 0 >> gpt/disk0 ONLINE 0 0 0 >> gpt/disk1 ONLINE 0 0 0 >> mirror ONLINE 0 0 0 >> gpt/disk2 ONLINE 0 0 0 >> gpt/disk3 ONLINE 0 0 0 >>=20 >> It started panicking under load a couple days ago. We replaced RAM = and motherboard, but problems persisted. I don't know if a hardware = issue originally caused the problem or what. When it panics, I get the = usual panic message, but I don't get a core file, and it never reboots = itself. =20 >>=20 >> http://pastebin.com/F1J2AjSF >>=20 >> While I was trying to figure out the source of the problem, I notice = stuck various stuck processes that peg a CPU and can't be killed, such = as: >>=20 >> PID JID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU = COMMAND >> 48735 0 root 1 46 0 11972K 924K CPU3 3 415:14 = 100.00% find >>=20 >> They are not marked zombie, but I can't kill them, and restarting the = jail they are in won't even get rid of them. truss just hangs with no = output on them. On different occasions, I noticed pop3d processes for = the same user getting stuck in this way. On a hunch I ran a "find" = through the files in the user's Maildir and got a panic. I disabled = this account and now the server is stable again. At least until = locate.updatedb walks through that directory, I suppose. Evidentially, = there is some kind of hole in the file system below that directory tree = causing the panic. =20 >>=20 >> I can move that directory out of the way, and carry on, but is there = anything I can do to really *repair* the problem? >=20 > Could you run these commands: >=20 > objdump -D /boot/kernel/zfs.ko.symbols | egrep '^[0-9a-f]{8,16} = ' | awk '{printf("0x%s\n", $1)}' | xargs -J ADDR = printf "%u + %u\n" ADDR 0x111 | bc | xargs printf "0x%x\n" | xargs = addr2line -e /boot/kernel/zfs.ko.symbols >=20 > They should convert fzap_cursor_retrieve+0x111 info file:line. Send it > here once you obtain it. % objdump -D /boot/kernel/zfs.ko.symbols | egrep '^[0-9a-f]{8,16} = ' | awk '{printf("0x%s\n", $1)}' | xargs -J ADDR = printf "%u + %u\n" ADDR 0x111 | bc | xargs printf "0x%x\n" | xargs = addr2line -e /boot/kernel/zfs.ko.symbols = /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/= zap.c:1158 - H From owner-freebsd-fs@FreeBSD.ORG Sun Oct 30 08:49:06 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACE17106564A; Sun, 30 Oct 2011 08:49:06 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (unknown [IPv6:2a01:4f8:150:6101::4]) by mx1.freebsd.org (Postfix) with ESMTP id 4697C8FC12; Sun, 30 Oct 2011 08:49:06 +0000 (UTC) Received: from core2.vx.sk (localhost [127.0.0.2]) by mail.vx.sk (Postfix) with ESMTP id 73F13B119; Sun, 30 Oct 2011 09:49:05 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk by core2.vx.sk (amavisd-new, unix socket) with LMTP id AVQbgn44kmX2; Sun, 30 Oct 2011 09:49:03 +0100 (CET) Received: from [10.9.8.1] (188-167-78-15.dynamic.chello.sk [188.167.78.15]) by mail.vx.sk (Postfix) with ESMTPSA id 55937B110; Sun, 30 Oct 2011 09:49:03 +0100 (CET) Message-ID: <4EAD0F7E.8030301@FreeBSD.org> Date: Sun, 30 Oct 2011 09:49:02 +0100 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Robert Millan References: <20111028200824.GA2757@thorin> In-Reply-To: <20111028200824.GA2757@thorin> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Adrian Chadd Subject: Re: [PATCH] fix gratuitous dependencies in ZFS libraries / utilities X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2011 08:49:06 -0000 On 28. 10. 2011 22:08, Robert Millan wrote: > Hi, > > Some of the ZFS libraries and utilities are linked with libraries they > don't use: > > - zinject doesn't use libavl > - ztest doesn't use libz > - zdb uses neither libavl nor libz > - zfs uses neither libbsdxml nor libm, nor libsbuf > - zpool uses neither libbsdxml nor libm, nor libsbuf > > In addition, libzfs needs libm because it uses pow(), however it isn't > linked with -lm. This went unnoticed because all its users had -lm before. > > Attached patch (tested with "make buildworld") fixes these problems. Looks good + tested. -- Martin Matuska FreeBSD committer http://blog.vx.sk From owner-freebsd-fs@FreeBSD.ORG Sun Oct 30 11:10:11 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 220C1106564A for ; Sun, 30 Oct 2011 11:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 11D8D8FC08 for ; Sun, 30 Oct 2011 11:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9UBAAIJ083806 for ; Sun, 30 Oct 2011 11:10:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9UBAA21083805; Sun, 30 Oct 2011 11:10:10 GMT (envelope-from gnats) Date: Sun, 30 Oct 2011 11:10:10 GMT Message-Id: <201110301110.p9UBAA21083805@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/162008: [zfs] Latest 9-STABLE and 10-CURRENT fail to boot from ZFS v15 root [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2011 11:10:11 -0000 The following reply was made to PR kern/162008; it has been noted by GNATS. From: Andriy Gapon To: Robert Millan Cc: bug-followup@FreeBSD.org Subject: Re: kern/162008: [zfs] Latest 9-STABLE and 10-CURRENT fail to boot from ZFS v15 root [regression] Date: Sun, 30 Oct 2011 13:06:21 +0200 on 26/10/2011 20:34 Robert Millan said the following: > 2011/10/26 Andriy Gapon : >> >> Please let us know how _exactly_ your "kernel is no longer >> able to boot from my ZFS pool as root file system". >> That is, what boot stage fails and what output you see - (gpt)zfsboot, >> zfsloader, kernel, root fs mounting, something else... > > I'm sorry, I thought there was no meaningful error, but in closer look I notice: > > Mounting from zfs:eeepc/root failed with error 6. > > Assuming this means ENXIO, could it be a race condition? > IMO, not likely. Please try setting vfs.zfs.debug=1 via loader.conf. Maybe additional debug information will make the situation clearer. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Sun Oct 30 06:13:13 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB671106564A for ; Sun, 30 Oct 2011 06:13:13 +0000 (UTC) (envelope-from mmbsd1982@yahoo.com) Received: from nm21-vm0.bullet.mail.ne1.yahoo.com (nm21-vm0.bullet.mail.ne1.yahoo.com [98.138.90.94]) by mx1.freebsd.org (Postfix) with SMTP id 67EB68FC08 for ; Sun, 30 Oct 2011 06:13:13 +0000 (UTC) Received: from [98.138.90.48] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 30 Oct 2011 06:00:35 -0000 Received: from [98.138.88.239] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 30 Oct 2011 06:00:35 -0000 Received: from [127.0.0.1] by omp1039.mail.ne1.yahoo.com with NNFMP; 30 Oct 2011 06:00:35 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 97379.73447.bm@omp1039.mail.ne1.yahoo.com Received: (qmail 23939 invoked by uid 60001); 30 Oct 2011 06:00:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1319954435; bh=YMmp1+jxiUqnMGTcWeA1L/yntIid6566NJaQmw5E1vk=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=HXW+j/pSkcH52LrwxsvIzkCoVbDj8aNydm9OBc+pECNIa8zMtV9oZmogFYp1YtDtfHPMnnivcu1LrE8ODuY0PCqk6OxVBjLzNWzAOUZSm2HjvmyqVnLPTts3bbZShtAceCVUGA91czfNb8ZT/anWfWZDGHmQqmTy7mkOlGVn2qs= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=q5KNID4xJhnWCEtjjsoiS5Yq14lgPFBkLETsg5TA10LQIDGZZI9z6RQEW6R0R44MII7okDnJVytiYXR44QWB8tOUe3W8EH5d+qW0yD5/5+EcEiczilrqZyTWUnC8/oVDcNOuMeN6OMnfK+2bSwqJ01ucw24KuFz3RO7lrk6zE/Q=; X-YMail-OSG: 2ZoHX2oVM1m5WrrzuSJUBK8HL8_oArrzN6tiI8DyYlBLxKU batqS5cWdiiB1GDOwdszOj6WXE6T8tfwq6DHe84oN4_qXP6YPQuTIqQOIMuA xUGSfIeyLfcX8llCX8i_Hs9mJZN8fL41v94vyNmWXIURbIhfuYk9LivrYljI 8tJpkMUdqglrKtLr7v2w6od6viUGDnrVlniD6SuCfSnc.3jEmE0IM.XjbJWB 2jFoOA91VmKc9BSbB.plmJqubCf4aGQ1.Wa8EDETne3n3C7vODezedhIQceC wQacx2nJD8.qtvK2yfFRk0EkOdepaGD2zVANU0NrRXM5yInbq8mIUYakLsIW S.mgMyIADXZroSyOr8McX2xSrK0HgZ9LByeOZBJcwm.1hxo804gIcPFX7v9r BAgP3YBSwWVdAQa7OVu.y5PCMHUPgoCEG6d0th8Xtubpn8MeYpCGrofGdY07 2dkoXAJfZoPOuj0ADRPg6zG2YSeYk3HFfUScCulsfMxxEMR0CXG7tF_R7 Received: from [93.182.132.100] by web124703.mail.ne1.yahoo.com via HTTP; Sat, 29 Oct 2011 23:00:35 PDT X-Mailer: YahooMailClassic/14.0.11 YahooMailWebService/0.8.114.317681 Message-ID: <1319954435.22260.YahooMailClassic@web124703.mail.ne1.yahoo.com> Date: Sat, 29 Oct 2011 23:00:35 -0700 (PDT) From: Mm Bsd To: freebsd-fs@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 30 Oct 2011 11:21:51 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problems with EFI / partitioning with FreeBSD ONLY mac mini ... from USB drive ... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2011 06:13:13 -0000 I booted the 8.2-RELEASE CD on my Intel mac mini, which has a thumb drive p= lugged into USB. I promptly entered FIXIT and used dd to zero out the ENTIRE internal hard d= rive.=A0 I may use it, I may not, but for now I want to reduce variables an= d I don't want remnants of OSX on that disk tripping me up. I exited FIXIT and proceeded with a plain old install of FreeBSD 8.2 onto t= he thumb drive, which was seen as da0.=A0 Upon rebooting, I see a folder ic= on with a question mark inside of it, blinking on the screen.=A0 The mac mi= ni cannot see an OS to boot. I have tried to solve this by: - same as above, but "plain old" loader instead of FreeBSD boot manager.=A0= Both failed - During install, in FDISK, using the "T" option to change the type to 238 Still failing.=A0 Any idea what the missing part of this recipe is ? NOTE:=A0 I see something of an answer here: http://lists.freebsd.org/pipermail/freebsd-current/2011-September/027585.ht= ml But I do not know how to "put a dummy MBR there even if using GPT layout" .= .. so if that is the answer, some additional details, please :) Just trying to boot FreeBSD, and only FreeBSD, off of the thumb drive plugg= ed into a mac mini with no other disks.=A0 Any help appreciated. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 31 11:02:42 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE6BC106564A for ; Mon, 31 Oct 2011 11:02:42 +0000 (UTC) (envelope-from ivan.natchkov@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id A64F78FC12 for ; Mon, 31 Oct 2011 11:02:42 +0000 (UTC) Received: by ggnq2 with SMTP id q2so7683277ggn.13 for ; Mon, 31 Oct 2011 04:02:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=FsismdH0F3ioFzGOV9YPh7tR0vtQ52EINCEWL2/btOU=; b=gZ+PxifJ2UHlqX7fNEUP9u1UAF8ufTtmn5y/LmHe85bEDTWmOTYAvgWwpgMDbKNK/7 ReXEjRGLkr6ZsSfOVoTIRF5HoupI08pRWtJuvJskiSuHDM24infVcmYWBnPLmB//HUas tBHkQNBbcOyK9cpPFs78ndk5PUUh75Q4/YVyc= MIME-Version: 1.0 Received: by 10.43.43.130 with SMTP id uc2mr21981399icb.35.1320057246652; Mon, 31 Oct 2011 03:34:06 -0700 (PDT) Received: by 10.231.33.139 with HTTP; Mon, 31 Oct 2011 03:34:06 -0700 (PDT) Date: Mon, 31 Oct 2011 12:34:06 +0200 Message-ID: From: Ivan Natchkov To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ZFS question - clones vs dedupe X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2011 11:02:43 -0000 Hello to everyone, I have the following situation. EVA 4000 with 3T disk space and one oracle DB 1,2T on a different storage. On our EVA we must keep copy of this DB with non stop applying of archive logs. In addition we need 3-4 development DB's plus 3-4 test DB's which are copies of the original 1,2T DB and are stored on the EVA. We are thinking about 2 scenarios. 1) 8 clonings with keeping differences between the clonings 2) to have 8 different DB made with zfs send/receive on the same storage with deduplication switch ON. In both scenario we want the DB with applying logs to be with dedupe switched off because of the performance issues. I have 20 Gigs of RAM and the DDT table is possible to be kept in it with some tuning of sysctl. Which scenario would you recommend in terms of performance? Regards: Ivan From owner-freebsd-fs@FreeBSD.ORG Mon Oct 31 11:07:02 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D175F1065676 for ; Mon, 31 Oct 2011 11:07:02 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C01E98FC1C for ; Mon, 31 Oct 2011 11:07:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9VB72tH056739 for ; Mon, 31 Oct 2011 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9VB72iZ056737 for freebsd-fs@FreeBSD.org; Mon, 31 Oct 2011 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 31 Oct 2011 11:07:02 GMT Message-Id: <201110311107.p9VB72iZ056737@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2011 11:07:02 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/162083 fs [zfs] [panic] zfs unmount -f pool o kern/162008 fs [zfs] Latest 9-STABLE and 10-CURRENT fail to boot from o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161897 fs [zfs] [patch] zfs partition probing causing long delay o kern/161864 fs [ufs] removing journaling from UFS partition fails on o bin/161807 fs [patch] add option for explicitly specifying metadata o kern/161674 fs [ufs] snapshot on journaled ufs doesn't work o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161511 fs [unionfs] Filesystem deadlocks when using multiple uni o kern/161493 fs [nfs] NFS v3 directory structure update slow o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic o kern/160860 fs Random UFS root filesystem corruption with SU+J [regre o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159971 fs [ffs] [panic] panic with soft updates journaling durin o kern/159930 fs [ufs] [panic] kernel core o kern/159418 fs [tmpfs] [panic] tmpfs kernel panic: recursing on non r o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159233 fs [ext2fs] [patch] fs/ext2fs: finish reallocblk implemen o kern/159232 fs [ext2fs] [patch] fs/ext2fs: merge ext2_readwrite into o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs [amd] amd(8) ICMP storm and unkillable process. o kern/158711 fs [ffs] [panic] panic in ffs_blkfree and ffs_valloc o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157722 fs [geli] unable to newfs a geli encrypted partition o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs o kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 o kern/154447 fs [zfs] [panic] Occasional panics - solaris assert somew p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153847 fs [nfs] [panic] Kernel panic from incorrect m_free in nf o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small p kern/152488 fs [tmpfs] [patch] mtime of file updated when only inode o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o kern/151845 fs [smbfs] [patch] smbfs should be upgraded to support Un o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133174 fs [msdosfs] [patch] msdosfs must support multibyte inter o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs f kern/127375 fs [zfs] If vm.kmem_size_max>"1073741823" then write spee o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files f sparc/123566 fs [zfs] zpool import issue: EOVERFLOW o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 261 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 31 18:24:39 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B98DF106564A for ; Mon, 31 Oct 2011 18:24:39 +0000 (UTC) (envelope-from olavgjerde@yahoo.no) Received: from nm6-vm0.bullet.mail.ukl.yahoo.com (nm6-vm0.bullet.mail.ukl.yahoo.com [217.146.183.234]) by mx1.freebsd.org (Postfix) with SMTP id 0F3748FC08 for ; Mon, 31 Oct 2011 18:24:38 +0000 (UTC) Received: from [217.146.183.216] by nm6.bullet.mail.ukl.yahoo.com with NNFMP; 31 Oct 2011 18:12:09 -0000 Received: from [217.146.183.62] by tm9.bullet.mail.ukl.yahoo.com with NNFMP; 31 Oct 2011 18:12:09 -0000 Received: from [127.0.0.1] by omp1031.mail.ukl.yahoo.com with NNFMP; 31 Oct 2011 18:12:09 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 791629.25877.bm@omp1031.mail.ukl.yahoo.com Received: (qmail 55809 invoked by uid 60001); 31 Oct 2011 18:12:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.no; s=s1024; t=1320084729; bh=3qvkd37CS7ZTo3n4/3BlRZA63Mf4QFS3HbH7kYVSpb4=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=g0jQ/2RWHAbfcgPoLRHoPW2sPMMrLt8tkF6OYG6penp/QzXi9Beb6rP5nJi20QG6n/93VgcQV2yv1jTk2mFr8oy3e3M0RJdj7uZt+L1Fj/ZgDZeyVCXk5bsPGiXVl1x3Uv58o0+v6GoAoNKUT3jM7bL7hX4F31lynCzQLt/fVhg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.no; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=axjqWK763u1HTSitQDe8UUCk44JnasWNUOIhurOHMJKQdVCUwU8C89vFu/ibR+Kfbhdnf/Vts865az44wGh9VmyKgDFWaq2RDZ4BaRi90K0uKpjhM4mwq7KpuzGl9rJ3ONOQZV7t12fE+SnseXYIeQSrh4ST6smGb3fxWxLuiMY=; X-YMail-OSG: 0L1H0Y0VM1krJYJ6IYh8C.yQuBCSFr6cmQsYi7xPDHslt96 jGi59jBsh2VVYoXaGH_X.qWhWhWXa26m5QPed6nR8wVMHpquBvTqbWRGPYK4 6.wM0Dnf9fta6XP0P9Kz6t.k37kC7bwsY1IPVL8nJ_vZrsUuncfjvIF3hQfN 26b2zFVXLZ1whssTsvii8bb9K_EooOmuiQbwW62U2wYGZJJJu1JA7uBI4Fcf q8IsBUKCNylTGPNL6Zvt25deutdMxaT8lJ_JGhA2NMr_yTQBL0X8y9Dv_h4v gabcuurM1CWwVB79wE0nWvgLgBNEw2PkXAFKXZXtTnAoposTOmXONg7kpphh opThSriRsJWzFtHIxNcbiKbTzhuvMSsC.x3qh7mncuZUYmQJX1nygGTSxV8H MmX6QfiWjuRo3PXUIrw-- Received: from [79.161.100.14] by web28204.mail.ukl.yahoo.com via HTTP; Mon, 31 Oct 2011 18:12:09 GMT X-Mailer: YahooMailWebService/0.8.114.317681 Message-ID: <1320084729.49009.YahooMailNeo@web28204.mail.ukl.yahoo.com> Date: Mon, 31 Oct 2011 18:12:09 +0000 (GMT) From: Olav Gjerde To: "freebsd-fs@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: How to use graid? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Olav Gjerde List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2011 18:24:39 -0000 I'm testing a new installation of FreeBSD 9 RC-1 and installed with the def= ault GPT partition. =0A=0A=0AHow can I create a mirror with the new graid? = There is no example in the manual=0AFrom the manual I belive the command = =0A=0A$graid label gm0 intel raid1 /dev/da0 =0A=0Ashould=A0 be correct? But= I keep getting a "Class not found" error.=0A From owner-freebsd-fs@FreeBSD.ORG Mon Oct 31 22:33:20 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C04F106566C for ; Mon, 31 Oct 2011 22:33:20 +0000 (UTC) (envelope-from andrey.kosachenko@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9B05D8FC14 for ; Mon, 31 Oct 2011 22:33:19 +0000 (UTC) Received: by bkbzs2 with SMTP id zs2so4031880bkb.13 for ; Mon, 31 Oct 2011 15:33:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BoeqS8P5KdGVJ1L6TES7HrJaQyI+qyFmodiarsnSXCg=; b=f4eBaUlsb3I8n68QtDUWsVNHCDBn9xMNOPa/iM5HT9EoOuj0OFhN+V64tA1q0FzWmP asT+V+ms5dsSG9yg4akTzxMUcMjxwsnBO0U7oQ23A2b4bFFDB54BUij3TKU8PFBnCfLm 7YWKaqwUANJ41TBEVkDQwUDAp0B4zf9UE1BiY= Received: by 10.204.145.78 with SMTP id c14mr12721053bkv.42.1320098874838; Mon, 31 Oct 2011 15:07:54 -0700 (PDT) Received: from beastie.intra ([195.60.174.66]) by mx.google.com with ESMTPS id v6sm11386586bkt.1.2011.10.31.15.07.52 (version=SSLv3 cipher=OTHER); Mon, 31 Oct 2011 15:07:53 -0700 (PDT) Message-ID: <4EAF1C36.9010209@gmail.com> Date: Tue, 01 Nov 2011 00:07:50 +0200 From: Andrey Kosachenko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0) Gecko/20111001 Thunderbird/7.0 MIME-Version: 1.0 To: Harold Paulson References: <4D8047A6-930E-4DE8-BA55-051890585BFE@internal.org> <20111023140222.GG1697@garage.freebsd.pl> <0D7D4701-925D-4BFC-A2BE-51892CD08B45@internal.org> In-Reply-To: <0D7D4701-925D-4BFC-A2BE-51892CD08B45@internal.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, pjd@FreeBSD.org Subject: Re: Damaged directory on ZFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2011 22:33:20 -0000 Hi, On 30.10.2011 08:46, Harold Paulson wrote: > Pawel, > > On Oct 23, 2011, at 7:02 AM, Pawel Jakub Dawidek wrote: > >> On Mon, Oct 17, 2011 at 05:17:31PM -0700, Harold Paulson wrote: >>> Hello, >>> >>> I've had a server that boots from ZFS panicking for a couple days. I have worked around the problem for now, but I hope someone can give me some insight into what's going on, and how I can solve it properly. >>> >>> The server is running 8.2-STABLE (zfs v28) with 8G of ram and 4 SATA disks in a raid10 type arrangement: >>> >>> # uname -a >>> FreeBSD jane.sierraweb.com 8.2-STABLE-201105 FreeBSD 8.2-STABLE-201105 #0: Tue May 17 05:18:48 UTC 2011 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >>> >>> And zpool status: >>> >>> NAME STATE READ WRITE CKSUM >>> tank ONLINE 0 0 0 >>> mirror ONLINE 0 0 0 >>> gpt/disk0 ONLINE 0 0 0 >>> gpt/disk1 ONLINE 0 0 0 >>> mirror ONLINE 0 0 0 >>> gpt/disk2 ONLINE 0 0 0 >>> gpt/disk3 ONLINE 0 0 0 >>> >>> It started panicking under load a couple days ago. We replaced RAM and motherboard, but problems persisted. I don't know if a hardware issue originally caused the problem or what. When it panics, I get the usual panic message, but I don't get a core file, and it never reboots itself. >>> >>> http://pastebin.com/F1J2AjSF >>> >>> While I was trying to figure out the source of the problem, I notice stuck various stuck processes that peg a CPU and can't be killed, such as: >>> >>> PID JID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND >>> 48735 0 root 1 46 0 11972K 924K CPU3 3 415:14 100.00% find >>> >>> They are not marked zombie, but I can't kill them, and restarting the jail they are in won't even get rid of them. truss just hangs with no output on them. On different occasions, I noticed pop3d processes for the same user getting stuck in this way. On a hunch I ran a "find" through the files in the user's Maildir and got a panic. I disabled this account and now the server is stable again. At least until locate.updatedb walks through that directory, I suppose. Evidentially, there is some kind of hole in the file system below that directory tree causing the panic. >>> >>> I can move that directory out of the way, and carry on, but is there anything I can do to really *repair* the problem? the same is observed over here (I'm running CURRENT system dated by Sun Oct 16 14:53:49 EEST 2011). Attempts to run any file commands (ls, find etc) on such directory (in my case it is /usr/local/include/dirac) make those commands hang (kill -9 doesn't help). Though my system doesn't panic. >> Could you run these commands: >> >> objdump -D /boot/kernel/zfs.ko.symbols | egrep '^[0-9a-f]{8,16}' | awk '{printf("0x%s\n", $1)}' | xargs -J ADDR printf "%u + %u\n" ADDR 0x111 | bc | xargs printf "0x%x\n" | xargs addr2line -e /boot/kernel/zfs.ko.symbols >> >> They should convert fzap_cursor_retrieve+0x111 info file:line. Send it >> here once you obtain it. > > % objdump -D /boot/kernel/zfs.ko.symbols | egrep '^[0-9a-f]{8,16}' | awk '{printf("0x%s\n", $1)}' | xargs -J ADDR printf "%u + %u\n" ADDR 0x111 | bc | xargs printf "0x%x\n" | xargs addr2line -e /boot/kernel/zfs.ko.symbols > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap.c:1158 output of suggested command just the same as Harolds's, i.e.: objdump -D /boot/kernel/zfs.ko.symbols | egrep '^[0-9a-f]{8,16} ' | awk '{printf("0x%s\n", $1)}' | xargs -J ADDR printf "%u + %u\n" ADDR 0x111 | bc | xargs printf "0x%x\n" | xargs addr2line -e /boot/kernel/zfs.ko.symbols /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zap.c:1158 -- WBR, Andrey Kosachenko From owner-freebsd-fs@FreeBSD.ORG Tue Nov 1 03:41:18 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75B9F106566B for ; Tue, 1 Nov 2011 03:41:18 +0000 (UTC) (envelope-from jwd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 657578FC0C for ; Tue, 1 Nov 2011 03:41:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pA13fILq090397 for ; Tue, 1 Nov 2011 03:41:18 GMT (envelope-from jwd@freefall.freebsd.org) Received: (from jwd@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pA13fIeY090391 for freebsd-fs@freebsd.org; Tue, 1 Nov 2011 03:41:18 GMT (envelope-from jwd) Date: Tue, 1 Nov 2011 03:41:18 +0000 From: John To: freebsd-fs@freebsd.org Message-ID: <20111101034118.GA73746@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: (Yet Another) Damaged directory on ZFS? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2011 03:41:18 -0000 Hi Folks, We have a zfs fileserver running 9.0-RC1 which appears to have locked up in a manner similar to the "Damanged directory on ZFS" thread. It started after a zfs snapshat which appears to have hung. At that point, an "ls" command on a directory which is either empty or contains only other directories works correctly. An "ls" on a directory containing a file will hang. The OS is installed on an OCZ card with UFS, ZFS is only used for the data volume. The following information is rather large and is available here: http://people.freebsd.org/~jwd/tx_sync_done.html On the page: zfs snapshot (which appears to have caused the issue) an ls that works (on empty or directory with only directories) an ls that hangs (directory contains files) zpool history that hangs ps -auxww procstat -kk -a zpool status zfs list df -hl zfs list -t sysctl -a (Very, Very large) uname -a (as below) FreeBSD server1 9.0-RC1 FreeBSD 9.0-RC1 #0 r226607M: Fri Oct 21 11:32:01 EDT 2011 neh@server1:/usr/obj/usr/src.2011-10-21_01.37.40/sys/ZFS amd64 The system is sitting idle at this point if we can provide any additional debugging informtion. Please let me know. Thanks, John From owner-freebsd-fs@FreeBSD.ORG Tue Nov 1 03:52:58 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A83C4106564A; Tue, 1 Nov 2011 03:52:58 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 52B8A8FC0C; Tue, 1 Nov 2011 03:52:57 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAH1sr06DaFvO/2dsb2JhbABDFoRhpUWBcgEpVjIDAg0ZAlEOiB2iTpF8gTCGPoEUBJQPkXs X-IronPort-AV: E=Sophos;i="4.69,436,1315195200"; d="scan'208";a="142153541" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 31 Oct 2011 23:52:57 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 7A550B3F0C; Mon, 31 Oct 2011 23:52:57 -0400 (EDT) Date: Mon, 31 Oct 2011 23:52:57 -0400 (EDT) From: Rick Macklem To: FS List Message-ID: <780905615.915177.1320119577445.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: Subject: NFS client patch that implements a list of dirty byte ranges in a buffer X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2011 03:52:58 -0000 Hi, I created this patch after the discussion by John Baldwin in late August under the Subject: Fixes to allow write clustering of NFS writes from a FreeBSD NFS client First off, I am in no way trying to "steal John's thunder" and I hope he will continue pursuing the good work he's doing on the above. However, I thought that the patch might be interesting to others who like to live on the "bleeding edge" and use NFS for source tree building, since the patch seems to help with the performance of that. My simple test using a run of "make -j4 buildworld" without/with the patch reduced the elapsed time from 4:17 to 2:42. (This was in no way a benchmark and used very slow single core i386 hardware, but it at least suggests that the patch may be useful.) So, if anyone is interested in trying the patch, it is at: http://people.freebsd.org/~rmacklem/dirtybuflist.patch But, be forewarned, this patch has been minimally tested and only on single core i386 hardware. If you do try the patch, please let me know how it goes, rick From owner-freebsd-fs@FreeBSD.ORG Tue Nov 1 08:29:17 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4088106564A for ; Tue, 1 Nov 2011 08:29:16 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5B5688FC0A for ; Tue, 1 Nov 2011 08:29:15 +0000 (UTC) Received: by bkbzs2 with SMTP id zs2so4393171bkb.13 for ; Tue, 01 Nov 2011 01:29:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=j6VcG9x9DD3NWZrBh5AmfPx8xlYKZ47v+dzYm55Cn54=; b=j4kiqjeTCb9ZqXwR73HmAzL2DEby1febtmVBCCaWFq+iH5QcN7CT6jMkv4gw6e72HL mPIddatvQaMSOXNmxoQI+YWsxpivhjFPWRXvMDBGVhfTufOGsWAO0m7fb0lY39oV+rNp Vwspooq/EwMuGlHrXRp7ntlq33WROlWcgOCI0= Received: by 10.204.9.1 with SMTP id j1mr13913898bkj.57.1320134656726; Tue, 01 Nov 2011 01:04:16 -0700 (PDT) Received: from limbo.lan ([195.225.157.86]) by mx.google.com with ESMTPS id w8sm19735423bks.11.2011.11.01.01.04.14 (version=SSLv3 cipher=OTHER); Tue, 01 Nov 2011 01:04:15 -0700 (PDT) Message-ID: <4EAFA7FC.4060304@gmail.com> Date: Tue, 01 Nov 2011 10:04:12 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:7.0.1) Gecko/20111002 Thunderbird/7.0.1 MIME-Version: 1.0 To: Andrey Kosachenko References: <4D8047A6-930E-4DE8-BA55-051890585BFE@internal.org> <20111023140222.GG1697@garage.freebsd.pl> <0D7D4701-925D-4BFC-A2BE-51892CD08B45@internal.org> <4EAF1C36.9010209@gmail.com> In-Reply-To: <4EAF1C36.9010209@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, pjd@FreeBSD.org Subject: Re: Damaged directory on ZFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2011 08:29:17 -0000 01.11.2011 00:07, Andrey Kosachenko wrote: >>>> I can move that directory out of the way, and carry on, but is there >>>> anything I can do to really *repair* the problem? > the same is observed over here (I'm running CURRENT system dated by Sun > Oct 16 14:53:49 EEST 2011). Attempts to run any file commands (ls, find > etc) on such directory (in my case it is /usr/local/include/dirac) make > those commands hang (kill -9 doesn't help). Though my system doesn't panic. I got the same when my world was built with gcc. When I switched to clang machine begins to throw panic correctly. I have already posted screenshots: http://lists.freebsd.org/pipermail/freebsd-fs/2011-September/012530.html I was wrong, this is not about high load. It was one directory in btpd configuration folder. Upon removing that directory everything works fine. By "removing directory" I mean "moving everything to another filesystem and getting rid of old one". -- Sphinx of black quartz judge my vow. From owner-freebsd-fs@FreeBSD.ORG Tue Nov 1 17:55:28 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9BA0106566B for ; Tue, 1 Nov 2011 17:55:28 +0000 (UTC) (envelope-from shivaram.u@quadstor.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9A11E8FC08 for ; Tue, 1 Nov 2011 17:55:28 +0000 (UTC) Received: by iabz21 with SMTP id z21so3674360iab.13 for ; Tue, 01 Nov 2011 10:55:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.28.106 with SMTP id l42mr84581ibc.66.1320168337058; Tue, 01 Nov 2011 10:25:37 -0700 (PDT) Received: by 10.231.60.204 with HTTP; Tue, 1 Nov 2011 10:25:36 -0700 (PDT) X-Originating-IP: [117.192.117.147] In-Reply-To: References: Date: Tue, 1 Nov 2011 22:55:36 +0530 Message-ID: From: Shivaram Upadhyayula To: Dennis Glatting Content-Type: multipart/mixed; boundary=001517740adcc62d6f04b0afa4bf X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS/compression/performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2011 17:55:29 -0000 --001517740adcc62d6f04b0afa4bf Content-Type: text/plain; charset=ISO-8859-1 On Thu, Oct 13, 2011 at 9:47 AM, Dennis Glatting wrote: > On Wed, 2011-10-12 at 08:59 +0100, Steven Hartland wrote: > ----- Original Message ----- >> >> From: "Dennis Glatting" >> >> >> Have you tried using the alternative compression algorithms >> e.g. lzjb or gzip-[1-5] the default gzip = gzip-6 >> > > I have tried lzjb and I am unimpressed. I have not tried different levels of > gzip on ZFS but I have tried it on documents with results I expected. > > As I mentioned, I have a lot of data. Two files were 26GB uncompressed but I > had to kill those data sets because I ran out of room (I have reorganized my > arrays since then). My ZFS compression ratio is 4.93x and I would require > more storage at different gzip levels or ljzb. > > An option is not too compress with ZFS rather directly with gzip however I > would still need lots of temporary storage for manipulation, which is what I > am doing now (e.g., sort). Processing with zcat isn't always a good solution > because some applications want files, but you have to do what you have to > do. > A few years back there was a discussion of about the possibility of other compression algorithms in ZFS (http://mail.opensolaris.org/pipermail/zfs-discuss/2007-June/011952.html). But it looks like there hasn't been anything much further on that. I have recently started using ZFS and during that time i have tried out ZFS with lzf (http://oldhome.schmorp.de/marc/liblzf.html) and it seems to perform much better, both in speed and ratio over lzjb. Anyway my point is that, somewhere down the line other compression algorithms should be evaluated. gzip seems slow and it looks like lzjb may not be sufficient. For anyone interested, I have attached some of the tests i had run and the diff for lzf support. Cheers, Shivaram -- Reduce Storage expenditure with QUADStor Storage Virtualization http://www.quadstor.com --001517740adcc62d6f04b0afa4bf-- From owner-freebsd-fs@FreeBSD.ORG Tue Nov 1 21:17:14 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12C7F1065670 for ; Tue, 1 Nov 2011 21:17:14 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from ita.aagh.net (unknown [IPv6:2a03:9800:10:11::2]) by mx1.freebsd.org (Postfix) with ESMTP id A86958FC08 for ; Tue, 1 Nov 2011 21:17:13 +0000 (UTC) Received: from cpc1-hart9-2-0-cust900.11-3.cable.virginmedia.com ([86.30.3.133] helo=voi.aagh.net ident=mailnull) by ita.aagh.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RLLhm-000EZB-P9; Tue, 01 Nov 2011 21:17:10 +0000 Received: from freaky by voi.aagh.net with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1RLLhm-000DUC-Er; Tue, 01 Nov 2011 21:17:10 +0000 Date: Tue, 1 Nov 2011 21:17:10 +0000 From: Thomas Hurst To: Shivaram Upadhyayula Message-ID: <20111101211710.GA36797@voi.aagh.net> Mail-Followup-To: Thomas Hurst , Shivaram Upadhyayula , Dennis Glatting , freebsd-fs@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Not much. User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 86.30.3.133 X-SA-Exim-Mail-From: tom.hurst@clara.net X-SA-Exim-Scanned: No (on ita.aagh.net); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org Subject: Re: ZFS/compression/performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2011 21:17:14 -0000 * Shivaram Upadhyayula (shivaram.u@quadstor.com) wrote: > I have recently started using ZFS and during that time i have tried out > ZFS with lzf (http://oldhome.schmorp.de/marc/liblzf.html) and it seems > to perform much better, both in speed and ratio over lzjb. > > Anyway my point is that, somewhere down the line other compression > algorithms should be evaluated. gzip seems slow and it looks like lzjb > may not be sufficient. For anyone interested, I have attached some of > the tests i had run and the diff for lzf support. No you haven't :) -- Thomas 'Freaky' Hurst http://hur.st/ From owner-freebsd-fs@FreeBSD.ORG Tue Nov 1 21:54:21 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02A09106566C; Tue, 1 Nov 2011 21:54:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CE51D8FC15; Tue, 1 Nov 2011 21:54:20 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pA1LsKhX038998; Tue, 1 Nov 2011 21:54:20 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pA1LsKiE038994; Tue, 1 Nov 2011 21:54:20 GMT (envelope-from linimon) Date: Tue, 1 Nov 2011 21:54:20 GMT Message-Id: <201111012154.pA1LsKiE038994@freefall.freebsd.org> To: yanegomi@gmail.com, linimon@FreeBSD.org, gnats-admin@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/162222: Re: kern/154447: [zfs] [panic] Occasional panics - solaris assert somewhere in ZFS code X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2011 21:54:21 -0000 Old Synopsis: Fwd: kern/154447: [zfs] [panic] Occasional panics - solaris assert New Synopsis: Re: kern/154447: [zfs] [panic] Occasional panics - solaris assert somewhere in ZFS code State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Tue Nov 1 21:53:34 UTC 2011 State-Changed-Why: Misfiled followup to kern/154447; content migrated. Responsible-Changed-From-To: gnats-admin->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Nov 1 21:53:34 UTC 2011 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=162222 From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 06:07:50 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74CE11065674 for ; Wed, 2 Nov 2011 06:07:50 +0000 (UTC) (envelope-from shivaram.u@quadstor.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 475778FC0C for ; Wed, 2 Nov 2011 06:07:50 +0000 (UTC) Received: by iabz21 with SMTP id z21so4677812iab.13 for ; Tue, 01 Nov 2011 23:07:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.28.106 with SMTP id l42mr485014ibc.66.1320214069491; Tue, 01 Nov 2011 23:07:49 -0700 (PDT) Received: by 10.231.60.204 with HTTP; Tue, 1 Nov 2011 23:07:49 -0700 (PDT) X-Originating-IP: [117.192.99.131] In-Reply-To: <20111101211710.GA36797@voi.aagh.net> References: <20111101211710.GA36797@voi.aagh.net> Date: Wed, 2 Nov 2011 11:37:49 +0530 Message-ID: From: Shivaram Upadhyayula To: Thomas Hurst , Shivaram Upadhyayula , Dennis Glatting , freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: ZFS/compression/performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 06:07:50 -0000 Sorry i didn't know it will be stripped out :-) http://www.quadstor.com/ietbsd/compression.tgz LZF diff is against FreeBSD8-STABLE checkout about a week ago. Cheers, Shivaram On Wed, Nov 2, 2011 at 2:47 AM, Thomas Hurst wrote: > * Shivaram Upadhyayula (shivaram.u@quadstor.com) wrote: > >> I have recently started using ZFS and during that time i have tried out >> ZFS with lzf (http://oldhome.schmorp.de/marc/liblzf.html) and it seems >> to perform much better, both in speed and ratio over lzjb. >> >> Anyway my point is that, somewhere down the line other compression >> algorithms should be evaluated. gzip seems slow and it looks like lzjb >> may not be sufficient. For anyone interested, I have attached some of >> the tests i had run and the diff for lzf support. > > No you haven't :) > > -- > Thomas 'Freaky' Hurst > =A0 =A0http://hur.st/ > --=20 Reduce Storage expenditure with QUADStor Storage Virtualization http://www.quadstor.com From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 06:38:11 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA9AE1065673 for ; Wed, 2 Nov 2011 06:38:11 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by mx1.freebsd.org (Postfix) with ESMTP id 8506F8FC1A for ; Wed, 2 Nov 2011 06:38:11 +0000 (UTC) Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by QMTA11.westchester.pa.mail.comcast.net with comcast id s6eB1h0011c6gX85B6eBRY; Wed, 02 Nov 2011 06:38:11 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta23.westchester.pa.mail.comcast.net with comcast id s6eA1h00E1t3BNj3j6eBNf; Wed, 02 Nov 2011 06:38:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 32B0D102C19; Tue, 1 Nov 2011 23:38:09 -0700 (PDT) Date: Tue, 1 Nov 2011 23:38:09 -0700 From: Jeremy Chadwick To: Shivaram Upadhyayula Message-ID: <20111102063809.GA50463@icarus.home.lan> References: <20111101211710.GA36797@voi.aagh.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS/compression/performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 06:38:11 -0000 On Wed, Nov 02, 2011 at 11:37:49AM +0530, Shivaram Upadhyayula wrote: > Sorry i didn't know it will be stripped out :-) > http://www.quadstor.com/ietbsd/compression.tgz LZF diff is against > FreeBSD8-STABLE checkout about a week ago. Are you sure about that? $ egrep '^---' lzffinal.diff --- cddl/boot/zfs/zfsimpl.h 2011-10-26 14:50:35.000000000 +0530 --- cddl/boot/zfs/zfssubr.c 2011-10-26 14:50:35.000000000 +0530 --- cddl/contrib/opensolaris/common/zfs/zfs_prop.c 2011-10-26 14:50:36.000000000 +0530 --- cddl/contrib/opensolaris/uts/common/Makefile.files 2011-10-27 14:21:41.000000000 +0530 --- cddl/contrib/opensolaris/uts/common/fs/zfs/lzf.c 1970-01-01 05:30:00.000000000 +0530 --- cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h 2011-10-26 14:50:36.000000000 +0530 --- cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio_compress.h 2011-10-26 14:50:36.000000000 +0530 --- cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c 2011-10-26 14:50:37.000000000 +0530 These pathnames don't reflect reality on FreeBSD RELENG_8. There are no such path names, both on our RELENG_8 systems, nor in CVS: $ ls -l /usr/src/cddl/boot ls: /usr/src/cddl/boot: No such file or directory $ ls -l /usr/src/cddl/contrib/opensolaris/uts ls: /usr/src/cddl/contrib/opensolaris/uts: No such file or directory $ ls -l /usr/src/cddl/contrib/opensolaris total 30 -rw-r--r-- 1 root wheel 18924 Mar 28 2008 OPENSOLARIS.LICENSE drwxr-xr-x 16 root wheel 512 Jun 23 00:43 cmd/ drwxr-xr-x 4 root wheel 512 Jun 23 00:43 common/ drwxr-xr-x 2 root wheel 512 Jun 23 00:43 head/ drwxr-xr-x 10 root wheel 512 Jun 23 00:43 lib/ drwxr-xr-x 3 root wheel 512 Jun 23 00:43 tools/ In CVS there used to be a src/cddl/contrib/opensolaris/uts/common directory but everything in it now is under Attic/, which means it's been deprecated. See for yourself: http://www.freebsd.org/cgi/cvsweb.cgi/src/cddl/contrib/opensolaris/uts/common/ Please advise. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 06:41:42 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F06D1065807 for ; Wed, 2 Nov 2011 06:41:41 +0000 (UTC) (envelope-from shivaram.u@quadstor.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id EED448FC15 for ; Wed, 2 Nov 2011 06:41:40 +0000 (UTC) Received: by iabz21 with SMTP id z21so4731378iab.13 for ; Tue, 01 Nov 2011 23:41:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.154.7 with SMTP id o7mr2115868icw.48.1320216099794; Tue, 01 Nov 2011 23:41:39 -0700 (PDT) Received: by 10.231.60.204 with HTTP; Tue, 1 Nov 2011 23:41:39 -0700 (PDT) X-Originating-IP: [117.192.99.131] In-Reply-To: <20111102063809.GA50463@icarus.home.lan> References: <20111101211710.GA36797@voi.aagh.net> <20111102063809.GA50463@icarus.home.lan> Date: Wed, 2 Nov 2011 12:11:39 +0530 Message-ID: From: Shivaram Upadhyayula To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS/compression/performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 06:41:42 -0000 path root is /usr/src/sys/ Cheers, Shivaram On Wed, Nov 2, 2011 at 12:08 PM, Jeremy Chadwick wrote: > On Wed, Nov 02, 2011 at 11:37:49AM +0530, Shivaram Upadhyayula wrote: >> Sorry i didn't know it will be stripped out :-) >> http://www.quadstor.com/ietbsd/compression.tgz LZF diff is against >> FreeBSD8-STABLE checkout about a week ago. > > Are you sure about that? > > $ egrep '^---' lzffinal.diff > --- cddl/boot/zfs/zfsimpl.h =A0 =A0 2011-10-26 14:50:35.000000000 +0530 > --- cddl/boot/zfs/zfssubr.c =A0 =A0 2011-10-26 14:50:35.000000000 +0530 > --- cddl/contrib/opensolaris/common/zfs/zfs_prop.c =A0 =A0 =A02011-10-26 = 14:50:36.000000000 +0530 > --- cddl/contrib/opensolaris/uts/common/Makefile.files =A02011-10-27 14:2= 1:41.000000000 +0530 > --- cddl/contrib/opensolaris/uts/common/fs/zfs/lzf.c =A0 =A01970-01-01 05= :30:00.000000000 +0530 > --- cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h =A0 =A0 =A0 =A02= 011-10-26 14:50:36.000000000 +0530 > --- cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio_compress.h =A0 =A0= =A0 2011-10-26 14:50:36.000000000 +0530 > --- cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c =A0 2011-10= -26 14:50:37.000000000 +0530 > > These pathnames don't reflect reality on FreeBSD RELENG_8. =A0There are n= o > such path names, both on our RELENG_8 systems, nor in CVS: > > $ ls -l /usr/src/cddl/boot > ls: /usr/src/cddl/boot: No such file or directory > > $ ls -l /usr/src/cddl/contrib/opensolaris/uts > ls: /usr/src/cddl/contrib/opensolaris/uts: No such file or directory > > $ ls -l /usr/src/cddl/contrib/opensolaris > total 30 > -rw-r--r-- =A0 =A01 root =A0 =A0 =A0wheel =A0 =A0 18924 Mar 28 =A02008 OP= ENSOLARIS.LICENSE > drwxr-xr-x =A0 16 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 cmd/ > drwxr-xr-x =A0 =A04 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 co= mmon/ > drwxr-xr-x =A0 =A02 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 he= ad/ > drwxr-xr-x =A0 10 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 lib/ > drwxr-xr-x =A0 =A03 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 to= ols/ > > In CVS there used to be a src/cddl/contrib/opensolaris/uts/common directo= ry > but everything in it now is under Attic/, which means it's been > deprecated. =A0See for yourself: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/cddl/contrib/opensolaris/uts/co= mmon/ > > Please advise. > > -- > | Jeremy Chadwick =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0jdc at parodius.com | > | Parodius Networking =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://= www.parodius.com/ | > | UNIX Systems Administrator =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mountain= View, CA, US | > | Making life hard for others since 1977. =A0 =A0 =A0 =A0 =A0 =A0 =A0 PGP= 4BD6C0CB | > > --=20 Reduce Storage expenditure with QUADStor Storage Virtualization http://www.quadstor.com From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 06:43:50 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2004F106564A for ; Wed, 2 Nov 2011 06:43:50 +0000 (UTC) (envelope-from shivaram.u@quadstor.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id D773E8FC1A for ; Wed, 2 Nov 2011 06:43:49 +0000 (UTC) Received: by iabz21 with SMTP id z21so4734599iab.13 for ; Tue, 01 Nov 2011 23:43:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.36.168 with SMTP id r8mr1882051igj.49.1320216229346; Tue, 01 Nov 2011 23:43:49 -0700 (PDT) Received: by 10.231.60.204 with HTTP; Tue, 1 Nov 2011 23:43:49 -0700 (PDT) X-Originating-IP: [117.192.99.131] In-Reply-To: References: <20111101211710.GA36797@voi.aagh.net> <20111102063809.GA50463@icarus.home.lan> Date: Wed, 2 Nov 2011 12:13:49 +0530 Message-ID: From: Shivaram Upadhyayula To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS/compression/performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 06:43:50 -0000 Sorry i meant patch root. To apply cd /usr/src/sys && patch -p0 < Cheers On Wed, Nov 2, 2011 at 12:11 PM, Shivaram Upadhyayula wrote: > path root is /usr/src/sys/ > > Cheers, > Shivaram > > On Wed, Nov 2, 2011 at 12:08 PM, Jeremy Chadwick > wrote: >> On Wed, Nov 02, 2011 at 11:37:49AM +0530, Shivaram Upadhyayula wrote: >>> Sorry i didn't know it will be stripped out :-) >>> http://www.quadstor.com/ietbsd/compression.tgz LZF diff is against >>> FreeBSD8-STABLE checkout about a week ago. >> >> Are you sure about that? >> >> $ egrep '^---' lzffinal.diff >> --- cddl/boot/zfs/zfsimpl.h =A0 =A0 2011-10-26 14:50:35.000000000 +0530 >> --- cddl/boot/zfs/zfssubr.c =A0 =A0 2011-10-26 14:50:35.000000000 +0530 >> --- cddl/contrib/opensolaris/common/zfs/zfs_prop.c =A0 =A0 =A02011-10-26= 14:50:36.000000000 +0530 >> --- cddl/contrib/opensolaris/uts/common/Makefile.files =A02011-10-27 14:= 21:41.000000000 +0530 >> --- cddl/contrib/opensolaris/uts/common/fs/zfs/lzf.c =A0 =A01970-01-01 0= 5:30:00.000000000 +0530 >> --- cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h =A0 =A0 =A0 =A0= 2011-10-26 14:50:36.000000000 +0530 >> --- cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio_compress.h =A0 = =A0 =A0 2011-10-26 14:50:36.000000000 +0530 >> --- cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c =A0 2011-1= 0-26 14:50:37.000000000 +0530 >> >> These pathnames don't reflect reality on FreeBSD RELENG_8. =A0There are = no >> such path names, both on our RELENG_8 systems, nor in CVS: >> >> $ ls -l /usr/src/cddl/boot >> ls: /usr/src/cddl/boot: No such file or directory >> >> $ ls -l /usr/src/cddl/contrib/opensolaris/uts >> ls: /usr/src/cddl/contrib/opensolaris/uts: No such file or directory >> >> $ ls -l /usr/src/cddl/contrib/opensolaris >> total 30 >> -rw-r--r-- =A0 =A01 root =A0 =A0 =A0wheel =A0 =A0 18924 Mar 28 =A02008 O= PENSOLARIS.LICENSE >> drwxr-xr-x =A0 16 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 cmd= / >> drwxr-xr-x =A0 =A04 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 c= ommon/ >> drwxr-xr-x =A0 =A02 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 h= ead/ >> drwxr-xr-x =A0 10 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 lib= / >> drwxr-xr-x =A0 =A03 root =A0 =A0 =A0wheel =A0 =A0 =A0 512 Jun 23 00:43 t= ools/ >> >> In CVS there used to be a src/cddl/contrib/opensolaris/uts/common direct= ory >> but everything in it now is under Attic/, which means it's been >> deprecated. =A0See for yourself: >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/cddl/contrib/opensolaris/uts/c= ommon/ >> >> Please advise. >> >> -- >> | Jeremy Chadwick =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0jdc at parodius.com | >> | Parodius Networking =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http:/= /www.parodius.com/ | >> | UNIX Systems Administrator =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mountai= n View, CA, US | >> | Making life hard for others since 1977. =A0 =A0 =A0 =A0 =A0 =A0 =A0 PG= P 4BD6C0CB | >> >> > > > > -- > Reduce Storage expenditure with QUADStor Storage Virtualization > http://www.quadstor.com > --=20 Reduce Storage expenditure with QUADStor Storage Virtualization http://www.quadstor.com From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 12:14:55 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5392106566B for ; Wed, 2 Nov 2011 12:14:55 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop04.sare.net (proxypop04.sare.net [194.30.0.65]) by mx1.freebsd.org (Postfix) with ESMTP id 7ADCB8FC16 for ; Wed, 2 Nov 2011 12:14:55 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPSA id 60B399DC464 for ; Wed, 2 Nov 2011 12:57:38 +0100 (CET) From: Borja Marcos Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 2 Nov 2011 12:57:33 +0100 Message-Id: To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 12:14:55 -0000 Hi Today I=B4ve come across an issue long ago forgotten :) Running out of = i-nodes. The condition was triggered on a 8 GB /usr filesystem which includes the = ports tree, on which I have compiled several ports and their = dependencies. I know, maybe not the best practices, it's a machine = being used to test a couple of thingies, but I wonder how many newbies = can run into such a problem. I guess many. Filesystem 1K-blocks Used Avail Capacity iused = ifree %iused Mounted on /dev/ad1s1e 8245660 5308960 2277048 70% 507099 61219 = 89% /usr Now i-nodes aren't completely full, as I have deleted /usr/obj (turns = out I had made a make world as well). Looking at the number of i-nodes per /usr subdirectory, I have noticed = that, wow! /usr/ports consumes A LOT of them.=20 freebsd9-borja# find . -print | wc -l 405481 I know the /usr isn't that large, and I know that I have compiled a lot = on this battered /usr filesystem, but with the increasing complexity of = many programs and the increased number of dependences in ports, I would: 1) At least double the default number of i-nodes per filesystem 2) Suggest strongly in sysinstall to create a /usr/ports filesystem for = the ports. But probably this won't be popular and many people will tend = to create a single large root to rule them all.... What do you think? I can't imagine what it might have been if I had = compiled Gnome or KDE... :D Borja. For the record, the ports I had compiled are: drwxr-xr-x 3 root wheel 512 Oct 11 18:21 converters/libiconv/work drwxr-xr-x 3 root wheel 512 Oct 13 12:19 converters/php52-iconv/work drwxr-xr-x 3 root wheel 512 Oct 13 11:16 databases/db42/work drwxr-xr-x 3 root wheel 512 Oct 13 11:14 databases/gdbm/work drwxr-xr-x 3 root wheel 512 Oct 13 12:05 = databases/mysql51-client/work drwxr-xr-x 3 root wheel 512 Oct 13 12:13 = databases/mysql51-server/work drwxr-xr-x 3 root wheel 512 Oct 13 12:19 databases/php52-mysql/work drwxr-xr-x 3 root wheel 512 Oct 13 12:19 databases/php52-pdo/work drwxr-xr-x 3 root wheel 512 Oct 13 12:20 = databases/php52-pdo_mysql/work drwxr-xr-x 3 root wheel 512 Oct 13 12:19 = databases/php52-pdo_sqlite/work drwxr-xr-x 3 root wheel 512 Oct 13 12:21 databases/php52-sqlite/work drwxr-xr-x 3 root wheel 1024 Oct 13 10:34 databases/rrdtool/work drwxr-xr-x 4 root wheel 512 Oct 13 11:18 devel/apr1/work drwxr-xr-x 2 root wheel 512 Oct 13 11:12 devel/autoconf-wrapper/work drwxr-xr-x 3 root wheel 512 Oct 13 11:12 devel/autoconf/work drwxr-xr-x 2 root wheel 512 Oct 13 11:13 devel/automake-wrapper/work drwxr-xr-x 3 root wheel 512 Oct 13 11:14 devel/automake/work drwxr-xr-x 3 root wheel 512 Oct 13 10:26 devel/bison/work drwxr-xr-x 3 root wheel 512 Oct 13 10:24 devel/gamin/work drwxr-xr-x 3 root wheel 512 Oct 11 18:25 devel/gettext/work drwxr-xr-x 3 root wheel 512 Oct 13 10:24 devel/gio-fam-backend/work drwxr-xr-x 3 root wheel 1024 Oct 13 10:22 devel/glib20/work drwxr-xr-x 3 root wheel 512 Oct 11 18:25 devel/gmake/work drwxr-xr-x 4 root wheel 1024 Oct 13 10:27 = devel/gobject-introspection/work drwxr-xr-x 3 root wheel 512 Oct 11 18:28 devel/gperf/work drwxr-xr-x 3 root wheel 512 Oct 11 18:29 devel/libcheck/work drwxr-xr-x 3 root wheel 512 Oct 17 17:06 devel/libevent/work drwxr-xr-x 3 root wheel 512 Oct 13 10:26 devel/libffi/work drwxr-xr-x 3 root wheel 512 Oct 11 18:40 devel/libpthread-stubs/work drwxr-xr-x 3 root wheel 512 Oct 11 18:20 devel/libtool/work drwxr-xr-x 3 root wheel 512 Oct 13 10:25 devel/m4/work drwxr-xr-x 3 root wheel 512 Oct 13 11:12 = devel/p5-Locale-gettext/work drwxr-xr-x 3 root wheel 512 Oct 13 11:27 devel/p5-TimeDate/work drwxr-xr-x 3 root wheel 512 Oct 13 10:19 devel/pcre/work drwxr-xr-x 3 root wheel 512 Oct 13 12:19 devel/php52-json/work drwxr-xr-x 3 root wheel 512 Oct 13 12:18 devel/php52-pcre/work drwxr-xr-x 3 root wheel 512 Oct 13 12:18 devel/php52-spl/work drwxr-xr-x 3 root wheel 512 Oct 13 12:21 devel/php52-tokenizer/work drwxr-xr-x 3 root wheel 512 Oct 11 18:26 devel/pkg-config/work drwxr-xr-x 3 root wheel 512 Oct 11 18:41 devel/xorg-macros/work drwxr-xr-x 3 root wheel 512 Oct 13 10:24 graphics/cairo/work drwxr-xr-x 3 root wheel 512 Oct 13 09:00 graphics/png/work drwxr-xr-x 2 root wheel 512 Oct 13 12:22 lang/php52-extensions/work drwxr-xr-x 3 root wheel 512 Oct 13 11:21 lang/php52/work drwxr-xr-x 3 root wheel 1024 Oct 11 18:39 lang/python27/work drwxr-xr-x 3 root wheel 512 Oct 13 11:27 mail/p5-Mail-Tools/work drwxr-xr-x 3 root wheel 512 Oct 13 11:12 misc/help2man/work drwxr-xr-x 3 root wheel 512 Oct 17 17:04 net/bird/work drwxr-xr-x 5 root wheel 1024 Oct 17 17:08 net/openbgpd/work drwxr-xr-x 4 root wheel 512 Oct 17 17:06 net/openospfd/work drwxr-xr-x 3 root wheel 512 Oct 13 12:20 net/php52-sockets/work drwxr-xr-x 3 root wheel 512 Oct 11 18:27 print/freetype2/work drwxr-xr-x 3 root wheel 1024 Oct 11 18:33 security/libgcrypt/work drwxr-xr-x 3 root wheel 512 Oct 11 18:32 security/libgpg-error/work drwxr-xr-x 3 root wheel 512 Oct 13 12:18 security/php52-filter/work drwxr-xr-x 3 root wheel 512 Oct 13 12:18 security/php52-hash/work drwxr-xr-x 3 root wheel 512 Oct 13 12:20 sysutils/php52-posix/work drwxr-xr-x 3 root wheel 512 Oct 11 18:26 textproc/expat2/work drwxr-xr-x 3 root wheel 512 Oct 11 18:26 textproc/intltool/work drwxr-xr-x 3 root wheel 512 Oct 11 18:36 textproc/libxml2/work drwxr-xr-x 3 root wheel 512 Oct 11 18:36 textproc/libxslt/work drwxr-xr-x 3 root wheel 512 Oct 11 18:26 textproc/p5-XML-Parser/work drwxr-xr-x 3 root wheel 512 Oct 13 12:17 textproc/php52-ctype/work drwxr-xr-x 3 root wheel 512 Oct 13 12:18 textproc/php52-dom/work drwxr-xr-x 3 root wheel 512 Oct 13 12:18 = textproc/php52-simplexml/work drwxr-xr-x 3 root wheel 512 Oct 13 12:21 textproc/php52-xml/work drwxr-xr-x 3 root wheel 512 Oct 13 12:22 = textproc/php52-xmlreader/work drwxr-xr-x 3 root wheel 512 Oct 13 12:22 = textproc/php52-xmlwriter/work drwxr-xr-x 3 root wheel 512 Oct 13 11:19 www/apache22-event-mpm/work drwxr-xr-x 3 root wheel 512 Oct 13 13:18 www/mod_fcgid/work drwxr-xr-x 3 root wheel 512 Oct 13 12:20 www/php52-session/work drwxr-xr-x 3 root wheel 512 Oct 13 10:32 x11-fonts/bdftopcf/work drwxr-xr-x 3 root wheel 512 Oct 13 10:32 = x11-fonts/bitstream-vera/work drwxr-xr-x 3 root wheel 512 Oct 13 10:32 x11-fonts/encodings/work drwxr-xr-x 3 root wheel 512 Oct 13 10:30 x11-fonts/font-bh-ttf/work drwxr-xr-x 3 root wheel 512 Oct 13 10:31 = x11-fonts/font-misc-ethiopic/work drwxr-xr-x 3 root wheel 512 Oct 13 10:30 = x11-fonts/font-misc-meltho/work drwxr-xr-x 3 root wheel 512 Oct 13 10:32 x11-fonts/font-util/work drwxr-xr-x 3 root wheel 1024 Oct 13 09:01 x11-fonts/fontconfig/work drwxr-xr-x 3 root wheel 512 Oct 13 10:31 x11-fonts/fontsproto/work drwxr-xr-x 3 root wheel 512 Oct 13 10:32 x11-fonts/libXfont/work drwxr-xr-x 3 root wheel 512 Oct 13 10:28 x11-fonts/libXft/work drwxr-xr-x 3 root wheel 512 Oct 13 10:30 x11-fonts/libfontenc/work drwxr-xr-x 3 root wheel 512 Oct 13 10:30 x11-fonts/mkfontdir/work drwxr-xr-x 3 root wheel 512 Oct 13 10:30 x11-fonts/mkfontscale/work drwxr-xr-x 3 root wheel 512 Oct 11 18:43 = x11-fonts/xf86bigfontproto/work drwxr-xr-x 2 root wheel 512 Oct 13 10:32 = x11-fonts/xorg-fonts-truetype/work drwxr-xr-x 3 root wheel 512 Oct 13 10:33 x11-toolkits/pango/work drwxr-xr-x 3 root wheel 512 Oct 11 18:41 x11/bigreqsproto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:42 x11/inputproto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:42 x11/kbproto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:45 x11/libX11/work drwxr-xr-x 3 root wheel 512 Oct 11 18:29 x11/libXau/work drwxr-xr-x 3 root wheel 512 Oct 11 18:29 x11/libXdmcp/work drwxr-xr-x 3 root wheel 512 Oct 11 18:45 x11/libXrender/work drwxr-xr-x 3 root wheel 512 Oct 11 18:40 x11/libxcb/work drwxr-xr-x 3 root wheel 512 Oct 13 10:18 x11/pixman/work drwxr-xr-x 3 root wheel 512 Oct 11 18:41 x11/renderproto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:39 x11/xcb-proto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:40 x11/xcb-util/work drwxr-xr-x 3 root wheel 512 Oct 11 18:41 x11/xcmiscproto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:42 x11/xextproto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:29 x11/xproto/work drwxr-xr-x 3 root wheel 512 Oct 11 18:42 x11/xtrans/work From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 12:45:32 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9839D106566B for ; Wed, 2 Nov 2011 12:45:32 +0000 (UTC) (envelope-from radiomlodychbandytow@o2.pl) Received: from moh1-ve2.go2.pl (moh1-ve2.go2.pl [193.17.41.132]) by mx1.freebsd.org (Postfix) with ESMTP id 29A5C8FC18 for ; Wed, 2 Nov 2011 12:45:31 +0000 (UTC) Received: from moh1-ve2.go2.pl (unknown [10.0.0.132]) by moh1-ve2.go2.pl (Postfix) with ESMTP id F2E1D1044099 for ; Wed, 2 Nov 2011 13:45:28 +0100 (CET) Received: from unknown (unknown [10.0.0.142]) by moh1-ve2.go2.pl (Postfix) with SMTP for ; Wed, 2 Nov 2011 13:45:28 +0100 (CET) Received: from host892524678.com-promis.3s.pl [89.25.246.78] by poczta.o2.pl with ESMTP id xQCQnb; Wed, 02 Nov 2011 13:45:28 +0100 Message-ID: <4EB13B65.20507@o2.pl> Date: Wed, 02 Nov 2011 13:45:25 +0100 From: =?UTF-8?B?UmFkaW8gbcWCb2R5Y2ggYmFuZHl0w7N3?= User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20111102120026.5F28D1065741@hub.freebsd.org> In-Reply-To: <20111102120026.5F28D1065741@hub.freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-O2-Trust: 2, 67 X-O2-SPF: neutral Cc: Subject: Re: freebsd-fs Digest, Vol 437, Issue 3 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 12:45:32 -0000 On 2011-11-02 13:00, freebsd-fs-request@freebsd.org wrote: > Message: 1 > Date: Tue, 1 Nov 2011 22:55:36 +0530 > From: Shivaram Upadhyayula > Subject: Re: ZFS/compression/performance > To: Dennis Glatting > Cc:freebsd-fs@freebsd.org > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > On Thu, Oct 13, 2011 at 9:47 AM, Dennis Glatting wrote: >> > On Wed, 2011-10-12 at 08:59 +0100, Steven Hartland wrote: >> > ----- Original Message ----- >>> >> >>> >> From: "Dennis Glatting" >>> >> >>> >> > >>> >> Have you tried using the alternative compression algorithms >>> >> e.g. lzjb or gzip-[1-5] the default gzip = gzip-6 >>> >> >> > >> > I have tried lzjb and I am unimpressed. I have not tried different levels of >> > gzip on ZFS but I have tried it on documents with results I expected. >> > >> > As I mentioned, I have a lot of data. Two files were 26GB uncompressed but I >> > had to kill those data sets because I ran out of room (I have reorganized my >> > arrays since then). My ZFS compression ratio is 4.93x and I would require >> > more storage at different gzip levels or ljzb. >> > >> > An option is not too compress with ZFS rather directly with gzip however I >> > would still need lots of temporary storage for manipulation, which is what I >> > am doing now (e.g., sort). Processing with zcat isn't always a good solution >> > because some applications want files, but you have to do what you have to >> > do. >> > > A few years back there was a discussion of about the possibility of > other compression algorithms in ZFS > (http://mail.opensolaris.org/pipermail/zfs-discuss/2007-June/011952.html). > But it looks like there hasn't been anything much further on that. I > have recently started using ZFS and during that time i have tried out > ZFS with lzf (http://oldhome.schmorp.de/marc/liblzf.html) and it seems > to perform much better, both in speed and ratio over lzjb. > > Anyway my point is that, somewhere down the line other compression > algorithms should be evaluated. gzip seems slow and it looks like lzjb > may not be sufficient. For anyone interested, I have attached some of > the tests i had run and the diff for lzf support. > > Cheers, > Shivaram > > -- Reduce Storage expenditure with QUADStor Storage Virtualization > http://www.quadstor.com I did some synthetic tests and lzf was OK, but not great. LZJB was terrible though. http://encode.ru/threads/1266-In-memory-benchmark-with-fastest-LZSS-%28QuickLZ-Snappy%29-compressors?p=25913#post25913 https://extrememoderate.wordpress.com/2011/08/14/synthetic-test-of-filesystem-compression-part-1/ https://extrememoderate.wordpress.com/2011/08/20/synthetic-test-of-filesystem-compression-part-2/ I'm in the process of doing a more comprehensive part 3 and I think that LZ4 should be better. -- Twoje radio From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 13:13:13 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98CDE106566C for ; Wed, 2 Nov 2011 13:13:13 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 8092C8FC08 for ; Wed, 2 Nov 2011 13:13:13 +0000 (UTC) Received: from omta11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by qmta08.emeryville.ca.mail.comcast.net with comcast id sD7K1h0010mlR8UA8DD5hT; Wed, 02 Nov 2011 13:13:05 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta11.emeryville.ca.mail.comcast.net with comcast id sDA91h00g1t3BNj8XDAA4Y; Wed, 02 Nov 2011 13:10:10 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id BA7B8102C19; Wed, 2 Nov 2011 06:13:11 -0700 (PDT) Date: Wed, 2 Nov 2011 06:13:11 -0700 From: Jeremy Chadwick To: Borja Marcos Message-ID: <20111102131311.GA56941@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 13:13:13 -0000 On Wed, Nov 02, 2011 at 12:57:33PM +0100, Borja Marcos wrote: > Today I?ve come across an issue long ago forgotten :) Running out of i-nodes. The last time I dealt with this was about 3 months ago, on a Netapp filer; hardly forgotten. :-) > The condition was triggered on a 8 GB /usr filesystem which includes the ports tree, on which I have compiled several ports and their dependencies. I know, maybe not the best practices, it's a machine being used to test a couple of thingies, but I wonder how many newbies can run into such a problem. I guess many. > > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on > /dev/ad1s1e 8245660 5308960 2277048 70% 507099 61219 89% /usr > > Now i-nodes aren't completely full, as I have deleted /usr/obj (turns out I had made a make world as well). > > Looking at the number of i-nodes per /usr subdirectory, I have noticed that, wow! /usr/ports consumes A LOT of them. > > freebsd9-borja# find . -print | wc -l > 405481 "find -x /usr/ports | wc -l" on my system returns 146420. "find -x /usr | wc -l" on my system returns 264901 (and this includes a populated /usr/obj buildworld/buildkernel tree. /usr/obj returns 37126, just for the record). $ df -k -i /usr Filesystem 1024-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ada0s1f 38110116 3425114 31636194 10% 258980 4686938 5% /usr Your 8GB filesystem is only ~21% the capacity of mine. So if we do some simple math, your /usr should really be showing (assuming yours is as "bare bones" as mine) around 26% inodes used. Yet what you have is 89%. You probably just have a lot of other software on /usr that "abuses" lots of individual files. You list off what ports you built from source, which means you have lots of "build cruft" laying around en masse (work/ directories). > I know the /usr isn't that large, and I know that I have compiled a > lot on this battered /usr filesystem, but with the increasing > complexity of many programs and the increased number of dependences in > ports, I would: > > 1) At least double the default number of i-nodes per filesystem > > 2) Suggest strongly in sysinstall to create a /usr/ports filesystem > for the ports. But probably this won't be popular and many people will > tend to create a single large root to rule them all.... Really? That isn't what the default installer does (re: single filesystem), and hasn't since... well, as long as I can remember (2.2.8). If someone chooses to create a single / for all of their stuff, so be it. It's their choice. This is very much a "Linux-ism"; I used to do the same thing back when I used Linux in the early 90s and was quickly taught why it's both useful *and* bad. > What do you think? Here's what I think: I wouldn't recommend a /usr/ports filesystem. It solves nothing. Imagine: /usr/ports can now run out of inodes while /usr won't. What would this address? It would decrease impact to applications creating new files on /usr. How often do you have that happening on your system? For me it's extremely rare. For comparison, /var gets a lot more activity. Adding a /usr/ports filesystem also provides zero scalability. Meaning: say someone decides "8GB for /usr/ports is enough" during the installer and so on. Then down the road, we run out of space, or inodes, or whatever else. Oops, what now? Symlinks all over the place? Yeah, not going to happen. We were already in this boat regarding the root filesystem size, which for quite some time defaulted to 512MBytes, which was not enough. Today, the default size is 1GBytes, which is enough for a kernel built with debugging symbols and so on, but tends to reach ~55-58% used. There's a reason /usr on FreeBSD defaults to "all the remaining space on the disk" if you pick the defaults/auto. Surprise. :-) The summarised version is: 1. You have control over this yourself: newfs(8) -i flag. You can even input this flag during sysinstall when building a new system. 2. When you built the system, you chose to assume /usr should be 8GBytes. Your usage habits may have changed, software gotten larger, etc.. It may be time for you to re-evaluate how you create your filesystems and what sizes you choose. You chose something that didn't scale. :-) 3. Get in the habit of cleaning up after yourself. Don't leave work/ directories laying around inside your ports ("make install clean" solves this problem, but the clean phase only happens at the end of whatever is being built, including dependencies). 4. For a limited-space (not just size but inodes!) filesystem, consider using packages (pkg_add -r) for anything that does not require customisation during the build/configure phase. For example, for quite some time now on my systems, I've always installed the package versions of perl, python27, cmake, gettext, pcre, etc. solely because they are "key softwares" that I hate building from source. 5. Most FreeBSD Ports folks are aware and respectful as much as possible of limited-space environments, especially due to those on embedded platforms. A very hot topic/debate many years ago was whether or not there should be a new file introduced into each ports' directory to define some dependency bits. Obviously it did not happen. I'm not sure all committers are aware of this though. For example, a recent (new) port I submitted contained 2 files in files/ (two patches). The committer chose to split this up into 14 files (which not only wastes more inodes, but also makes my life as port maintainer a bigger PITA given where the patches come from). You get the idea I'm sure. > I can't imagine what it might have been if I had compiled Gnome or KDE... :D I imagine you would have experienced that your filesystem ran out of inodes. Oh wait, you said it did... :-) "What" was compiled has no bearing on the situation; failure is failure, whether you were building Office.org or compiling a 4-file C program. > For the record, the ports I had compiled are: > {snip} -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 13:36:53 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EC95106564A for ; Wed, 2 Nov 2011 13:36:53 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id D1EC78FC15 for ; Wed, 2 Nov 2011 13:36:52 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id pA2DagAf037330 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 2 Nov 2011 15:36:48 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <4EB1476A.3070204@digsys.bg> Date: Wed, 02 Nov 2011 15:36:42 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111007 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20111102131311.GA56941@icarus.home.lan> In-Reply-To: <20111102131311.GA56941@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 13:36:53 -0000 On 02.11.11 15:13, Jeremy Chadwick wrote: > On Wed, Nov 02, 2011 at 12:57:33PM +0100, Borja Marcos wrote: >> Today I?ve come across an issue long ago forgotten :) Running out of i-nodes. > [...] > > There's a reason /usr on FreeBSD defaults to "all the remaining space on > the disk" if you pick the defaults/auto. Surprise. :-) > > The summarised version is: > > 1. You have control over this yourself: newfs(8) -i flag. You can even > input this flag during sysinstall when building a new system. > > [...] Just for the completeness of it, one would use ZFS and be done with this issue. :-) That would be point 0. in my personal list of suggestions. All the rest would be "if you have good reason to not use ZFS". Daniel From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 13:49:21 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51A751065672 for ; Wed, 2 Nov 2011 13:49:21 +0000 (UTC) (envelope-from Lee@Dilkie.com) Received: from spock.dilkie.com (spock.dilkie.com [IPv6:2001:470:8900::40]) by mx1.freebsd.org (Postfix) with ESMTP id C26F88FC13 for ; Wed, 2 Nov 2011 13:49:20 +0000 (UTC) Received: from [IPv6:2001:4978:f:4bf::2] (cl-1216.chi-02.us.sixxs.net [IPv6:2001:4978:f:4bf::2]) (authenticated bits=0) by spock.dilkie.com (8.14.5/8.14.5) with ESMTP id pA2Dn0AT033347 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 2 Nov 2011 09:49:03 -0400 (EDT) (envelope-from Lee@Dilkie.com) X-DKIM: Sendmail DKIM Filter v2.8.3 spock.dilkie.com pA2Dn0AT033347 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dilkie.com; s=mail; t=1320241744; bh=oMv996sBrdH3n49omyL8sPvgaTIob4fkxay84wj9z5A=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=MZq8wBfA9nryvR9rVwRibxfZf7mlJ8y/defJy8aCPdy40OqMBNcNX7UWEHfCZvOpF qsoN3rH192rXJ1Czm/7yv4NawtZ6RlGyKjq2etE1YDgHudOZeJ8Yasaxy+Dfxqk Message-ID: <4EB14A47.8010107@Dilkie.com> Date: Wed, 02 Nov 2011 13:48:55 +0000 From: Lee Dilkie User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Daniel Kalchev References: <20111102131311.GA56941@icarus.home.lan> <4EB1476A.3070204@digsys.bg> In-Reply-To: <4EB1476A.3070204@digsys.bg> X-Enigmail-Version: 1.3.2 X-Scanned-By: MIMEDefang 2.72 on IPv6:2001:470:8900::40 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 13:49:21 -0000 On 11/2/2011 1:36 PM, Daniel Kalchev wrote: > > > On 02.11.11 15:13, Jeremy Chadwick wrote: >> On Wed, Nov 02, 2011 at 12:57:33PM +0100, Borja Marcos wrote: >>> Today I?ve come across an issue long ago forgotten :) Running out of >>> i-nodes. >> [...] >> >> There's a reason /usr on FreeBSD defaults to "all the remaining space on >> the disk" if you pick the defaults/auto. Surprise. :-) >> >> The summarised version is: >> >> 1. You have control over this yourself: newfs(8) -i flag. You can even >> input this flag during sysinstall when building a new system. >> >> [...] > > Just for the completeness of it, one would use ZFS and be done with > this issue. :-) Are you suggesting that ZFS be the default FS? My only concern with ZFS is that it still appears to be in flux and have some issues. I don't know, from monitoring this list, if those are issues that heavy load users experience and ZFS is as stable as UFS or if it isn't. I just know I see issues being raised. -lee From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 14:10:27 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D07B106566B for ; Wed, 2 Nov 2011 14:10:27 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 832A98FC14 for ; Wed, 2 Nov 2011 14:10:27 +0000 (UTC) Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta12.emeryville.ca.mail.comcast.net with comcast id sE4E1h0020S2fkCACEAL9D; Wed, 02 Nov 2011 14:10:20 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta09.emeryville.ca.mail.comcast.net with comcast id sEAe1h0091t3BNj8VEAf3p; Wed, 02 Nov 2011 14:10:39 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8EBA6102C19; Wed, 2 Nov 2011 07:10:25 -0700 (PDT) Date: Wed, 2 Nov 2011 07:10:25 -0700 From: Jeremy Chadwick To: Lee Dilkie Message-ID: <20111102141025.GA58230@icarus.home.lan> References: <20111102131311.GA56941@icarus.home.lan> <4EB1476A.3070204@digsys.bg> <4EB14A47.8010107@Dilkie.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EB14A47.8010107@Dilkie.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 14:10:27 -0000 On Wed, Nov 02, 2011 at 01:48:55PM +0000, Lee Dilkie wrote: > > On 11/2/2011 1:36 PM, Daniel Kalchev wrote: > > > > > > On 02.11.11 15:13, Jeremy Chadwick wrote: > >> On Wed, Nov 02, 2011 at 12:57:33PM +0100, Borja Marcos wrote: > >>> Today I?ve come across an issue long ago forgotten :) Running out of > >>> i-nodes. > >> [...] > >> > >> There's a reason /usr on FreeBSD defaults to "all the remaining space on > >> the disk" if you pick the defaults/auto. Surprise. :-) > >> > >> The summarised version is: > >> > >> 1. You have control over this yourself: newfs(8) -i flag. You can even > >> input this flag during sysinstall when building a new system. > >> > >> [...] > > > > Just for the completeness of it, one would use ZFS and be done with > > this issue. :-) > > Are you suggesting that ZFS be the default FS? > > My only concern with ZFS is that it still appears to be in flux and have > some issues. I don't know, from monitoring this list, if those are > issues that heavy load users experience and ZFS is as stable as UFS or > if it isn't. I just know I see issues being raised. This is a valid concern. The posts that come in to -fs and -stable on a weekly basis about ZFS haven't diminished (from what I can tell). Blindly recommending ZFS as a replacement is something I tend to look down on at this point -- but Daniel's point is true, the issue of inodes is more or less moot on ZFS. :-) The important thing to note here is that every ZFS situation has to be treated separate; sometimes there are wider-spread issues that are known or addressed, but the majority of the time the problem is specific to that individual reporter. This is different than how it was, say, a year ago. However, key folks like Ivan Voras, for example, are waiting on ZFS on FreeBSD to "settle down" before revisiting using it. "Settle down" in this context means "when there isn't an issue/commit being done to it practically every week". As for our systems, we use ZFS for /home and /var/mail on multi-user systems, as well as for our system that handles backups, but we don't use things like ZFS-on-root, boot from ZFS pools, GPT, or other "more involved" things; we apply KISS principle as much as possible and that definitely helps. Heck, at this point we only have one loader.conf tunable (vfs.zfs.arc_max), which is great. Regardless we'll be keeping our root, /usr, /var, and /tmp on UFS2 for quite some time: it "just works" with no risks that can catch me off-guard during scenarios where I need things to "just work". (Last thing I need to be dealing with in the middle of a production problem is, say, weird filesystem ordeals...) I also appreciate the commits/focus being done to ZFS on RELENG_8 on a regular basis, and the commit comments have greatly improved in recent days. So it's a little easier to follow, for me anyway. mm@'s posts on zfs-devel are also insightful and given a hint of fixes/issues which Illumos finds and thus can be backported to FreeBSD. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 14:14:57 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FB331065672 for ; Wed, 2 Nov 2011 14:14:57 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 099E58FC1A for ; Wed, 2 Nov 2011 14:14:56 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id pA2EEZ4A037612 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 2 Nov 2011 16:14:41 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <4EB1504B.3080107@digsys.bg> Date: Wed, 02 Nov 2011 16:14:35 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111007 Thunderbird/7.0.1 MIME-Version: 1.0 To: Lee Dilkie References: <20111102131311.GA56941@icarus.home.lan> <4EB1476A.3070204@digsys.bg> <4EB14A47.8010107@Dilkie.com> In-Reply-To: <4EB14A47.8010107@Dilkie.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 14:14:57 -0000 On 02.11.11 15:48, Lee Dilkie wrote: > > On 11/2/2011 1:36 PM, Daniel Kalchev wrote: >> >> >> On 02.11.11 15:13, Jeremy Chadwick wrote: >>> On Wed, Nov 02, 2011 at 12:57:33PM +0100, Borja Marcos wrote: >>>> Today I?ve come across an issue long ago forgotten :) Running out >>>> of i-nodes. >>> >> Just for the completeness of it, one would use ZFS and be done with >> this issue. :-) > > Are you suggesting that ZFS be the default FS? Not really. Perhaps we might think about something like this in 10.0 or 11.0 -- today too many people are wary of ZFS and there are already trivial ways to have ZFS-only FreeBSD install - so no need to hurry. > My only concern with ZFS is that it still appears to be in flux and > have some issues. I don't know, from monitoring this list, if those > are issues that heavy load users experience and ZFS is as stable as > UFS or if it isn't. I just know I see issues being raised. > Personally, I have two issues with ZFS: memory use and ... that it exposes very quickly bad hardware. I am currently at something like ~85% of my systems farm converted to ZFS-only. In the process, too many components proved to be bad. Disks, that previously were 'wonderful', display CRC errors in ZFS. Guess what --- these disks were happily reading/writing garbage with UFS and nobody ever noticed! This is a serious "issue" with going to ZFS .. that has me prompted to convert any active system to use ZFS-only, although that would require much more resources memory-wise. Another issue I have with ZFS is that it is not (yet) trivial to use for read-only installs, especially on the root. I have a multitude of systems that mount all their 'system' partitions read-only (UFS) and only data partitions are writable. I have yet to discover how one does this with ZFS only. Yet another issue, more pronounced with v28 than with v15 is that when your zpool gets full, performance becomes abysmal. That is particularly bad for systems that are nearly full most of the time --- easily fixable with larger disks, I know.. Yet another issue with ZFS is that while the traditional UNIX partittioning semantics has been local (such as, partittions a,b,c on drive1 are different than partittions a,b,c on drive2), ZFS pool names are global. You cannot have two 'system' pools on the same system and that makes some historic habits difficult to apply. The same trouble is with GEOM/GPT labels too, so we may just have to grow up. Other than that, my experience with ZFS has been more than wonderful. Daniel From owner-freebsd-fs@FreeBSD.ORG Wed Nov 2 19:43:14 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A18B1065674 for ; Wed, 2 Nov 2011 19:43:14 +0000 (UTC) (envelope-from prvs=1287dce182=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 8614C8FC0C for ; Wed, 2 Nov 2011 19:43:13 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Wed, 02 Nov 2011 19:32:19 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 02 Nov 2011 19:32:19 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50016153453.msg for ; Wed, 02 Nov 2011 19:32:19 +0000 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1287dce182=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@FreeBSD.ORG Message-ID: <3BA4142083B3413E86CB874A37154749@multiplay.co.uk> From: "Steven Hartland" To: Date: Wed, 2 Nov 2011 19:32:19 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 Cc: Subject: booting of large raidz2 fails - all block copies unavailable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2011 19:43:14 -0000 Just installed a machine using mfsbsd 8.2-RELEASE with raidz2 across 14 x 3TB Disks but boot fails with the following at the boot loader:- ZFS: i/o error - all block copies unavailable There seems to have been several threads on this in the past but all seem to have been resolved a long time ago. I tried 9.0rc1 mfsbsd and that just sits at a spinney cursor with no signs of any progress :( Any advice? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 00:24:29 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 6ADE8106567D; Thu, 3 Nov 2011 00:24:29 +0000 (UTC) Date: Thu, 3 Nov 2011 00:24:29 +0000 From: Alexander Best To: Daniel Kalchev Message-ID: <20111103002429.GA66126@freebsd.org> References: <20111102131311.GA56941@icarus.home.lan> <4EB1476A.3070204@digsys.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EB1476A.3070204@digsys.bg> Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 00:24:29 -0000 On Wed Nov 2 11, Daniel Kalchev wrote: > > > On 02.11.11 15:13, Jeremy Chadwick wrote: > >On Wed, Nov 02, 2011 at 12:57:33PM +0100, Borja Marcos wrote: > >>Today I?ve come across an issue long ago forgotten :) Running out of > >>i-nodes. > >[...] > > > >There's a reason /usr on FreeBSD defaults to "all the remaining space on > >the disk" if you pick the defaults/auto. Surprise. :-) > > > >The summarised version is: > > > >1. You have control over this yourself: newfs(8) -i flag. You can even > >input this flag during sysinstall when building a new system. > > > >[...] > > Just for the completeness of it, one would use ZFS and be done with this > issue. :-) 'boot -s && fsck_ufs -r /dev/ufs/whatever' might also be helpful. cheers. alex > > That would be point 0. in my personal list of suggestions. All the rest > would be "if you have good reason to not use ZFS". > > Daniel From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 09:41:36 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03CC2106566C for ; Thu, 3 Nov 2011 09:41:36 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop03.sare.net (proxypop03.sare.net [194.30.0.207]) by mx1.freebsd.org (Postfix) with ESMTP id 99B3D8FC13 for ; Thu, 3 Nov 2011 09:41:35 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id BEF779DC520; Thu, 3 Nov 2011 10:41:33 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20111102131311.GA56941@icarus.home.lan> Date: Thu, 3 Nov 2011 10:41:30 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <32C5CE2F-8C1C-442E-A1B4-9DD9FD47C691@sarenet.es> References: <20111102131311.GA56941@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 09:41:36 -0000 On Nov 2, 2011, at 2:13 PM, Jeremy Chadwick wrote: > On Wed, Nov 02, 2011 at 12:57:33PM +0100, Borja Marcos wrote: >> Today I?ve come across an issue long ago forgotten :) Running out of = i-nodes. >=20 > The last time I dealt with this was about 3 months ago, on a Netapp > filer; hardly forgotten. :-) >=20 >> The condition was triggered on a 8 GB /usr filesystem which includes = the ports tree, on which I have compiled several ports and their = dependencies. I know, maybe not the best practices, it's a machine = being used to test a couple of thingies, but I wonder how many newbies = can run into such a problem. I guess many. >>=20 >> Filesystem 1K-blocks Used Avail Capacity = iused ifree %iused Mounted on >> /dev/ad1s1e 8245660 5308960 2277048 70% 507099 61219 = 89% /usr >>=20 >> Now i-nodes aren't completely full, as I have deleted /usr/obj (turns = out I had made a make world as well). >>=20 >> Looking at the number of i-nodes per /usr subdirectory, I have = noticed that, wow! /usr/ports consumes A LOT of them.=20 >>=20 >> freebsd9-borja# find . -print | wc -l >> 405481 >=20 > "find -x /usr/ports | wc -l" on my system returns 146420. My find was on /usr/ports after having compiled the mentioned ports. = It's using so many inodes after compiling the mentioned ports. > Your 8GB filesystem is only ~21% the capacity of mine. So if we do = some > simple math, your /usr should really be showing (assuming yours is as > "bare bones" as mine) around 26% inodes used. Yet what you have is = 89%. >=20 > You probably just have a lot of other software on /usr that "abuses" > lots of individual files. You list off what ports you built from > source, which means you have lots of "build cruft" laying around en > masse (work/ directories). Yes, of course, I am aware of that. But a = mother-of-all-stuff-and-not-too-large /usr filesystem can create = problems if you build plenty of ports. The issue is: given that tasks such as port building now consume = inordinate amounts of inodes, is the current default value reasonable? = This is an issue on which I can imagine a newbie having problems, hence = my suggestion to increase the default number. > Really? That isn't what the default installer does (re: single > filesystem), and hasn't since... well, as long as I can remember > (2.2.8). Sorry, I'm wrong on that. > I wouldn't recommend a /usr/ports filesystem. It solves nothing. > Imagine: /usr/ports can now run out of inodes while /usr won't. What > would this address? It would decrease impact to applications creating > new files on /usr. How often do you have that happening on your = system? > For me it's extremely rare. For comparison, /var gets a lot more > activity. Yes, but there are ports that use /usr as far as I know. Anyway, it = would be an issue if the user is just building ports. > Adding a /usr/ports filesystem also provides zero scalability. = Meaning: > say someone decides "8GB for /usr/ports is enough" during the = installer > and so on. Then down the road, we run out of space, or inodes, or > whatever else. Oops, what now? Symlinks all over the place? Yeah, = not > going to happen. Good point.=20 > We were already in this boat regarding the root filesystem size, which > for quite some time defaulted to 512MBytes, which was not enough. > Today, the default size is 1GBytes, which is enough for a kernel built > with debugging symbols and so on, but tends to reach ~55-58% used. >=20 > There's a reason /usr on FreeBSD defaults to "all the remaining space = on > the disk" if you pick the defaults/auto. Surprise. :-) >=20 > The summarised version is: >=20 > 1. You have control over this yourself: newfs(8) -i flag. You can = even > input this flag during sysinstall when building a new system. >=20 > 2. When you built the system, you chose to assume /usr should be = 8GBytes. > Your usage habits may have changed, software gotten larger, etc.. It > may be time for you to re-evaluate how you create your filesystems and > what sizes you choose. You chose something that didn't scale. :-) I'm not complaining about the issue, I know well I have to clean up, = etc. Been using FreeBSD since 2.0.5 ;) But I'm wondering if it could be an issue to others. And the /usr was small because I need a lot of room for /var.=20 > 4. For a limited-space (not just size but inodes!) filesystem, = consider > using packages (pkg_add -r) for anything that does not require > customisation during the build/configure phase. For example, for = quite > some time now on my systems, I've always installed the package = versions > of perl, python27, cmake, gettext, pcre, etc. solely because they are > "key softwares" that I hate building from source. Unfortunately there are several key ports that *do* need compile time = customization. Moreover, I could be wrong, as I've been compiling ports = for many, many years, but do we have a mechanism to document which = compile-time options were used to build a package? I'm not aware of it. Just a suggestion anyway. The calculation for the default number of = inodes was right many years ago, in my opinion the number is too low = nowadays. And yes, I know this isn't an issue with ZFS, been using it for a long = time as well. But FFS is still very widely used. Borja. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 11:22:05 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB8C1106564A; Thu, 3 Nov 2011 11:22:05 +0000 (UTC) (envelope-from Karli.Sjoberg@slu.se) Received: from Edge1-3.slu.se (edge1-3.slu.se [193.10.100.98]) by mx1.freebsd.org (Postfix) with ESMTP id AE9F18FC18; Thu, 3 Nov 2011 11:22:04 +0000 (UTC) Received: from Exchange2.ad.slu.se (193.10.100.95) by Edge1-3.slu.se (193.10.100.98) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 3 Nov 2011 12:22:01 +0100 Received: from exmbx3.ad.slu.se ([193.10.100.93]) by Exchange2.ad.slu.se ([193.10.100.95]) with mapi; Thu, 3 Nov 2011 12:22:01 +0100 From: =?iso-8859-1?Q?Karli_Sj=F6berg?= To: "Kenneth D. Merry" Date: Thu, 3 Nov 2011 12:21:59 +0100 Thread-Topic: AOC-USAS2-L8i zfs panics and SCSI errors in messages Thread-Index: AcyaGs4yiVLBqLRGSh6I0qMEfXlyoQ== Message-ID: <666756B5-218E-48D6-99A7-56C7FB0D2E33@slu.se> References: <82B38DBF-DD3A-46CD-93F6-02CDB6506E05@slu.se> <20111025193302.GA30409@nargothrond.kdm.org> In-Reply-To: <20111025193302.GA30409@nargothrond.kdm.org> Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: sv-SE, en-US MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-scsi@freebsd.org" , "fs@freebsd.org" Subject: Re: AOC-USAS2-L8i zfs panics and SCSI errors in messages X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 11:22:05 -0000 Hi, I=B4m not alone! By complete chance I was reading another thread on the forum and it turns o= ut that peetaur also has the exact same problem as me with timeouts and som= etimes losing disks. His hardware is very different from mine, except that = we both have LSI controllers and are running 8.2-STABLE. He has tried both = the mps-driver in FreeBSD and the mps-driver that LSI provides (phase 11), = and still gets these timeouts. peetaur=B4s system: 4HE Chassis from Supermicro 847E16-R1400LPB with 2 1400 Watt red. power and 36x HotSwap for SAS or SATA Motherboard from Supermicro - Intel=AE 5520 (Tylersburg) Chipset - 12 DIMM memory slots (max. 192GB DDR3) - 2x 100/1000Base TX Gigabit Ethernet Port (Dual Intel=AE 82576 Gigabit Eth= ernet) - 6x SATA (3 Gbps) Ports via ICH10R Controller - PCI Slots: 7x (x8) PCI-E 2.0 (in x16 slots) - Integrated IPMI 2.0 with Dedicated LAN - Integrated Matrox G200eW Graphics CPU - 2x E5620 Intel Xeon (Westmere) Quad Core CPU, (80W) 2,40 GHz, 12 MB L3 Ca= che RAM - 48 GB (6x 8GB) DDR3 1333 DIMM, REG, ECC SAS HBA - 9211-8i Network - 10G Card with Dual-port Intel=AE 82598EB (CX4) Disks - 9x HDD 3TB SATA from Hitachi, 7.2k UPM, 64 MB Cache - 9x HDD 3TB SATA from Seagate, 7.2k UPM, 64 MB Cache - 2x consumer SSDs (boot, root, zil, cache) #uname -a FreeBSD bcnas1.bc.local 8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Sep 29 15:06:= 03 CEST 2011 root@bcnas1.bc.local:/usr/obj/usr/src/sys/GENERIC amd64 and a extract from /var/log/messages when using FreeBSD=B4s mps: Oct 4 08:57:05 bcnas1 kernel: (da3:mps0:0:0:0): SCSI command timeout on de= vice handle 0x000a SMID 568 Oct 4 08:57:05 bcnas1 kernel: (da3:mps0:0:0:0): SCSI command timeout on de= vice handle 0x000a SMID 998 Oct 4 08:57:13 bcnas1 kernel: mps0: (0:0:0) terminated ioc 804b scsi 0 sta= te c xfer 0 Oct 4 08:57:13 bcnas1 kernel: mps0: mpssas_abort_complete: abort request o= n handle 0x0a SMID 568 complete Oct 4 08:57:13 bcnas1 kernel: mps0: mpssas_complete_tm_request: sending de= ferred task management request for handle 0x0a SMID 998 Oct 4 08:57:13 bcnas1 kernel: mps0: mpssas_abort_complete: abort request o= n handle 0x0a SMID 998 complete Oct 4 08:58:13 bcnas1 kernel: (da3:mps0:0:0:0): SCSI command timeout on de= vice handle 0x000a SMID 973 Oct 4 08:58:13 bcnas1 kernel: (da3:mps0:0:0:0): SCSI command timeout on de= vice handle 0x000a SMID 981 Oct 4 08:58:21 bcnas1 kernel: mps0: (0:0:0) terminated ioc 804b scsi 0 sta= te c xfer 0 Oct 4 08:58:21 bcnas1 kernel: mps0: mpssas_abort_complete: abort request o= n handle 0x0a SMID 973 complete Oct 4 08:58:21 bcnas1 kernel: mps0: mpssas_complete_tm_request: sending de= ferred task management request for handle 0x0a SMID 981 Oct 4 08:58:21 bcnas1 kernel: mps0: mpssas_abort_complete: abort request o= n handle 0x0a SMID 981 complete Oct 4 08:58:24 bcnas1 kernel: (da3:mps0:0:0:0): READ(6). CDB: 8 0 0 0 80 0 Oct 4 08:58:24 bcnas1 kernel: (da3:mps0:0:0:0): CAM status: SCSI Status Er= ror Oct 4 08:58:24 bcnas1 kernel: (da3:mps0:0:0:0): SCSI status: Check Conditi= on Oct 4 08:58:24 bcnas1 kernel: (da3:mps0:0:0:0): SCSI sense: UNIT ATTENTION= asc:29,0 (Power on, reset, or bus device reset occurred) Oct 4 09:00:14 bcnas1 kernel: mps0: mpssas_remove_complete on target 0x000= 0, IOCStatus=3D 0x0 Oct 4 09:00:14 bcnas1 kernel: (da3:mps0:0:0:0): lost device and a extract from /var/log/messages when using LSI=B4s mps: Nov 3 09:17:10 bcnas1bak kernel: mpslsi0: mpssas_scsiio_timeout checking s= c 0xffffff800f629000 cm 0xffffff800f65f698 Nov 3 09:17:10 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 6 2c 0 da 0 0 0 0 0 4f 0 c2 0 b0 0 length 0 SMID 717 c= ommand timeout cm 0xffffff800f65f698 ccb 0xffffff0026bbb800 Nov 3 09:17:10 bcnas1bak kernel: mpslsi0: mpssas_alloc_tm freezing simq Nov 3 09:17:10 bcnas1bak kernel: mpslsi0: timedout cm 0xffffff800f65f698 a= llocated tm 0xffffff800f6340f8 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 2c f3 be e2 0 0 2a 0 length 21504 SMID 261 completed cm 0xffffff800f643cd8= ccb 0xffffff0026bd1000 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 2c f3 be e2 0 0 2a 0 length 21504 SMID 261 terminated ioc 804b scsi 0 stat= e c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 52 1e 2 e3 0 0 2b 0 length 22016 SMID 534 completed cm 0xffffff800f654550 = ccb 0xffffff0026b96000 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 52 1e 2 e3 0 0 2b 0 length 22016 SMID 534 terminated ioc 804b scsi 0 state= c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 3a 5 14 a3 0 0 2b 0 length 22016 SMID 798 completed cm 0xffffff800f664510 = ccb 0xffffff003d438000 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 3a 5 14 a3 0 0 2b 0 length 22016 SMID 798 terminated ioc 804b scsi 0 state= c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 39 81 86 6f 0 0 2b 0 length 22016 SMID 590 completed cm 0xffffff800f657b90= ccb 0xffffff00314ce800 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 39 81 86 6f 0 0 2b 0 length 22016 SMID 590 terminated ioc 804b scsi 0 stat= e c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 39 47 e8 2c 0 0 2a 0 length 21504 SMID 634 completed cm 0xffffff800f65a630= ccb 0xffffff0026ba1800 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 39 47 e8 2c 0 0 2a 0 length 21504 SMID 634 terminated ioc 804b scsi 0 stat= e c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 2d 8b 96 af 0 0 2b 0 length 22016 SMID 707 completed cm 0xffffff800f65ece8= ccb 0xffffff0026bb1800 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 2d 8b 96 af 0 0 2b 0 length 22016 SMID 707 terminated ioc 804b scsi 0 stat= e c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 6 2c 0 da 0 0 0 0 0 4f 0 c2 0 b0 0 length 0 SMID 717 c= ompleted timedout cm 0xffffff800f65f698 ccb 0xffffff0026bbb800 during recov= (da0:mpslsi0:0:10:0): R$ Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 1c dc 68 73 0 0 2b 0 length 22016 SMID 690 terminated ioc 804b scsi 0 stat= e c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 58 d da 33 0 0 2b 0 length 22016 SMID 947 completed cm 0xffffff800f66d568 = ccb 0xffffff0026bf9000 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 58 d da 33 0 0 2b 0 length 22016 SMID 947 terminated ioc 804b scsi 0 state= c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 4b 30 d1 80 0 0 2a 0 length 21504 SMID 683 completed cm 0xffffff800f65d5a8= ccb 0xffffff003d47f800 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 4b 30 d1 80 0 0 2a 0 length 21504 SMID 683 terminated ioc 804b scsi 0 stat= e c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 4a d 10 d0 0 0 2b 0 length 22016 SMID 219 completed cm 0xffffff800f641428 = ccb 0xffffff0031536000 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 4a d 10 d0 0 0 2b 0 length 22016 SMID 219 terminated ioc 804b scsi 0 state= c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 41 1e 9a 58 0 0 2a 0 length 21504 SMID 169 completed cm 0xffffff800f63e3b8= ccb 0xffffff00314ec800 during recovery ioc 804b scsi 0 state c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 41 1e 9a 58 0 0 2a 0 length 21504 SMID 169 terminated ioc 804b scsi 0 stat= e c xfer 0 Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 8 e 0 d0 0 1 0 0 0 4f 0 c2 0 b0 0 length 512 SMID 139 = completed cm 0xffffff800f63c6a8 ccb 0xffffff0026a89000 during recovery ioc = (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 6 2c 0 da 0 0 0 0 0 4f 0 c2 0 b0 0 length 0 SMID 876 c= ompleted cm 0xffffff800f6690a0 ccb 0xffffff00314c8800 during recovery ioc 8= (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 8 e 0 d5 0 1 0 6 0 4f 0 c2 0 b0 0 length 512 SMID 661 = completed cm 0xffffff800f65c058 ccb 0xffffff0026b7d000 during recovery ioc = (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 8 e 0 d5 0 1 0 6 0 4f 0 c2 0 b0 0 length 512 SMID 471 = completed cm 0xffffff800f650848 ccb 0xffffff0026be7800 during recovery ioc = (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 8 e 0 d0 0 1 0 0 0 4f 0 c2 0 b0 0 length 512 SMID 215 = completed cm 0xffffff800f641048 ccb 0xffffff0026bef800 during recovery ioc = (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 8 e 0 d5 0 1 0 6 0 4f 0 c2 0 b0 0 length 512 SMID 203 = completed cm 0xffffff800f6404a8 ccb 0xffffff0026bb6000 during recovery ioc = (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 8 e 0 d0 0 1 0 0 0 4f 0 c2 0 b0 0 length 512 SMID 546 = completed cm 0xffffff800f6550f0 ccb 0xffffff003d447800 during recovery ioc = (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (pass0:mpslsi0:0:10:0): ATA COMMAND PASS = THROUGH(16). CDB: 85 8 e 0 d5 0 1 0 6 0 4f 0 c2 0 b0 0 length 512 SMID 513 = completed cm 0xffffff800f6530f8 ccb 0xffffff0026bcb800 during recovery ioc = (pass0:mpslsi0:0:10:0):$ Nov 3 09:17:11 bcnas1bak kernel: (noperiph:mpslsi0:0:10:0): SMID 1 abort T= askMID 717 status 0x0 code 0x0 count 20 Nov 3 09:17:11 bcnas1bak kernel: (noperiph:mpslsi0:0:10:0): SMID 1 finishe= d recovery after aborting TaskMID 717 Nov 3 09:17:11 bcnas1bak kernel: mpslsi0: mpssas_free_tm releasing simq Nov 3 09:17:17 bcnas1bak kernel: (da0:mpslsi0:0:10:0): READ(10). CDB: 28 0= 41 1e 9a 58 0 0 2a 0 Nov 3 09:17:17 bcnas1bak kernel: (da0:mpslsi0:0:10:0): CAM status: SCSI St= atus Error Nov 3 09:17:17 bcnas1bak kernel: (da0:mpslsi0:0:10:0): SCSI status: Check = Condition Nov 3 09:17:17 bcnas1bak kernel: (da0:mpslsi0:0:10:0): SCSI sense: UNIT AT= TENTION asc:29,0 (Power on, reset, or bus device reset occurred) /Karli 25 okt 2011 kl. 21.33 skrev Kenneth D. Merry: On Thu, Oct 20, 2011 at 13:28:17 +0200, Karli Sj?berg wrote: Hi, I?m in the process of vacating a Sun/Oracle system to a another Supermicro/= FreeBSD system, doing zfs send/recv between. Two times now, the system has = panicked while not doing anything at all, and it?s throwing alot of SCSI/CA= M-related errors while doing IO-intensive operations, like send/recv, resil= ver, and zpool has sometimes reported read/write errors on the hard drives.= Best part is that the errors in messages are about all hard drives at one = time or another, and they are connected with separate cables, controllers a= nd caddies. Specs: HW: 1x Supermicro X8SIL-F 2x Supermicro AOC-USAS2-L8i 2x Supermicro CSE-M35T-1B 1x Intel Core i5 650 3,2GHz 4x 2GB 1333MHZ DDR3 ECC UDIMM 10x SAMSUNG HD204UI (in a raidz2 zpool) 1x OCZ Vertex 3 240GB (L2ARC) SW: # uname -a FreeBSD server 8.2-STABLE FreeBSD 8.2-STABLE #0: Mon Oct 10 09:12:25 UTC 20= 11 root@server:/usr/obj/usr/src/sys/GENERIC amd64 # zpool get version pool1 NAME PROPERTY VALUE SOURCE pool1 version 28 default[/CODE] I got the panic from the IPMI KVM: http://i55.tinypic.com/synpzk.png In looking at the panic, this is a ZFS panic. Nothing the disks do should be able to cause ZFS to panic. ZFS is panicing in avl_add(): /* * This is unfortunate. We want to call panic() here, even for * non-DEBUG kernels. In userland, however, we can't depend on anything * in libc or else the rtld build process gets confused. So, all we can * do in userland is resort to a normal ASSERT(). */ if (avl_find(tree, new_node, &where) !=3D NULL) #ifdef _KERNEL panic("avl_find() succeeded inside avl_add()"); #else ASSERT(0); #endif There are certainly timeouts and two terminated IOCs in the log below. Tha= t does suggest a hardware or driver problem, but it isn't very obvious what it might be. I have seen bad behavior with SATA drives behind 3Gb Maxim expanders talking to 6GB LSI controllers, but your particular configuration does not involve any expanders, and therefore is not that particular STP issue. My best guess, and it is a guess, is that either the drives are misbehaving (i.e. firmware type problem) or you've got a cabling issue. If you have more hardware available, you might try swapping out the cables and/or drives to see if you can reproduce the drive errors with a different setup. If you swap the drives, I would use a different brand if you've got them available. I'm CCing the fs list, perhaps someone there can look at the stack trace above and figure out what ZFS might be doing. Again, ZFS should survive any errors from the drives, and the panic above looks like ZFS is flagging a logic bug somewhere. And an extract from /var/log/messages: Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): WRITE(10). CDB: 2a 0 6 13 6= 6 f 0 0 f 0 Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): CAM status: SCSI Status Err= or Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): SCSI status: Check Conditio= n Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): SCSI sense: UNIT ATTENTION = asc:29,0 (Power on, reset, or bus device reset occurred) Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): WRITE(6). CDB: a 0 1 b2 2 0 Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): CAM status: SCSI Status Err= or Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): SCSI status: Check Conditio= n Oct 19 17:37:19 fs2-7 kernel: (da6:mps1:0:0:0): SCSI sense: UNIT ATTENTION = asc:29,0 (Power on, reset, or bus device reset occurred) Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI command timeout on dev= ice handle 0x000c SMID 859 Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI command timeout on dev= ice handle 0x000c SMID 495 Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI command timeout on dev= ice handle 0x000c SMID 725 Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI command timeout on dev= ice handle 0x000c SMID 722 Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI command timeout on dev= ice handle 0x000c SMID 438 Oct 19 17:40:38 fs2-7 kernel: mps1: (1:4:0) terminated ioc 804b scsi 0 stat= e c xfer 0 Oct 19 17:40:38 fs2-7 last message repeated 3 times Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_abort_complete: abort request on= handle 0x0c SMID 859 complete Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_complete_tm_request: sending def= erred task management request for handle 0x0c SMID 495 Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_abort_complete: abort request on= handle 0x0c SMID 495 complete Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_complete_tm_request: sending def= erred task management request for handle 0x0c SMID 725 Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_abort_complete: abort request on= handle 0x0c SMID 725 complete Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_complete_tm_request: sending def= erred task management request for handle 0x0c SMID 722 Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_abort_complete: abort request on= handle 0x0c SMID 722 complete Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_complete_tm_request: sending def= erred task management request for handle 0x0c SMID 438 Oct 19 17:40:38 fs2-7 kernel: mps1: mpssas_abort_complete: abort request on= handle 0x0c SMID 438 complete Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): WRITE(10). CDB: 2a 0 6 25 4= f 75 0 0 b 0 Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): CAM status: SCSI Status Err= or Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI status: Check Conditio= n Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI sense: UNIT ATTENTION = asc:29,0 (Power on, reset, or bus device reset occurred) Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): WRITE(10). CDB: 2a 0 2d a5 = 10 ca 0 0 80 0 Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): CAM status: SCSI Status Err= or Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI status: Check Conditio= n Oct 19 17:40:38 fs2-7 kernel: (da9:mps1:0:4:0): SCSI sense: UNIT ATTENTION = asc:29,0 (Power on, reset, or bus device reset occurred) Oct 19 17:45:40 fs2-7 kernel: (da1:mps0:0:1:0): SCSI command timeout on dev= ice handle 0x000a SMID 976 Oct 19 17:45:41 fs2-7 kernel: (da1:mps0:0:1:0): SCSI command timeout on dev= ice handle 0x000a SMID 636 Oct 19 17:45:41 fs2-7 kernel: (da1:mps0:0:1:0): SCSI command timeout on dev= ice handle 0x000a SMID 888 Oct 19 17:45:41 fs2-7 kernel: (da1:mps0:0:1:0): SCSI command timeout on dev= ice handle 0x000a SMID 983 Oct 19 17:45:41 fs2-7 kernel: mps0: (0:1:0) terminated ioc 804b scsi 0 stat= e c xfer 0 Oct 19 17:45:41 fs2-7 last message repeated 2 times Oct 19 17:45:41 fs2-7 kernel: mps0: mpssas_abort_complete: abort request on= handle 0x0a SMID 976 complete Oct 19 17:45:41 fs2-7 kernel: mps0: mpssas_complete_tm_request: sending def= erred task management request for handle 0x0a SMID 636 Oct 19 17:45:41 fs2-7 kernel: mps0: mpssas_abort_complete: abort request on= handle 0x0a SMID 636 complete Oct 19 17:45:41 fs2-7 kernel: mps0: mpssas_complete_tm_request: sending def= erred task management request for handle 0x0a SMID 888 Oct 19 17:45:41 fs2-7 kernel: mps0: mpssas_abort_complete: abort request on= handle 0x0a SMID 888 complete Oct 19 17:45:41 fs2-7 kernel: mps0: mpssas_complete_tm_request: sending def= erred task management request for handle 0x0a SMID 983 Oct 19 17:45:41 fs2-7 kernel: mps0: mpssas_abort_complete: abort request on= handle 0x0a SMID 983 complete Oct 19 17:45:41 fs2-7 kernel: (da1:mps0:0:1:0): WRITE(10). CDB: 2a 0 6 40 a= 7 2 0 0 3 0 Oct 19 17:45:41 fs2-7 kernel: (da1:mps0:0:1:0): CAM status: SCSI Status Err= or Oct 19 17:45:41 fs2-7 kernel: (da1:mps0:0:1:0): SCSI status: Check Conditio= n Oct 19 17:45:41 fs2-7 kernel: (da1:mps0:0:1:0): SCSI sense: UNIT ATTENTION = asc:29,0 (Power on, reset, or bus device reset occurred) Oct 19 17:45:42 fs2-7 kernel: (da1:mps0:0:1:0): WRITE(10). CDB: 2a 0 6 40 b= 0 9 0 0 9 0 Oct 19 17:45:42 fs2-7 kernel: (da1:mps0:0:1:0): CAM status: SCSI Status Err= or Oct 19 17:45:42 fs2-7 kernel: (da1:mps0:0:1:0): SCSI status: Check Conditio= n Oct 19 17:45:42 fs2-7 kernel: (da1:mps0:0:1:0): SCSI sense: UNIT ATTENTION = asc:29,0 (Power on, reset, or bus device reset occurred) What?s going on? Regards Karli Sj?berg_______________________________________________ freebsd-scsi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-scsi To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" Ken -- Kenneth Merry ken@FreeBSD.ORG Med V=E4nliga H=E4lsningar ---------------------------------------------------------------------------= ---- Karli Sj=F6berg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kron=E5sv=E4gen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg@slu.se From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 12:44:18 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17EDF106564A for ; Thu, 3 Nov 2011 12:44:18 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id C2AE38FC08 for ; Thu, 3 Nov 2011 12:44:17 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RLweV-00083L-2o for freebsd-fs@freebsd.org; Thu, 03 Nov 2011 13:44:15 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Nov 2011 13:44:15 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Nov 2011 13:44:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Thu, 03 Nov 2011 13:43:58 +0100 Lines: 45 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDE943E0C91F6804A6A260F63" X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111004 Thunderbird/7.0.1 In-Reply-To: X-Enigmail-Version: 1.1.2 Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 12:44:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDE943E0C91F6804A6A260F63 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 02/11/2011 12:57, Borja Marcos wrote: >=20 > Hi >=20 > Today I=C2=B4ve come across an issue long ago forgotten :) Running out = of i-nodes. Actually, nowadays I mostly *reduce* the number of inodes rather than increasing it, since I often have large files and want to reduce fsck time (but that's a corner case). > Looking at the number of i-nodes per /usr subdirectory, I have noticed = that, wow! /usr/ports consumes A LOT of them.=20 >=20 > freebsd9-borja# find . -print | wc -l > 405481 Did you forget to do "make clean" after "make install" on several large ports? But yes, the ports tree is getting a bit unwieldy. On the other hand, did you fsck the file system lately? --------------enigDE943E0C91F6804A6A260F63 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6yjI4ACgkQldnAQVacBcgwFQCgzZaYjuDXmhphJXDTPd5zc6GD 3wUAn3v+6IPYYppjlSt61dP65q86Gu+b =2uRS -----END PGP SIGNATURE----- --------------enigDE943E0C91F6804A6A260F63-- From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 12:50:12 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8445C1065679 for ; Thu, 3 Nov 2011 12:50:12 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3DB0D8FC16 for ; Thu, 3 Nov 2011 12:50:12 +0000 (UTC) Received: by vcbfo14 with SMTP id fo14so181779vcb.13 for ; Thu, 03 Nov 2011 05:50:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type:content-transfer-encoding; bh=M1LGmtrqng6fBHw9SXpjb35cxZv/MW3wRkdw28fpSNI=; b=ksGRD8z24oUUThcI8UbrMkFZo58TWXcvjzzN9d7jKF8hIQmoQCRmNwxiCPEnRaG4Wf OBC1dvyx/ppTz8yKlsY+wZRm3AEQb1pTRUlTrCt4ST+RZtOr6b7ZCN9+4o0GzFlA2yoI 2tDCUmpagufZr4BTiHxgvB+6lMnt8N3hOD5Zw= MIME-Version: 1.0 Received: by 10.52.174.115 with SMTP id br19mr9381062vdc.130.1320324611575; Thu, 03 Nov 2011 05:50:11 -0700 (PDT) Received: by 10.52.182.40 with HTTP; Thu, 3 Nov 2011 05:50:11 -0700 (PDT) In-Reply-To: References: Date: Thu, 3 Nov 2011 12:50:11 +0000 Message-ID: From: Tom Evans Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 12:50:12 -0000 On Thu, Nov 3, 2011 at 12:43 PM, Ivan Voras wrote: > On 02/11/2011 12:57, Borja Marcos wrote: >> >> Hi >> >> Today I=C2=B4ve come across an issue long ago forgotten :) Running out o= f i-nodes. > > Actually, nowadays I mostly *reduce* the number of inodes rather than > increasing it, since I often have large files and want to reduce fsck > time (but that's a corner case). > >> Looking at the number of i-nodes per /usr subdirectory, I have noticed t= hat, wow! /usr/ports consumes A LOT of them. >> >> freebsd9-borja# =C2=A0 =C2=A0 =C2=A0 find . -print | wc -l >> =C2=A0 405481 > > Did you forget to do "make clean" after "make install" on several large > ports? > > But yes, the ports tree is getting a bit unwieldy. On the other hand, > did you fsck the file system lately? > If building directly, you can put all this in one line: make all install clean or if reinstalling: make all deinstall reinstall clean Or you can just use portupgrade/portmaster - portupgrade certainly always cleans the work directories, I'm sure portmaster does as well. Cheers Tom From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 15:27:36 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 760FB1065672 for ; Thu, 3 Nov 2011 15:27:36 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (dauterive.egr.msu.edu [35.9.37.168]) by mx1.freebsd.org (Postfix) with ESMTP id 494038FC14 for ; Thu, 3 Nov 2011 15:27:35 +0000 (UTC) Received: from dauterive (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 5253B77F15 for ; Thu, 3 Nov 2011 11:08:13 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by dauterive (dauterive.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uvLj42UBrqLI for ; Thu, 3 Nov 2011 11:08:13 -0400 (EDT) Received: from [35.9.44.65] (daemon.egr.msu.edu [35.9.44.65]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mail.egr.msu.edu (Postfix) with ESMTPSA id 2E01877F0F for ; Thu, 3 Nov 2011 11:08:13 -0400 (EDT) Message-ID: <4EB2AE5D.5040206@egr.msu.edu> Date: Thu, 03 Nov 2011 11:08:13 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111004 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20111102131311.GA56941@icarus.home.lan> <32C5CE2F-8C1C-442E-A1B4-9DD9FD47C691@sarenet.es> In-Reply-To: <32C5CE2F-8C1C-442E-A1B4-9DD9FD47C691@sarenet.es> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 15:27:36 -0000 On 11/03/11 05:41, Borja Marcos wrote: > > And the /usr was small because I need a lot of room for /var. The way you've described the issue sounds like it concerns mainly just ports, so perhaps a ports-specific adjustment like below is appropriate and an easy solution for any admin with sufficient inodes available on a partition of their choosing? I am concerned about the drawbacks (performance) of increasing the ratio of inodes on /usr just to accommodate an optional and somewhat flexible component. I've been setting this for many years now even when it is not a space concern on /usr, it keeps my /usr/ports tree clean and puts all the "junk" in a location I can easily clean out: WRKDIRPREFIX=/var/tmp/ports From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 16:46:28 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C50CF1065753 for ; Thu, 3 Nov 2011 16:46:28 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8DEA38FC08 for ; Thu, 3 Nov 2011 16:46:28 +0000 (UTC) Received: by iabz21 with SMTP id z21so2513643iab.13 for ; Thu, 03 Nov 2011 09:46:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s7EvQNkTeIQ7/Agp3Wyn1pvn0GNUiyhoE7h5ytrf3w0=; b=LLS4uL9Ez27IcrwCBBEf5CunxjQs0S4vEiOWosLvY1Z2r7JYZ1EVLvn1JjqtaE7i0p 4MqwYsn+EtcoWPb09tIWM+ea4sc4ZANev6DPpmYYYXXZGUk665RUX0rANRcQaY2MvS+q oZfYYI5PeW68FB/HPfzmKUXjPQtMe4kTOal1Q= MIME-Version: 1.0 Received: by 10.231.48.203 with SMTP id s11mr2132534ibf.90.1320338787901; Thu, 03 Nov 2011 09:46:27 -0700 (PDT) Received: by 10.231.11.140 with HTTP; Thu, 3 Nov 2011 09:46:27 -0700 (PDT) Received: by 10.231.11.140 with HTTP; Thu, 3 Nov 2011 09:46:27 -0700 (PDT) In-Reply-To: <4EB2AE5D.5040206@egr.msu.edu> References: <20111102131311.GA56941@icarus.home.lan> <32C5CE2F-8C1C-442E-A1B4-9DD9FD47C691@sarenet.es> <4EB2AE5D.5040206@egr.msu.edu> Date: Thu, 3 Nov 2011 16:46:27 +0000 Message-ID: From: Chris Rees To: Adam McDougall Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 16:46:29 -0000 On 3 Nov 2011 15:27, "Adam McDougall" wrote: > > On 11/03/11 05:41, Borja Marcos wrote: >> >> >> And the /usr was small because I need a lot of room for /var. > > > The way you've described the issue sounds like it concerns mainly just ports, so perhaps a ports-specific adjustment like below is appropriate and an easy solution for any admin with sufficient inodes available on a partition of their choosing? I am concerned about the drawbacks (performance) of increasing the ratio of inodes on /usr just to accommodate an optional and somewhat flexible component. > > I've been setting this for many years now even when it is not a space concern on /usr, it keeps my /usr/ports tree clean and puts all the "junk" in a location I can easily clean out: > > WRKDIRPREFIX=/var/tmp/ports > ... but then you need a bigger than default /var... Personally I use /usr/obj and occasionally nuke it (I know we're running out of inode on /usr, but rm should solve that problem). Chris Chris From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 17:09:10 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AC6C106566C for ; Thu, 3 Nov 2011 17:09:10 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2CAA18FC17 for ; Thu, 3 Nov 2011 17:09:09 +0000 (UTC) Received: by wyg36 with SMTP id 36so1992339wyg.13 for ; Thu, 03 Nov 2011 10:09:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=JGUcn0AS3a0leL9YB72WLWkqMtxNQrwhiSUK2SrWKkc=; b=BlQL+ZtShU8a3bLzWkNbNvGq8LWsXGtbSu+EeKZVJa+ssvYd2s5B5pvFUcInKPIDni ci/JS5KRB0IJYfmzfKuNBL6pIVWbeBwno28/qCiUS0PbPCpJf3TSsuUflcJc3gUGaapf fcy3cuGsds95w8wYQbc9Ks02gsyTj8s0SNOtc= Received: by 10.216.180.8 with SMTP id i8mr3107684wem.26.1320339651146; Thu, 03 Nov 2011 10:00:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.2.199 with HTTP; Thu, 3 Nov 2011 10:00:20 -0700 (PDT) In-Reply-To: References: <20111102131311.GA56941@icarus.home.lan> <32C5CE2F-8C1C-442E-A1B4-9DD9FD47C691@sarenet.es> <4EB2AE5D.5040206@egr.msu.edu> From: Eitan Adler Date: Thu, 3 Nov 2011 13:00:20 -0400 Message-ID: To: Chris Rees Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 17:09:10 -0000 On Thu, Nov 3, 2011 at 12:46 PM, Chris Rees wrote: > On 3 Nov 2011 15:27, "Adam McDougall" wrote: >> >> On 11/03/11 05:41, Borja Marcos wrote: >>> >>> >>> And the /usr was small because I need a lot of room for /var. >> >> >> The way you've described the issue sounds like it concerns mainly just > ports, so perhaps a ports-specific adjustment like below is appropriate a= nd > an easy solution for any admin with sufficient inodes available on a > partition of their choosing? =C2=A0I am concerned about the drawbacks > (performance) of increasing the ratio of inodes on /usr just to accommoda= te > an optional and somewhat flexible component. >> >> I've been setting this for many years now even when it is not a space > concern on /usr, it keeps my /usr/ports tree clean and puts all the "junk= " > in a location I can easily clean out: >> >> WRKDIRPREFIX=3D/var/tmp/ports >> > > ... but then you need a bigger than default /var... > > Personally I use /usr/obj and occasionally nuke it (I know we're running > out of inode on /usr, but rm should solve that problem). A dedicated "WRKDIRPREFIX" mdfs can also help. --=20 Eitan Adler From owner-freebsd-fs@FreeBSD.ORG Thu Nov 3 20:10:44 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BCAA106566C; Thu, 3 Nov 2011 20:10:44 +0000 (UTC) (envelope-from bsd@xerq.net) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3030A8FC2B; Thu, 3 Nov 2011 20:10:43 +0000 (UTC) Received: by iabz21 with SMTP id z21so2798812iab.13 for ; Thu, 03 Nov 2011 13:10:43 -0700 (PDT) Received: by 10.42.147.72 with SMTP id m8mr10590020icv.56.1320349527291; Thu, 03 Nov 2011 12:45:27 -0700 (PDT) Received: from [10.142.3.1] (cv86.chapman.edu. [206.211.150.86]) by mx.google.com with ESMTPS id e2sm12046291ibe.0.2011.11.03.12.45.24 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Nov 2011 12:45:26 -0700 (PDT) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Message-Id: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> X-Mailer: iPhone Mail (9A334) From: Matt Connor Date: Thu, 3 Nov 2011 12:45:20 -0700 To: Ivan Voras Cc: "freebsd-fs@freebsd.org" Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 20:10:44 -0000 On Nov 3, 2011, at 5:43 AM, Ivan Voras wrote: > On 02/11/2011 12:57, Borja Marcos wrote: >>=20 >> Hi >>=20 >> Today I=C2=B4ve come across an issue long ago forgotten :) Running out of= i-nodes. >=20 > Actually, nowadays I mostly *reduce* the number of inodes rather than > increasing it, since I often have large files and want to reduce fsck > time (but that's a corner case). >=20 >> Looking at the number of i-nodes per /usr subdirectory, I have noticed th= at, wow! /usr/ports consumes A LOT of them.=20 >>=20 >> freebsd9-borja# find . -print | wc -l >> 405481 >=20 > Did you forget to do "make clean" after "make install" on several large > ports? >=20 > But yes, the ports tree is getting a bit unwieldy. On the other hand, > did you fsck the file system lately? >=20 >=20 cd /usr/ports/ports-mgmt/portupgrade && make install clean portsclean -CD That's a quick way to clean out all the clutter. -Matt= From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 11:02:26 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 827A3106566B; Fri, 4 Nov 2011 11:02:26 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 410EF8FC0A; Fri, 4 Nov 2011 11:02:26 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id EB9C128455; Fri, 4 Nov 2011 12:02:24 +0100 (CET) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 380B128453; Fri, 4 Nov 2011 12:02:24 +0100 (CET) Message-ID: <4EB3C63F.2060805@quip.cz> Date: Fri, 04 Nov 2011 12:02:23 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Matt Connor References: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> In-Reply-To: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-fs@freebsd.org" , Ivan Voras Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 11:02:26 -0000 Matt Connor wrote: > > On Nov 3, 2011, at 5:43 AM, Ivan Voras wrote: > >> On 02/11/2011 12:57, Borja Marcos wrote: [...] >> Did you forget to do "make clean" after "make install" on several large >> ports? >> >> But yes, the ports tree is getting a bit unwieldy. On the other hand, >> did you fsck the file system lately? >> > > cd /usr/ports/ports-mgmt/portupgrade&& make install clean > > portsclean -CD > > That's a quick way to clean out all the clutter. Installing ruby and portupgrade is really big overhead to simple task, which can be done by: cd /usr/ports && make clean or with find: find /usr/ports/ -depth 3 -name "work" -exec rm -r {} + Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 13:58:50 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id DA231106566C; Fri, 4 Nov 2011 13:58:50 +0000 (UTC) Date: Fri, 4 Nov 2011 13:58:50 +0000 From: Alexander Best To: freebsd-fs@freebsd.org Message-ID: <20111104135850.GA25559@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: tmpfs(5) speeds X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 13:58:50 -0000 hi there, using 'time dd if=/dev/zero of=/tmp/test bs=1m count=500' i got a result of: 500+0 records in 500+0 records out 524288000 bytes transferred in 1.133749 secs (462437450 bytes/sec) dd if=/dev/zero of=/tmp/test bs=1m count=500 0,00s user 1,33s system 99% cpu 1,332 total isn't this a bit slow? i've seen people get speeds of 2 gigabytes/sec running striped SSDs as fs backend. the RAM i'm using is 2x1GB DDR2 non-ECC memory 800MHZ (PC2-6400) and CL4 (4-4-4-12). http://en.wikipedia.org/wiki/DDR2_SDRAM shows a peek 6400 megabyte/sec. i'm running HEAD on amd64. cheers. alex From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 14:16:26 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 7288B1065670; Fri, 4 Nov 2011 14:16:26 +0000 (UTC) Date: Fri, 4 Nov 2011 14:16:26 +0000 From: Alexander Best To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20111104141626.GA28925@freebsd.org> References: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> <4EB3C63F.2060805@quip.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EB3C63F.2060805@quip.cz> Cc: "freebsd-fs@freebsd.org" , Ivan Voras Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 14:16:26 -0000 On Fri Nov 4 11, Miroslav Lachman wrote: > Matt Connor wrote: > > > >On Nov 3, 2011, at 5:43 AM, Ivan Voras wrote: > > > >>On 02/11/2011 12:57, Borja Marcos wrote: > > [...] > > >>Did you forget to do "make clean" after "make install" on several large > >>ports? > >> > >>But yes, the ports tree is getting a bit unwieldy. On the other hand, > >>did you fsck the file system lately? > >> > > > >cd /usr/ports/ports-mgmt/portupgrade&& make install clean > > > >portsclean -CD > > > >That's a quick way to clean out all the clutter. > > Installing ruby and portupgrade is really big overhead to simple task, > which can be done by: > > cd /usr/ports && make clean > > or with find: > > find /usr/ports/ -depth 3 -name "work" -exec rm -r {} + ...or with 'rm -rf /usr/ports/*/*/work' cheers. alex > > Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 15:29:42 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FA3C1065670; Fri, 4 Nov 2011 15:29:42 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 200218FC15; Fri, 4 Nov 2011 15:29:41 +0000 (UTC) Received: by iabz21 with SMTP id z21so4265276iab.13 for ; Fri, 04 Nov 2011 08:29:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=fQMsJioytpYNbYAJsoACei+rbHBWt1qBH4p4PmVIsNg=; b=Aty6Axr+86wst5u7qGECdAXWkoFdBmJHTlpf2DA7iREqetrnTGPXKwrE3JA/AUIR6T ozn1QmUclYHIqOacum0+ApVcoiuZ5InSWmd5MZ4iKS9VsCgpu0+PiTDAFNc3Ia7OSG7w euXUx9TvC4KOpTFbFwqq07S+faJjXQrEoS5E4= Received: by 10.231.82.11 with SMTP id z11mr3701979ibk.77.1320420581218; Fri, 04 Nov 2011 08:29:41 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.11.140 with HTTP; Fri, 4 Nov 2011 08:29:10 -0700 (PDT) In-Reply-To: <20111104141626.GA28925@freebsd.org> References: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> <4EB3C63F.2060805@quip.cz> <20111104141626.GA28925@freebsd.org> From: Chris Rees Date: Fri, 4 Nov 2011 15:29:10 +0000 X-Google-Sender-Auth: RTXpo4CEkNCMWQdJEgZ6w-96-M4 Message-ID: To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-fs@freebsd.org" , Ivan Voras Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 15:29:42 -0000 On 4 November 2011 14:16, Alexander Best wrote: > On Fri Nov =A04 11, Miroslav Lachman wrote: >> Matt Connor wrote: >> > >> >On Nov 3, 2011, at 5:43 AM, Ivan Voras =A0wrote: >> > >> >>On 02/11/2011 12:57, Borja Marcos wrote: >> >> [...] >> >> >>Did you forget to do "make clean" after "make install" on several larg= e >> >>ports? >> >> >> >>But yes, the ports tree is getting a bit unwieldy. On the other hand, >> >>did you fsck the file system lately? >> >> >> > >> >cd /usr/ports/ports-mgmt/portupgrade&& =A0make install clean >> > >> >portsclean -CD >> > >> >That's a quick way to clean out all the clutter. >> >> Installing ruby and portupgrade is really big overhead to simple task, >> which can be done by: >> >> cd /usr/ports && make clean >> >> or with find: >> >> find /usr/ports/ -depth 3 -name "work" -exec rm -r {} + > > ...or with 'rm -rf /usr/ports/*/*/work' > I almost had the strength of mind to stay out of this.... BUT you could well run into argument list too long issues there (considering the insane number of inodes used), so you're probably better off getting around that using the builtin echo: # echo /usr/ports/*/*/work | xargs rm -r Since you're doing stuff like that, find is probably more appropriate. Chris From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 16:04:21 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 67A471065672; Fri, 4 Nov 2011 16:04:21 +0000 (UTC) Date: Fri, 4 Nov 2011 16:04:21 +0000 From: Alexander Best To: Chris Rees Message-ID: <20111104160421.GA43288@freebsd.org> References: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> <4EB3C63F.2060805@quip.cz> <20111104141626.GA28925@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: "freebsd-fs@freebsd.org" , Ivan Voras Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 16:04:21 -0000 On Fri Nov 4 11, Chris Rees wrote: > On 4 November 2011 14:16, Alexander Best wrote: > > On Fri Nov  4 11, Miroslav Lachman wrote: > >> Matt Connor wrote: > >> > > >> >On Nov 3, 2011, at 5:43 AM, Ivan Voras  wrote: > >> > > >> >>On 02/11/2011 12:57, Borja Marcos wrote: > >> > >> [...] > >> > >> >>Did you forget to do "make clean" after "make install" on several large > >> >>ports? > >> >> > >> >>But yes, the ports tree is getting a bit unwieldy. On the other hand, > >> >>did you fsck the file system lately? > >> >> > >> > > >> >cd /usr/ports/ports-mgmt/portupgrade&&  make install clean > >> > > >> >portsclean -CD > >> > > >> >That's a quick way to clean out all the clutter. > >> > >> Installing ruby and portupgrade is really big overhead to simple task, > >> which can be done by: > >> > >> cd /usr/ports && make clean > >> > >> or with find: > >> > >> find /usr/ports/ -depth 3 -name "work" -exec rm -r {} + > > > > ...or with 'rm -rf /usr/ports/*/*/work' > > > > I almost had the strength of mind to stay out of this.... > > BUT you could well run into argument list too long issues there > (considering the insane number of inodes used), so you're probably > better off getting around that using the builtin echo: > > # echo /usr/ports/*/*/work | xargs rm -r right i forgot about long argument lists. will -prune speed up the above find(1) command invocation? cheers. alex > > Since you're doing stuff like that, find is probably more appropriate. > > Chris From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 16:50:04 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26CC9106566B for ; Fri, 4 Nov 2011 16:50:04 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id C85C58FC12 for ; Fri, 4 Nov 2011 16:50:03 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id B09CA861; Fri, 4 Nov 2011 17:50:00 +0100 (CET) Date: Fri, 4 Nov 2011 17:49:12 +0100 From: Pawel Jakub Dawidek To: Steven Hartland Message-ID: <20111104164911.GA1684@garage.freebsd.pl> References: <3BA4142083B3413E86CB874A37154749@multiplay.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <3BA4142083B3413E86CB874A37154749@multiplay.co.uk> X-OS: FreeBSD 9.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.ORG Subject: Re: booting of large raidz2 fails - all block copies unavailable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 16:50:04 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 02, 2011 at 07:32:19PM -0000, Steven Hartland wrote: > Just installed a machine using mfsbsd 8.2-RELEASE with raidz2 across > 14 x 3TB Disks but boot fails with the following at the boot loader:- > ZFS: i/o error - all block copies unavailable=20 >=20 > There seems to have been several threads on this in the past but > all seem to have been resolved a long time ago. >=20 > I tried 9.0rc1 mfsbsd and that just sits at a spinney cursor with > no signs of any progress :( >=20 > Any advice? Yes, there were plenty of fixes in ZFS boot code in HEAD. They are not in 9.0-RC1 and not yet in 9-STABLE. Could you try those: http://people.freebsd.org/~pjd/zfsboot/ You need to copy zfsloader to /boot/ directory of your root dataset and install gptzfsboot using gpart(8). --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk60F4cACgkQForvXbEpPzQ3ZQCfaugSCTtz2abzaGheUvz9GKPU AccAoOov3vgM6q41HAnS8D5w834TCrHh =vS5L -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 16:52:57 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6C01106566C; Fri, 4 Nov 2011 16:52:57 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 28D618FC18; Fri, 4 Nov 2011 16:52:56 +0000 (UTC) Received: by qadb12 with SMTP id b12so1133967qad.13 for ; Fri, 04 Nov 2011 09:52:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vjR+RLH+93vLLxqvkgk6gNPterPt2U1NEeIMGHNSops=; b=vqAw3tznrLWv3U4GElbwgAV2idTnmx2n+mvu0+2HWA1pom8Ytn/oWih8WFmcI2azWt LdfAqNdlBaZTcrpbpGLmsMdRF4n1ScLddy0OxVZMyooqr9QBSlJzH045D7xz+ccGNS9M mUS0g/6cgCNmZA++8ShDtKvP0rrUXcNmxcux0= MIME-Version: 1.0 Received: by 10.50.170.105 with SMTP id al9mr13296710igc.28.1320425575400; Fri, 04 Nov 2011 09:52:55 -0700 (PDT) Sender: utisoft@gmail.com Received: by 10.231.11.140 with HTTP; Fri, 4 Nov 2011 09:52:55 -0700 (PDT) Received: by 10.231.11.140 with HTTP; Fri, 4 Nov 2011 09:52:55 -0700 (PDT) In-Reply-To: <20111104160421.GA43288@freebsd.org> References: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> <4EB3C63F.2060805@quip.cz> <20111104141626.GA28925@freebsd.org> <20111104160421.GA43288@freebsd.org> Date: Fri, 4 Nov 2011 16:52:55 +0000 X-Google-Sender-Auth: aU7IUfTb-ZcBxWbaOjQK02EYA5U Message-ID: From: Chris Rees To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-fs@freebsd.org" , Ivan Voras Subject: Re: Default inode number too low in FFS nowadays? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 16:52:57 -0000 On 4 Nov 2011 16:05, "Alexander Best" wrote: > > On Fri Nov 4 11, Chris Rees wrote: > > On 4 November 2011 14:16, Alexander Best wrote: > > > On Fri Nov 4 11, Miroslav Lachman wrote: > > >> Matt Connor wrote: > > >> > > > >> >On Nov 3, 2011, at 5:43 AM, Ivan Voras wrote: > > >> > > > >> >>On 02/11/2011 12:57, Borja Marcos wrote: > > >> > > >> [...] > > >> > > >> >>Did you forget to do "make clean" after "make install" on several large > > >> >>ports? > > >> >> > > >> >>But yes, the ports tree is getting a bit unwieldy. On the other hand, > > >> >>did you fsck the file system lately? > > >> >> > > >> > > > >> >cd /usr/ports/ports-mgmt/portupgrade&& make install clean > > >> > > > >> >portsclean -CD > > >> > > > >> >That's a quick way to clean out all the clutter. > > >> > > >> Installing ruby and portupgrade is really big overhead to simple task, > > >> which can be done by: > > >> > > >> cd /usr/ports && make clean > > >> > > >> or with find: > > >> > > >> find /usr/ports/ -depth 3 -name "work" -exec rm -r {} + > > > > > > ...or with 'rm -rf /usr/ports/*/*/work' > > > > > > > I almost had the strength of mind to stay out of this.... > > > > BUT you could well run into argument list too long issues there > > (considering the insane number of inodes used), so you're probably > > better off getting around that using the builtin echo: > > > > # echo /usr/ports/*/*/work | xargs rm -r > > right i forgot about long argument lists. will -prune speed up the above > find(1) command invocation? > > cheers. > alex > -depth 3 deals with that. Chris From owner-freebsd-fs@FreeBSD.ORG Fri Nov 4 23:20:11 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF4861065674 for ; Fri, 4 Nov 2011 23:20:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AEB898FC15 for ; Fri, 4 Nov 2011 23:20:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pA4NKBW6036600 for ; Fri, 4 Nov 2011 23:20:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pA4NKBXv036599; Fri, 4 Nov 2011 23:20:11 GMT (envelope-from gnats) Date: Fri, 4 Nov 2011 23:20:11 GMT Message-Id: <201111042320.pA4NKBXv036599@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Robert Millan Cc: Subject: Re: kern/162008: [zfs] Latest 9-STABLE and 10-CURRENT fail to boot from ZFS v15 root [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Millan List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2011 23:20:11 -0000 The following reply was made to PR kern/162008; it has been noted by GNATS. From: Robert Millan To: Andriy Gapon Cc: bug-followup@freebsd.org Subject: Re: kern/162008: [zfs] Latest 9-STABLE and 10-CURRENT fail to boot from ZFS v15 root [regression] Date: Sat, 5 Nov 2011 00:11:34 +0100 2011/10/30 Andriy Gapon : > IMO, not likely. > Please try setting vfs.zfs.debug=1 via loader.conf. > Maybe additional debug information will make the situation clearer. Strangely, the system boots now, but kernel panics as soon as "zfs volinit" is attempted: vdev_geom_open_by_guid:352[1]: Searching by guid [13849114725133984793]. panic: _sx_xlock_hard: recursed on non-recursive sx spa_namespace_lock @ /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zvol.c:877 It also drops me to a debug prompt. Backtrace: kdb_enter panic _sx_xlock_hard _sx_xlock zvol_geom_access g_access vdev_geom_open vdev_open vdev_open_children vdev_root_open vdev_open spa_load spa_load_best spa_open_common spa_get_stats zfs_ioc_pool_stats zfsdev_ioctl devfs_ioctl_f kern_ioctl (this happened with 9-STABLE, SVN r226626) -- Robert Millan From owner-freebsd-fs@FreeBSD.ORG Sat Nov 5 07:01:45 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3ED5106566C for ; Sat, 5 Nov 2011 07:01:45 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id C5E508FC0A for ; Sat, 5 Nov 2011 07:01:45 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 7B59250834 for ; Fri, 4 Nov 2011 23:46:39 -0700 (PDT) To: freebsd-fs@freebsd.org Date: Fri, 04 Nov 2011 23:46:39 -0700 Message-ID: <60946.1320475599@tristatelogic.com> From: "Ronald F. Guilmette" Subject: write access to various times X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2011 07:01:46 -0000 Greetings, It would appear that in 8.2-RELEASE, at least, each "struct stat" contains four fields, each of type "timespec", and having the following names: st_atimespec st_mtimespec st_ctimespec st_birthtimespec I already know that if I want to modify either (or both) of the first two fields listed above, I should call utimes(2). But what do I do if I need to modify the values of either or both of the other two fields? (I may want to do this, e.g. if I am trying to restore all of the struct stat fields from a backed-up representation of some original filesystem entry.) The current man page for utimes(2) says (among other things): =========================================================================== ... If times is non-NULL, it is assumed to point to an array of two timeval structures. The access time is set to the value of the first element, and the modification time is set to the value of the second element. For file systems that support file birth (creation) times (such as UFS2), the birth time will be set to the value of the second element if the second element is older than the currently set birth time. To set both a birth time and a modification time, two calls are required; the first to set the birth time and the second to set the (presumably newer) modification time. Ideally a new system call will be added that allows the setting of all three times at once... =========================================================================== Is there any ETA for this postulated new system call? It would be most helpful to have that. Also, of course, although the method described above for setting the value of the st_birthtimespec field is rather clumsey and inefficient, at least there _is_ a way to set that field. I am concerned however because I personally still know of no way whatsoever to set the value of the st_ctimespec field. Is there any way to do that? It would be most helpful to have that too. Regards, rfg From owner-freebsd-fs@FreeBSD.ORG Sat Nov 5 16:30:23 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28214106566B; Sat, 5 Nov 2011 16:30:23 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F42308FC15; Sat, 5 Nov 2011 16:30:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pA5GUMIQ029894; Sat, 5 Nov 2011 16:30:22 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pA5GUMHd029882; Sat, 5 Nov 2011 16:30:22 GMT (envelope-from pjd) Date: Sat, 5 Nov 2011 16:30:22 GMT Message-Id: <201111051630.pA5GUMHd029882@freefall.freebsd.org> To: rmh@debian.org, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/162008: [zfs] Latest 9-STABLE and 10-CURRENT fail to boot from ZFS v15 root [regression] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2011 16:30:23 -0000 Synopsis: [zfs] Latest 9-STABLE and 10-CURRENT fail to boot from ZFS v15 root [regression] State-Changed-From-To: open->patched State-Changed-By: pjd State-Changed-When: sob 5 lis 2011 16:29:46 UTC State-Changed-Why: Fix committed to HEAD. Thanks for the report! Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: sob 5 lis 2011 16:29:46 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=162008