From owner-freebsd-fs@FreeBSD.ORG Sun Nov 12 22:47:43 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C960B16A40F for ; Sun, 12 Nov 2006 22:47:43 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6816743D66 for ; Sun, 12 Nov 2006 22:47:42 +0000 (GMT) (envelope-from r.c.ladan@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so806335uge for ; Sun, 12 Nov 2006 14:47:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:x-enigmail-version:content-type:content-transfer-encoding; b=QaQo55vVtvPMabSFH3h3VVry1JFKpen9r2o0+mZQM9sflv8h3jQCMpWupg4TVYEle4TPTtTIOLzoqFH5gyqjfTilrqONxIMAai2nf0Pi5xv+aRdqfocnVKMOU++UPl48nawCyM13/apmSaXWbnF6QqRuJQCBTgDfklbkr13nwZU= Received: by 10.66.242.19 with SMTP id p19mr7084254ugh.1163371661337; Sun, 12 Nov 2006 14:47:41 -0800 (PST) Received: from ?192.168.123.106? ( [195.241.221.201]) by mx.google.com with ESMTP id s7sm5574187uge.2006.11.12.14.47.40; Sun, 12 Nov 2006 14:47:41 -0800 (PST) Message-ID: <4557A48B.4080605@gmail.com> Date: Sun, 12 Nov 2006 23:47:39 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.7 (X11/20061018) MIME-Version: 1.0 To: freebsd-fs@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: xtaf-r6-20061112 available 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, 12 Nov 2006 22:47:43 -0000 Hi, I've uploaded a new version of the XTAF (XBox 360 fs) code at http://home.tiscali.nl/rladan/freebsd/xtaf-r6-20061112.diff.bz2 The code now patch(1)es against /usr/src, no further actions are needed as in the previous version. It compiles on RELENG_6 2006-11-12, it probably fails on CURRENT. Read support should be fairly complete. Some hard disk issues may be remaining, but memory cards should be supported unless I made a mistake somewhere. I haven't really looked into write support yet. The biggest todo right now is to connect the code with the code which creates /dev/da?s? (geom?) . Both memory cards and hard disks have multiple slices. The start/size information is not stored on the devices, but in the XBox 360 kernel, so we have to duplicate it here. For memory cards (64MB) : start size info 0x0 0x7ff,000 XTAF, 16 bits, system cache 0x7ff,000 0x3,621,000 XTAF, 16 bits, user area For hard disks (20GB) : start size info 0x0 0x80,000 hard disk header 0x80,000 0x80,000,000 XTAF, 16 bits, system cache 0x80,080,000 0xA0,E30,000 unused, filled with 00 0x120,eb0,000 0x10,000,000 XTAF, 16 bits, XBox 1 compatibility 0x130,eb0,000 0x377,680,000 XTAF, 32 bits, user area I haven't yet looked at the new 256MB memory cards (goto shop). There are also rumors about larger hard disks, ranging from 60GB to 200GB. Other todos: write support, hard disk header support Could some locking / fs guru could sanity check the code? That would speed up runtime testing of the code. Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 From owner-freebsd-fs@FreeBSD.ORG Mon Nov 13 15:20:38 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF70516A53F for ; Mon, 13 Nov 2006 15:20:38 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3FDB43FF9 for ; Mon, 13 Nov 2006 15:05:43 +0000 (GMT) (envelope-from freebsd-fs@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1GjdMs-0004c7-LD for freebsd-fs@freebsd.org; Mon, 13 Nov 2006 16:05:02 +0100 Received: from firewall.andxor.it ([195.223.2.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Nov 2006 16:05:02 +0100 Received: from lapo by firewall.andxor.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Nov 2006 16:05:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Lapo Luchini Date: Mon, 13 Nov 2006 14:55:44 +0000 (UTC) Lines: 80 Message-ID: References: <854C78DB-2099-4DA5-9E3B-F30D6947C532@jlauser.net> <4512F957.2090205@centtech.com> <20060922041535.GF4842@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 195.223.2.2 (Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1) Gecko/20061106 Firefox/2.0) Sender: news Subject: Re: Snapshot corruption on 6.1/amd64 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, 13 Nov 2006 15:20:39 -0000 Kostik Belousov gmail.com> writes: > > >After some searching, I've found a bug report filed last year that > > >describes this problem exactly, though the log of that report does > > >not suggest that anything has been done with it. That report is at > > >http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90512 > > James, look at the PR/100365. Supposed fix is MFCed. Original reporter > said that this changed nothing for him. I have not much time lately to > look at this problem, but would like to get additional data points. > > BTW, use of snapshots with stock 6.1 is not very attractive idea, better > to update to the 6-STABLE (many important fixes in that area were made). I had a problem with snapshots too, and I also use amd64. The description of neither PR seem to match my case: I compiled 6.1-STABLE at the beginning of September and activated snapshots on the whole /usr FS and had no problems until the beginning of October, when: Oct 22 04:00:33 motoko root: snapshot: daily.0 snapshot on filesystem / made (duration: 0 min) Oct 22 04:03:29 motoko root: snapshot: daily.0 snapshot on filesystem /usr made (duration: 2 min) Oct 22 04:03:47 motoko root: snapshot: daily.0 snapshot on filesystem /var made (duration: 0 min) [machine manually reset] Oct 23 11:09:21 motoko syslogd: kernel boot file is /boot/kernel/kernel Oct 23 11:09:21 motoko kernel: Copyright (c) 1992-2006 The FreeBSD Project. [...] Oct 23 11:11:02 motoko fsck: /dev/ad0s1e: 4449 files, 118197 used, 135618 free (8882 frags, 15842 blocks, 3.5% fragmentation) Oct 23 11:11:18 motoko fsck: /dev/ad0s1d: UNREF FILE I=23564 OWNER=operator MODE=100400 [...many more...] Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: UNREF FILE I=212299 OWNER=www MODE=100600 Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: SIZE=2048 MTIME=Oct 1 15:57 2006 (CLEARED) Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: Reclaimed: 0 directories, 1991 files, 1832 fragments Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: 18768 files, 83120 used, 915663 free ( 6839 frags, 113603 blocks, 0.7% fragmentation) Oct 23 11:13:49 motoko ntpd[670]: kernel time sync disabled 2041 Oct 23 11:21:10 motoko syslogd: kernel boot file is /boot/kernel/kernel Oct 23 11:21:10 motoko kernel: panic: snapblkfree: inconsistent block type Oct 23 11:21:10 motoko kernel: Uptime: 20m38s Oct 23 11:21:10 motoko kernel: Cannot dump. No dump device defined. Oct 23 11:21:10 motoko kernel: Automatic reboot in 15 seconds - press a key on the console to abort Oct 23 11:21:10 motoko kernel: Copyright (c) 1992-2006 The FreeBSD Project. And after this the box kinda looped 27 times { fsck; panic; reset; } until it finally crashed for good. I then decided to stop taking new snapshots and activate a dump device, but after a few days a new problem was there: Dump header from device /dev/ad0s1b Architecture: amd64 Architecture Version: 2 Dump Length: 1056505856B (1007 MB) Blocksize: 512 Dumptime: Fri Nov 3 04:25:36 2006 Hostname: motoko.lapo.it Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-STABLE #4: Fri Sep 1 17:02:50 CEST 2006 root@motoko.lapo.it:/usr/obj/usr/src/sys/MOTOKO Panic String: snapacct_ufs2: bad block Dump Parity: 2648692799 Bounds: 1 Dump Status: good I solved this removing any existing snapshot, but at this time I had accumulated enough downtime and frustration (and angry users) not to want to try snapshots anymore unless I had some strong impression the problem could really have been solved, which kinda explains why I noticed this thread... the obvious question is: may this problem be resolved by PR/100365 (seems quite different to me, but I don't know the internals...) or is it a new thing? I have the dump file, for the latest problem. From owner-freebsd-fs@FreeBSD.ORG Mon Nov 13 15:35:18 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F27816A500 for ; Mon, 13 Nov 2006 15:35:18 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90BED43D70 for ; Mon, 13 Nov 2006 15:35:13 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kADFZ6d9030096; Mon, 13 Nov 2006 09:35:07 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <455890AE.9050807@centtech.com> Date: Mon, 13 Nov 2006 09:35:10 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Lapo Luchini References: <854C78DB-2099-4DA5-9E3B-F30D6947C532@jlauser.net> <4512F957.2090205@centtech.com> <20060922041535.GF4842@deviant.kiev.zoral.com.ua> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2190/Mon Nov 13 03:31:57 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: Snapshot corruption on 6.1/amd64 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, 13 Nov 2006 15:35:18 -0000 On 11/13/06 08:55, Lapo Luchini wrote: > Kostik Belousov gmail.com> writes: > >>>> After some searching, I've found a bug report filed last year that >>>> describes this problem exactly, though the log of that report does >>>> not suggest that anything has been done with it. That report is at >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90512 >> James, look at the PR/100365. Supposed fix is MFCed. Original reporter >> said that this changed nothing for him. I have not much time lately to >> look at this problem, but would like to get additional data points. >> >> BTW, use of snapshots with stock 6.1 is not very attractive idea, better >> to update to the 6-STABLE (many important fixes in that area were made). > > I had a problem with snapshots too, and I also use amd64. > The description of neither PR seem to match my case: I compiled 6.1-STABLE at > the beginning of September and activated snapshots on the whole /usr FS and had > no problems until the beginning of October, when: > > Oct 22 04:00:33 motoko root: snapshot: daily.0 snapshot on filesystem / made > (duration: 0 min) > Oct 22 04:03:29 motoko root: snapshot: daily.0 snapshot on filesystem /usr made > (duration: 2 min) > Oct 22 04:03:47 motoko root: snapshot: daily.0 snapshot on filesystem /var made > (duration: 0 min) > [machine manually reset] > Oct 23 11:09:21 motoko syslogd: kernel boot file is /boot/kernel/kernel > Oct 23 11:09:21 motoko kernel: Copyright (c) 1992-2006 The FreeBSD Project. > [...] > Oct 23 11:11:02 motoko fsck: /dev/ad0s1e: 4449 files, 118197 used, 135618 free > (8882 frags, 15842 blocks, 3.5% fragmentation) > Oct 23 11:11:18 motoko fsck: /dev/ad0s1d: UNREF FILE I=23564 OWNER=operator > MODE=100400 > [...many more...] > Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: UNREF FILE I=212299 OWNER=www > MODE=100600 > Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: SIZE=2048 MTIME=Oct 1 15:57 2006 > (CLEARED) > Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: Reclaimed: 0 directories, 1991 files, > 1832 fragments > Oct 23 11:11:19 motoko fsck: /dev/ad0s1d: 18768 files, 83120 used, 915663 free > ( 6839 frags, 113603 blocks, 0.7% fragmentation) > Oct 23 11:13:49 motoko ntpd[670]: kernel time sync disabled 2041 > Oct 23 11:21:10 motoko syslogd: kernel boot file is /boot/kernel/kernel > Oct 23 11:21:10 motoko kernel: panic: snapblkfree: inconsistent block type > Oct 23 11:21:10 motoko kernel: Uptime: 20m38s > Oct 23 11:21:10 motoko kernel: Cannot dump. No dump device defined. > Oct 23 11:21:10 motoko kernel: Automatic reboot in 15 seconds - press a key on > the console to abort > Oct 23 11:21:10 motoko kernel: Copyright (c) 1992-2006 The FreeBSD Project. > > And after this the box kinda looped 27 times { fsck; panic; reset; } until it > finally crashed for good. > > I then decided to stop taking new snapshots and activate a dump device, but > after a few days a new problem was there: > > Dump header from device /dev/ad0s1b > Architecture: amd64 > Architecture Version: 2 > Dump Length: 1056505856B (1007 MB) > Blocksize: 512 > Dumptime: Fri Nov 3 04:25:36 2006 > Hostname: motoko.lapo.it > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 6.1-STABLE #4: Fri Sep 1 17:02:50 CEST 2006 > root@motoko.lapo.it:/usr/obj/usr/src/sys/MOTOKO > Panic String: snapacct_ufs2: bad block > Dump Parity: 2648692799 > Bounds: 1 > Dump Status: good > > I solved this removing any existing snapshot, but at this time I had accumulated > enough downtime and frustration (and angry users) not to want to try snapshots > anymore unless I had some strong impression the problem could really have been > solved, which kinda explains why I noticed this thread... the obvious question > is: may this problem be resolved by PR/100365 (seems quite different to me, but > I don't know the internals...) or is it a new thing? > > I have the dump file, for the latest problem. Maybe you have a bad disk? You might try swapping the drive out. (just a wild guess here) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Mon Nov 13 22:22:55 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACC4716A49E for ; Mon, 13 Nov 2006 22:22:55 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC2B743D5E for ; Mon, 13 Nov 2006 22:21:38 +0000 (GMT) (envelope-from r.c.ladan@gmail.com) Received: by nf-out-0910.google.com with SMTP id l23so30444nfc for ; Mon, 13 Nov 2006 14:21:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=CrF/xhnPyPxT4RQ/q7CmP/spP2mBVFSnSc/6zcKdIBlm7WHiZz85TCUeJc36RW7N3WkMjNaj6DcUXC9nw4fbaDP5xaTMmrEVWD+HVfEey31mM+hwtHPEFBihc+vF0Ng1/8MCp8gz11qXyi6J4HrhKfUm9n4Db7OeCX8tN6uBnMU= Received: by 10.48.230.18 with SMTP id c18mr148990nfh.1163456494445; Mon, 13 Nov 2006 14:21:34 -0800 (PST) Received: from ?192.168.123.106? ( [195.241.221.201]) by mx.google.com with ESMTP id k9sm242005nfc.2006.11.13.14.21.33; Mon, 13 Nov 2006 14:21:33 -0800 (PST) Message-ID: <4558EFEC.2080402@gmail.com> Date: Mon, 13 Nov 2006 23:21:32 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.8 (X11/20061113) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4557A48B.4080605@gmail.com> In-Reply-To: <4557A48B.4080605@gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: xtaf-r6-20061112 available 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, 13 Nov 2006 22:22:55 -0000 [self- and top-replying >:) ] I've put a slightly corrected version of the patch online at http://home.tiscali.nl/rladan/freebsd/xtaf-r6-20061113.diff.bz2 -rw-r--r-- 1 rene rene 42171 13 nov 22:32 xtaf-r6-20061113.diff.bz2 MD5 (xtaf-r6-20061113.diff.bz2) = 6880eb31124eb7554e7a395b30f7745f It cleans up some orphaned definitions and variables and it preserves the access time of files (XTAF supports this, unlike some ancient FAT versions). Regards, Rene Rene Ladan schreef: > Hi, > > I've uploaded a new version of the XTAF (XBox 360 fs) code at > http://home.tiscali.nl/rladan/freebsd/xtaf-r6-20061112.diff.bz2 > > The code now patch(1)es against /usr/src, no further actions are needed > as in the previous version. It compiles on RELENG_6 2006-11-12, it > probably fails on CURRENT. > > Read support should be fairly complete. Some hard disk issues may be > remaining, but memory cards should be supported unless I made a mistake > somewhere. I haven't really looked into write support yet. > > The biggest todo right now is to connect the code with the code which > creates /dev/da?s? (geom?) . Both memory cards and hard disks have > multiple slices. The start/size information is not stored on the > devices, but in the XBox 360 kernel, so we have to duplicate it here. > > For memory cards (64MB) : > start size info > 0x0 0x7ff,000 XTAF, 16 bits, system cache > 0x7ff,000 0x3,621,000 XTAF, 16 bits, user area > > For hard disks (20GB) : > start size info > 0x0 0x80,000 hard disk header > 0x80,000 0x80,000,000 XTAF, 16 bits, system cache > 0x80,080,000 0xA0,E30,000 unused, filled with 00 > 0x120,eb0,000 0x10,000,000 XTAF, 16 bits, XBox 1 compatibility > 0x130,eb0,000 0x377,680,000 XTAF, 32 bits, user area > > I haven't yet looked at the new 256MB memory cards (goto shop). There > are also rumors about larger hard disks, ranging from 60GB to 200GB. > Other todos: write support, hard disk header support > > Could some locking / fs guru could sanity check the code? That would > speed up runtime testing of the code. > > Regards, > Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 From owner-freebsd-fs@FreeBSD.ORG Tue Nov 14 11:36:42 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D6DD16A416 for ; Tue, 14 Nov 2006 11:36:42 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35C2F43D60 for ; Tue, 14 Nov 2006 11:36:40 +0000 (GMT) (envelope-from r.c.ladan@gmail.com) Received: by nf-out-0910.google.com with SMTP id l23so240246nfc for ; Tue, 14 Nov 2006 03:36:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=CmYTH82LttTy2b0OZTvJ/Z9kzClUDxHvNe1YMo4AeF3MiEc+iS1E1tEOgDrq94+2/Xk0Bk4n4V95XAa2HKyxgVGWKtufNiqT/k3AvvSZSblgPL/WwXomQy8fYKNbGEAhP4jLLQBgBr6VVwaCa65WNsMIG10JKvbKlCTV0RrrBKo= Received: by 10.49.90.4 with SMTP id s4mr981632nfl.1163504199397; Tue, 14 Nov 2006 03:36:39 -0800 (PST) Received: from ?192.168.123.106? ( [195.241.221.201]) by mx.google.com with ESMTP id y24sm1771845nfb.2006.11.14.03.36.38; Tue, 14 Nov 2006 03:36:39 -0800 (PST) Message-ID: <4559AA45.9090402@gmail.com> Date: Tue, 14 Nov 2006 12:36:37 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.8 (X11/20061113) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4557A48B.4080605@gmail.com> <4558EFEC.2080402@gmail.com> In-Reply-To: <4558EFEC.2080402@gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: xtaf-r6-20061112 available 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, 14 Nov 2006 11:36:42 -0000 [again...] Yesterdays patch contained an undeclared variable which I forgot to remove, new patch at http://home.tiscali.nl/rladan/freebsd/xtaf-r6-20061114.diff.bz2 MD5 (xtaf-r6-20061114.diff.bz2) = 7b13c697bcd57241c54c6d8f86dc046d -rw-r--r-- 1 rene rene 42195 14 nov 11:39 xtaf-r6-20061114.diff.bz2 Rene Ladan schreef: > [self- and top-replying >:) ] > > I've put a slightly corrected version of the patch online at > http://home.tiscali.nl/rladan/freebsd/xtaf-r6-20061113.diff.bz2 > > -rw-r--r-- 1 rene rene 42171 13 nov 22:32 xtaf-r6-20061113.diff.bz2 > MD5 (xtaf-r6-20061113.diff.bz2) = 6880eb31124eb7554e7a395b30f7745f > > It cleans up some orphaned definitions and variables and it preserves > the access time of files (XTAF supports this, unlike some ancient FAT > versions). > > Regards, > Rene > -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 From owner-freebsd-fs@FreeBSD.ORG Tue Nov 14 15:10:25 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A38CB16A4E7 for ; Tue, 14 Nov 2006 15:10:25 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33F4243D5F for ; Tue, 14 Nov 2006 15:10:24 +0000 (GMT) (envelope-from dudu@dudu.ro) Received: by nz-out-0102.google.com with SMTP id i11so998257nzh for ; Tue, 14 Nov 2006 07:10:24 -0800 (PST) Received: by 10.65.100.14 with SMTP id c14mr811621qbm.1163517023889; Tue, 14 Nov 2006 07:10:23 -0800 (PST) Received: by 10.65.112.4 with HTTP; Tue, 14 Nov 2006 07:10:23 -0800 (PST) Message-ID: Date: Tue, 14 Nov 2006 17:10:23 +0200 From: "Vlad Galu" To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200610010015.k910F6Ba001594@cwsys.cwsent.com> <45475DEA.2030506@centtech.com> <20061031193139.GA27951@xor.obsecurity.org> Cc: Subject: Re: Frequent VFS crashes with RELENG_6 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, 14 Nov 2006 15:10:25 -0000 On 11/1/06, Vlad Galu wrote: > On 10/31/06, Kris Kennaway wrote: > > On Tue, Oct 31, 2006 at 04:34:59PM +0200, Vlad Galu wrote: > > > > > Yes, but for objective reasons I can't publish it :( > > > The only > > > debugging option that I didn't use was INVARIANTS. > > > > Which is coincidentally the most useful one ;-) > > > > Also turn on DEBUG_LOCKS and DEBUG_VFS_LOCKS then report the output of > > 'show lockedvnods' at the time of crash, as well. Upon Tor Egge's suggestion, I removed ZERO_COPY_SOCKETS from my kernel and the machine has been running nicely ever since. -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-fs@FreeBSD.ORG Tue Nov 14 19:19:44 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9168E16A4C8; Tue, 14 Nov 2006 19:19:44 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62CFF43D5A; Tue, 14 Nov 2006 19:18:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8B7461A3C1C; Tue, 14 Nov 2006 11:17:24 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4C24051341; Tue, 14 Nov 2006 14:17:13 -0500 (EST) Date: Tue, 14 Nov 2006 14:17:13 -0500 From: Kris Kennaway To: Vlad Galu Message-ID: <20061114191713.GA89460@xor.obsecurity.org> References: <200610010015.k910F6Ba001594@cwsys.cwsent.com> <45475DEA.2030506@centtech.com> <20061031193139.GA27951@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Frequent VFS crashes with RELENG_6 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, 14 Nov 2006 19:19:44 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 14, 2006 at 05:10:23PM +0200, Vlad Galu wrote: > On 11/1/06, Vlad Galu wrote: > >On 10/31/06, Kris Kennaway wrote: > >> On Tue, Oct 31, 2006 at 04:34:59PM +0200, Vlad Galu wrote: > >> > >> > Yes, but for objective reasons I can't publish it :( > >> > The only > >> > debugging option that I didn't use was INVARIANTS. > >> > >> Which is coincidentally the most useful one ;-) > >> > >> Also turn on DEBUG_LOCKS and DEBUG_VFS_LOCKS then report the output of > >> 'show lockedvnods' at the time of crash, as well. >=20 > Upon Tor Egge's suggestion, I removed ZERO_COPY_SOCKETS from my > kernel and the machine has been running nicely ever since. Glad to hear it, depending on what Tor had to say you might want to file a PR about that. Kris --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFWhY4Wry0BWjoQKURAn7YAJ41i0lHxAiQQ7tjGPWYKQLlpJxNCgCgvQ4B tJgPSleM5AciNuoseCttNYA= =dL+Q -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- From owner-freebsd-fs@FreeBSD.ORG Wed Nov 15 20:40:11 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33ACB16A4D8 for ; Wed, 15 Nov 2006 20:40:11 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.4.150.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDED143D5F for ; Wed, 15 Nov 2006 20:40:02 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id DDF3B263DD; Wed, 15 Nov 2006 15:39:56 -0500 (EST) Date: Wed, 15 Nov 2006 15:39:56 -0500 (EST) From: Ensel Sharon To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: quota command and rsync snapshots... 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, 15 Nov 2006 20:40:11 -0000 I am currently afraid of UFS2 snapshots (maybe that's rational and maybe it's not ...) and so I am using Mike Rubel style rsync snapshots: rm -rf day.3 mv day.2 day.3 mv day.1 day.2 cp -al day.0 day.1 rsync /source /destination/day.0 (note, GNU cp, the -al means copy everything with hard links) You get the idea. The question is, when I do a `du -ak` of each of the four days (day.0 - day.3) I get roughly the same number for all of them, which is to be expected. However the output of `quota` for that user shows a _much_ larger number than the `du` for each of those directories. I would think that `quota` would show me the sum of day.0 plus (all the total differences of day.1 - day.3) but it shows me a number _much_ larger than that. I really can't even guess what the number it is showing me is. So I have two questions: given a directory that contains one current backup and three snapshots (day.0 - day.4) what command can I run that will show me the total _actual_ space used ? du will not work because it counts up each directory as if it used all of that space... Second, is there any way to get quota to show an accurate representation of the users usage ? Comments ? From owner-freebsd-fs@FreeBSD.ORG Wed Nov 15 20:53:46 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CB8916A47C for ; Wed, 15 Nov 2006 20:53:46 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9050C43DCD for ; Wed, 15 Nov 2006 20:53:14 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kAFKr6ip090645; Wed, 15 Nov 2006 14:53:07 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <455B7E37.9000003@centtech.com> Date: Wed, 15 Nov 2006 14:53:11 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2196/Wed Nov 15 08:16:17 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: quota command and rsync snapshots... 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, 15 Nov 2006 20:53:46 -0000 On 11/15/06 14:39, Ensel Sharon wrote: > I am currently afraid of UFS2 snapshots (maybe that's rational and maybe > it's not ...) and so I am using Mike Rubel style rsync snapshots: > > rm -rf day.3 > mv day.2 day.3 > mv day.1 day.2 > cp -al day.0 day.1 > rsync /source /destination/day.0 > > (note, GNU cp, the -al means copy everything with hard links) > > You get the idea. > > The question is, when I do a `du -ak` of each of the four days (day.0 - > day.3) I get roughly the same number for all of them, which is to be > expected. > > However the output of `quota` for that user shows a _much_ larger number > than the `du` for each of those directories. > > I would think that `quota` would show me the sum of day.0 plus (all the > total differences of day.1 - day.3) but it shows me a number _much_ larger > than that. I really can't even guess what the number it is showing me is. > > So I have two questions: given a directory that contains one current > backup and three snapshots (day.0 - day.4) what command can I run that > will show me the total _actual_ space used ? du will not work because it > counts up each directory as if it used all of that space... Sure it does - you just need to specify either all the directories on the command line, or the top level of the directories. It won't count hard links (assuming that is what you are talking about with the Mike Rubel comment) twice. > Second, is there any way to get quota to show an accurate representation > of the users usage ? It should be accurate - can you send some sample output? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Wed Nov 15 21:14:25 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAEE516A416 for ; Wed, 15 Nov 2006 21:14:24 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB19C43D49 for ; Wed, 15 Nov 2006 21:14:16 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20061115211409m9100em60le>; Wed, 15 Nov 2006 21:14:09 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id kAFLE7AP068532; Wed, 15 Nov 2006 15:14:07 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id kAFLE27e068528; Wed, 15 Nov 2006 15:14:02 -0600 (CST) (envelope-from brooks) Date: Wed, 15 Nov 2006 15:14:01 -0600 From: Brooks Davis To: Ensel Sharon Message-ID: <20061115211401.GA68129@lor.one-eyed-alien.net> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Cc: freebsd-fs@freebsd.org Subject: Re: quota command and rsync snapshots... 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, 15 Nov 2006 21:14:25 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 15, 2006 at 03:39:56PM -0500, Ensel Sharon wrote: >=20 > I am currently afraid of UFS2 snapshots (maybe that's rational and maybe > it's not ...) and so I am using Mike Rubel style rsync snapshots: >=20 > rm -rf day.3 > mv day.2 day.3 > mv day.1 day.2 > cp -al day.0 day.1 > rsync /source /destination/day.0 > > (note, GNU cp, the -al means copy everything with hard links) >=20 > You get the idea. Unless you're using some flags to rsync the symlinks are always being broken... [1:05pm] brooks@host (~/baz): ls -li total 4 32361971 -rw-r--r-- 1 brooks brooks 512 Nov 15 13:04 foo [1:05pm] brooks@host (~/baz): ln foo bar [1:05pm] brooks@host (~/baz): cp foo baz [1:05pm] brooks@host (~/baz): ls -li total 12 32361971 -rw-r--r-- 2 brooks brooks 512 Nov 15 13:04 bar 32361970 -rw-r--r-- 1 brooks brooks 512 Nov 15 13:05 baz 32361971 -rw-r--r-- 2 brooks brooks 512 Nov 15 13:04 foo [1:05pm] brooks@host (~/baz): rsync baz bar [1:06pm] brooks@host (~/baz): ls -li total 12 32361972 -rw-r--r-- 1 brooks brooks 512 Nov 15 13:06 bar 32361970 -rw-r--r-- 1 brooks brooks 512 Nov 15 13:05 baz 32361971 -rw-r--r-- 1 brooks brooks 512 Nov 15 13:04 foo > The question is, when I do a `du -ak` of each of the four days (day.0 - > day.3) I get roughly the same number for all of them, which is to be > expected. >=20 > However the output of `quota` for that user shows a _much_ larger number > than the `du` for each of those directories. >=20 > I would think that `quota` would show me the sum of day.0 plus (all the > total differences of day.1 - day.3) but it shows me a number _much_ larger > than that. I really can't even guess what the number it is showing me is. Quota operates on the filesystem and gives the amount of space used on the volume the directory you pass it is on. > So I have two questions: given a directory that contains one current > backup and three snapshots (day.0 - day.4) what command can I run that > will show me the total _actual_ space used ? du will not work because it > counts up each directory as if it used all of that space... There isn't one that I know of. Unless the volume is only used for this purposed (in which case df could be used) the only way to find this out would be to write a version of du that kept track of the inode of each hardlink and then didn't count it again. > Second, is there any way to get quota to show an accurate representation > of the users usage ? At this point you haven't established that it doesn't. -- Brooks --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFW4MZXY6L6fI4GtQRAmJPAKClciy4bVqfQkie6p9rw9Cs3CVjwQCeJu4V BmrInVhxkgk2+gD6uQ/hPOE= =IF7n -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-fs@FreeBSD.ORG Wed Nov 15 21:23:51 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EEE716A644 for ; Wed, 15 Nov 2006 21:23:51 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.4.150.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8209943D4C for ; Wed, 15 Nov 2006 21:23:49 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id 9687F263D3; Wed, 15 Nov 2006 16:23:42 -0500 (EST) Date: Wed, 15 Nov 2006 16:23:42 -0500 (EST) From: Ensel Sharon To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: quota command and rsync snapshots... 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, 15 Nov 2006 21:23:51 -0000 >> Second, is there any way to get quota to show an accurate representation >> of the users usage ? > It should be accurate - can you send some sample output? Ok, here is what I see (6.1-RELEASE) : First, the output of the quota command for that user: # quota sammy Disk quotas for user sammy (uid 1002): Filesystem usage quota limit grace files quota limit /mnt/big1 197067392 500000000 600000000 1554116 50000000 60000000 So, quota is saying 197 GB used, ~1.5 mil. files. Now looking at the users home directory itself, I see: du -ak /home/sammy | tail -1 197067392 (ok, agrees with quota) find /home/sammy | wc -l 5007486 (5 million ... ?) Now inside of the home directory: day.0 day.1 day.2 day.3 All four of these dirs are size 130 GB (give or take - small differences based on deletions day to day) All four of these dirs have ~1.25 (?) million files in them. Remember, only day.0 is "real" - the others are `cp -al` copies, consisting almost totally of hard links back to day.0. So I really don't know what is going on. quota says 1.5 mil. files, I have 5 million total "files", each dir does not exceed 140 GB. Does this mean that there is (197 minus 140) GB of churn per day, and that there must be (1.5 mil. minus 1.25 mil.) churn of file turnover per day ? Or something like that ? That is the only thing i can think of ... From owner-freebsd-fs@FreeBSD.ORG Wed Nov 15 21:33:53 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B92716A515 for ; Wed, 15 Nov 2006 21:33:53 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87D5C43D73 for ; Wed, 15 Nov 2006 21:33:46 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20061115213345m9200klk5te>; Wed, 15 Nov 2006 21:33:45 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id kAFLXhJr068772; Wed, 15 Nov 2006 15:33:43 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id kAFLXgLt068771; Wed, 15 Nov 2006 15:33:42 -0600 (CST) (envelope-from brooks) Date: Wed, 15 Nov 2006 15:33:42 -0600 From: Brooks Davis To: Ensel Sharon Message-ID: <20061115213342.GB68129@lor.one-eyed-alien.net> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JP+T4n/bALQSJXh8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Cc: freebsd-fs@freebsd.org Subject: Re: quota command and rsync snapshots... 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, 15 Nov 2006 21:33:53 -0000 --JP+T4n/bALQSJXh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 15, 2006 at 04:23:42PM -0500, Ensel Sharon wrote: >=20 > >> Second, is there any way to get quota to show an accurate > representation > >> of the users usage ? >=20 > > It should be accurate - can you send some sample output? >=20 >=20 > Ok, here is what I see (6.1-RELEASE) : >=20 > First, the output of the quota command for that user: >=20 > # quota sammy > Disk quotas for user sammy (uid 1002): > Filesystem usage quota limit grace files quota limit > /mnt/big1 197067392 500000000 600000000 1554116 50000000 60000000 >=20 > So, quota is saying 197 GB used, ~1.5 mil. files. >=20 > Now looking at the users home directory itself, I see: >=20 > du -ak /home/sammy | tail -1 > 197067392 >=20 > (ok, agrees with quota) >=20 > find /home/sammy | wc -l > 5007486 >=20 > (5 million ... ?) >=20 > Now inside of the home directory: >=20 > day.0 day.1 day.2 day.3 >=20 > All four of these dirs are size 130 GB (give or take - small differences > based on deletions day to day) >=20 > All four of these dirs have ~1.25 (?) million files in them. >=20 > Remember, only day.0 is "real" - the others are `cp -al` copies, > consisting almost totally of hard links back to day.0. >=20 >=20 > So I really don't know what is going on. quota says 1.5 mil. files, I > have 5 million total "files", each dir does not exceed 140 GB. quota only counts inodes so the hard links are only counted once. > Does this mean that there is (197 minus 140) GB of churn per day, and that > there must be (1.5 mil. minus 1.25 mil.) churn of file turnover per day > ? Or something like that ? That is the only thing i can think of ... It means that files totaling 57GB are modified over three days. Depending on your work load that may or not be reasonable. Remember that a 1 byte will cause the whole file to count toward the total. -- Brooks --JP+T4n/bALQSJXh8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFW4e2XY6L6fI4GtQRAkJqAJ4juCd3Z28T1cMjzQx265Za6TN7BgCgqdnE Ivs3F6xVhXGo8+Jj5ixjAZY= =6yD0 -----END PGP SIGNATURE----- --JP+T4n/bALQSJXh8-- From owner-freebsd-fs@FreeBSD.ORG Wed Nov 15 21:34:55 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABEB616A715 for ; Wed, 15 Nov 2006 21:34:55 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from customer-domains.icp-qv1-irony11.iinet.net.au (customer-domains.icp-qv1-irony11.iinet.net.au [203.59.1.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267D243D49 for ; Wed, 15 Nov 2006 21:34:45 +0000 (GMT) (envelope-from fbsd-fs@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [127.0.0.1]) ([203.206.173.235]) by customer-domains.icp-qv1-irony11.iinet.net.au with ESMTP; 16 Nov 2006 05:34:44 +0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAALEWW0XLzq3r/2dsb2JhbAAN X-IronPort-AV: i="4.09,425,1157299200"; d="scan'208"; a="34981826:sNHT17190405" Message-ID: <455B87A0.6040604@mawer.org> Date: Thu, 16 Nov 2006 08:33:20 +1100 From: Antony Mawer User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Brooks Davis References: <20061115211401.GA68129@lor.one-eyed-alien.net> In-Reply-To: <20061115211401.GA68129@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Ensel Sharon Subject: Re: quota command and rsync snapshots... 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, 15 Nov 2006 21:34:55 -0000 On 16/11/2006 8:14 AM, Brooks Davis wrote: > On Wed, Nov 15, 2006 at 03:39:56PM -0500, Ensel Sharon wrote: >> So I have two questions: given a directory that contains one current >> backup and three snapshots (day.0 - day.4) what command can I run that >> will show me the total _actual_ space used ? du will not work because it >> counts up each directory as if it used all of that space... > > There isn't one that I know of. Unless the volume is only used for this > purposed (in which case df could be used) the only way to find this out > would be to write a version of du that kept track of the inode of each > hardlink and then didn't count it again. du already does this - for instance, one of our backups snapshots: $ du -h -d1 . 73G ./monthly 190M ./2006-11-06_Mon 198M ./2006-11-07_Tue 14M ./2006-11-08_Wed 19M ./2006-11-09_Thu 11M ./2006-11-10_Fri 9.6M ./2006-11-11_Sat 9.6M ./2006-11-12_Sun 15M ./2006-11-13_Mon 12M ./2006-11-14_Tue 13M ./2006-11-15_Wed 73G . The 'monthly' folder here contains several snapshots (one per month), and then there's the daily snapshots. This magic is all performed by linkchk() in /src/usr.bin/du/du.c. --Antony From owner-freebsd-fs@FreeBSD.ORG Wed Nov 15 21:39:44 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC06916A412 for ; Wed, 15 Nov 2006 21:39:44 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from customer-domains.icp-qv1-irony13.iinet.net.au (customer-domains.icp-qv1-irony13.iinet.net.au [203.59.1.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3AC643D60 for ; Wed, 15 Nov 2006 21:39:43 +0000 (GMT) (envelope-from fbsd-fs@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [127.0.0.1]) ([203.206.173.235]) by customer-domains.icp-qv1-irony13.iinet.net.au with ESMTP; 16 Nov 2006 05:39:41 +0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAALEWW0XLzq3r/2dsb2JhbAAN X-IronPort-AV: i="4.09,425,1157299200"; d="scan'208"; a="20589598:sNHT24939648" Message-ID: <455B88C9.2080000@mawer.org> Date: Thu, 16 Nov 2006 08:38:17 +1100 From: Antony Mawer User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: quota command and rsync snapshots... 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, 15 Nov 2006 21:39:44 -0000 On 16/11/2006 8:23 AM, Ensel Sharon wrote: ... > Remember, only day.0 is "real" - the others are `cp -al` copies, > consisting almost totally of hard links back to day.0. > > So I really don't know what is going on. quota says 1.5 mil. files, I > have 5 million total "files", each dir does not exceed 140 GB. > > Does this mean that there is (197 minus 140) GB of churn per day, and that > there must be (1.5 mil. minus 1.25 mil.) churn of file turnover per day > ? Or something like that ? That is the only thing i can think of ... The easiest way to check your snapshots are working properly is to check the hard linked files using ls -li. Find some files you know will be the same between two snapshots, and perform an ls -li against them. Then compare the inode numbers of the two to see if they are identical or not. For instance: > $ /bin/ls -li 2006-11-14_Tue/etc/pkgtools.conf 2006-11-13_Mon/etc/pkgtools.conf > 19312769 -rw-r----- 15 backup backup 2242 May 30 20:32 2006-11-13_Mon/etc/pkgtools.conf > 19312769 -rw-r----- 15 backup backup 2242 May 30 20:32 2006-11-14_Tue/etc/pkgtools.conf So in this case, the inode for both files is the same, and I know that file hasn't changed between those two snapshots, so the snapshots are operating correctly. --Antony From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 01:59:26 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45D9316A412; Thu, 16 Nov 2006 01:59:26 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC6843D4C; Thu, 16 Nov 2006 01:59:24 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id DA30748800; Thu, 16 Nov 2006 02:59:23 +0100 (CET) Received: from localhost (djy66.neoplus.adsl.tpnet.pl [83.24.2.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 3A10045684; Thu, 16 Nov 2006 02:59:17 +0100 (CET) Date: Thu, 16 Nov 2006 02:59:08 +0100 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20061116015908.GB63195@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aM3YZ0Iwxop3KEKx" Content-Disposition: inline X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL autolearn=no version=3.0.4 Cc: freebsd-current@FreeBSD.org Subject: ZFS patches for FreeBSD. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 01:59:26 -0000 --aM3YZ0Iwxop3KEKx Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. This is a first set of patches, which allows to use ZFS file system from OpenSolaris on FreeBSD. To apply the patch you need to have recent FreeBSD source (be sure you have rev. 1.284 of src/sys/kern/kern_synch.c). To try it out you need i386 machine (this is what I tested) and kernel without WITNESS compiled in (there are probably some warnings still). Currently it can only be compiled as a kernel module. To apply the patch you need the following steps: # cd /usr/src # mkdir -p cddl/lib/lib{avl,nvpair,umem,uutil,zfs,zpool} # mkdir -p cddl/usr.bin/ztest # mkdir -p cddl/usr.sbin/{zdb,zfs,zpool} # mkdir -p compat/opensolaris/{include,misc} # mkdir -p contrib/opensolaris/cmd/{zdb,zfs,zpool,ztest} # mkdir -p contrib/opensolaris/common/{acl,avl,nvpair,zfs} # mkdir -p contrib/opensolaris/head # mkdir -p contrib/opensolaris/lib/libnvpair # mkdir -p contrib/opensolaris/lib/lib{uutil,zfs}/common # mkdir -p contrib/opensolaris/lib/libzpool/common/sys # mkdir -p sys/compat/opensolaris/{kern,machine,rpc,sys} # mkdir -p sys/contrib/opensolaris/uts/common/fs/zfs/sys # mkdir -p sys/contrib/opensolaris/uts/common/{os,rpc} # mkdir -p sys/contrib/opensolaris/uts/common/sys/fm/fs # mkdir -p sys/contrib/opensolaris/uts/common/sys/fs # mkdir -p sys/modules/zfs # fetch http://people.freebsd.org/~pjd/patches/zfs_20061117.patch.bz2 # bzip2 -d zfs_20061117.patch.bz2 # patch < zfs_20061117.patch # make buildworld # make kernel # make installworld # kldload zfs.ko (zfs and zpool command should work now) Before reboot: # zfs export After reboot: # kldload zfs.ko # zfs import After a panic: # kldload zfs.ko # zfs mount -a # zfs volinit Most of the functionality should work, but there are exceptions. zfs share/unshare don't work yet, you also won't be able to export ZFS files systems via NFS. ACLs don't work yet. The ZFS file system is MPSAFE (it operates without the Giant lock), but performance isn't quite there yet. Please do not report that it is slower than UFS, etc. I know it is. On the other hand you should report if there are some huge differences in performance between UFS and ZFS, for example if ZFS is few times slower in some workloads. Under very heavy load (or maybe even under not that heavy load, but after a longer time) it may panic with "kmem_malloc(X): kmem_map too small: Y total allocated" message. The back-presure mechanism doesn't work well and SUN guys are helping me to figure out why. If you see such panic, please do not report it, just reboot your machine and continue (or not). Please do report any other strange panics or situations (like various commands not working as they should, you see strange file system behaviour, etc.), _but_ before reporting any issue, verify that it wasn't already reported on freebsd-fs@FreeBSD.org mailing list. If you have any questions or comments, I'd prefer if you send them to the mailing list instead of me privately, as it's quite possible others would like to know too. Good luck and enjoy! Big thanks to ZFS developers for great work and to SUN for opening ZFS source! --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --aM3YZ0Iwxop3KEKx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFW8XsForvXbEpPzQRAopsAKCxij/eju0khuMs7X9QQyXlM8ZunwCdG59o GSciI9I5WqSCoCavql2RGAk= =3p1N -----END PGP SIGNATURE----- --aM3YZ0Iwxop3KEKx-- From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 07:42:24 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1709316A415 for ; Thu, 16 Nov 2006 07:42:24 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from lab.alexdupre.com (lab.alexdupre.com [81.174.31.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 111F243D4C for ; Thu, 16 Nov 2006 07:42:22 +0000 (GMT) (envelope-from ale@FreeBSD.org) Received: (qmail 66562 invoked from network); 16 Nov 2006 07:42:40 -0000 Received: from unknown (HELO ?192.168.178.2?) (192.168.178.2) by lab.alexdupre.com with SMTP; 16 Nov 2006 07:42:40 -0000 Message-ID: <455C165D.5080702@FreeBSD.org> Date: Thu, 16 Nov 2006 08:42:21 +0100 From: Alex Dupre User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org References: <20061116015908.GB63195@garage.freebsd.pl> In-Reply-To: <20061116015908.GB63195@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 07:42:24 -0000 Pawel Jakub Dawidek wrote: > This is a first set of patches, which allows to use ZFS file system from > OpenSolaris on FreeBSD. Thanks for your much appreciated work! > To apply the patch you need the following steps: > > # cd /usr/src > # mkdir -p cddl/lib/lib{avl,nvpair,umem,uutil,zfs,zpool} > # mkdir -p cddl/usr.bin/ztest > # mkdir -p cddl/usr.sbin/{zdb,zfs,zpool} > # mkdir -p compat/opensolaris/{include,misc} > # mkdir -p contrib/opensolaris/cmd/{zdb,zfs,zpool,ztest} > # mkdir -p contrib/opensolaris/common/{acl,avl,nvpair,zfs} > # mkdir -p contrib/opensolaris/head > # mkdir -p contrib/opensolaris/lib/libnvpair > # mkdir -p contrib/opensolaris/lib/lib{uutil,zfs}/common > # mkdir -p contrib/opensolaris/lib/libzpool/common/sys > # mkdir -p sys/compat/opensolaris/{kern,machine,rpc,sys} > # mkdir -p sys/contrib/opensolaris/uts/common/fs/zfs/sys > # mkdir -p sys/contrib/opensolaris/uts/common/{os,rpc} > # mkdir -p sys/contrib/opensolaris/uts/common/sys/fm/fs > # mkdir -p sys/contrib/opensolaris/uts/common/sys/fs > # mkdir -p sys/modules/zfs > # fetch http://people.freebsd.org/~pjd/patches/zfs_20061117.patch.bz2 > # bzip2 -d zfs_20061117.patch.bz2 > # patch < zfs_20061117.patch Is it not simpler/enough to replace all these commands with: # cd /usr/src # fetch http://people.freebsd.org/~pjd/patches/zfs_20061117.patch.bz2 # bzip2 -d zfs_20061117.patch.bz2 # patch -p0 < zfs_20061117.patch or even shorter: # cd /usr/src # fetch -o - \ http://people.freebsd.org/~pjd/patches/zfs_20061117.patch.bz2 \ | bunzip2 | patch -p0 ? The point is that using the '-p0' option we can avoid creating directories manually. -- Alex Dupre From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 15:22:04 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 761B116A4A7; Thu, 16 Nov 2006 15:22:04 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0CF243D64; Thu, 16 Nov 2006 15:22:00 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 16 Nov 2006 07:19:17 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id kAGFM0sP069217; Thu, 16 Nov 2006 07:22:00 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id kAGFLxP5069212; Thu, 16 Nov 2006 07:21:59 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200611161521.kAGFLxP5069212@ambrisko.com> In-Reply-To: <20061116015908.GB63195@garage.freebsd.pl> To: freebsd-fs@freebsd.org Date: Thu, 16 Nov 2006 07:21:59 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 15:22:04 -0000 Pawel Jakub Dawidek writes: | This is a first set of patches, which allows to use ZFS file system from | OpenSolaris on FreeBSD. | | To apply the patch you need to have recent FreeBSD source (be sure you | have rev. 1.284 of src/sys/kern/kern_synch.c). | | To try it out you need i386 machine (this is what I tested) and kernel | without WITNESS compiled in (there are probably some warnings still). | | Currently it can only be compiled as a kernel module. | | To apply the patch you need the following steps: | | # cd /usr/src | # fetch http://people.freebsd.org/~pjd/patches/zfs_20061117.patch.bz2 | # bzip2 -d zfs_20061117.patch.bz2 | # patch < zfs_20061117.patch | # make buildworld | # make kernel | # make installworld | # kldload zfs.ko | (zfs and zpool command should work now) | | Before reboot: | # zfs export | | After reboot: | # kldload zfs.ko | # zfs import I skipped the mkdir and used patch -p0. Everything looked to compile okay but when I kldload zfs is fails since the kernel doesn't have memset: %kldload zfs link_elf: symbol memset undefined kldload: can't load zfs: No such file or directory % Is there another change required? Thanks, Doug A. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 17:55:00 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B99A16A4CA for ; Thu, 16 Nov 2006 17:55:00 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.4.150.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 171F243D53 for ; Thu, 16 Nov 2006 17:55:00 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id 2499C263EE; Thu, 16 Nov 2006 12:54:58 -0500 (EST) Date: Thu, 16 Nov 2006 12:54:58 -0500 (EST) From: Ensel Sharon To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: what is the safe <2 TB number, precisely ? 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, 16 Nov 2006 17:55:00 -0000 (6.1-RELEASE - already installed and running with other arrays) I am installing a new array of 5 500 GB disks. It's hard to say what the total raw space will be, but it will certainly be above 2 TB. However, I want to ensure a ZERO-exposure to any 2 TB limit issues (with quotas, and disk tools and snapshots, etc.) So with that in mind, when I go into my adaptec firmware to create an array, and it asks me to specify the size of the array, I am going to type in a number _less than_ the max possible size. So the question is, do I type in 1999 ? 2000 ? 2047 ? 2048 ? What number is totally, absolutely safe and will shield me from _all possible_ BIGDISK related issues ? I am leaning towards 1999 since that _must be_ safe...but am curious if I could get away with 2047 or 2048 ... All comments appreciated. Thank you! From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 18:32:35 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4277116A407 for ; Thu, 16 Nov 2006 18:32:35 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D934E43D60 for ; Thu, 16 Nov 2006 18:32:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kAGIWThA053748; Thu, 16 Nov 2006 12:32:30 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <455CAEC2.3000800@centtech.com> Date: Thu, 16 Nov 2006 12:32:34 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2200/Thu Nov 16 08:10:16 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: what is the safe <2 TB number, precisely ? 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, 16 Nov 2006 18:32:35 -0000 On 11/16/06 11:54, Ensel Sharon wrote: > (6.1-RELEASE - already installed and running with other arrays) > > I am installing a new array of 5 500 GB disks. > > It's hard to say what the total raw space will be, but it will certainly > be above 2 TB. > > However, I want to ensure a ZERO-exposure to any 2 TB limit issues (with > quotas, and disk tools and snapshots, etc.) So with that in mind, when I > go into my adaptec firmware to create an array, and it asks me to specify > the size of the array, I am going to type in a number _less than_ the max > possible size. > > So the question is, do I type in 1999 ? 2000 ? 2047 ? 2048 ? > > What number is totally, absolutely safe and will shield me from _all > possible_ BIGDISK related issues ? > > I am leaning towards 1999 since that _must be_ safe...but am curious if I > could get away with 2047 or 2048 ... > > All comments appreciated. Thank you! I think the only issue you might have, is fsck'ing the filesystem if you ever need to. The more inodes/blocks, the more memory you'll need. Otherwise, large filesystems work well: /dev/label/vol10-data.journal 10T 7.3T 2.0T 79% 150359740 1132635458 12% /vol10 /dev/label/vol11-data.journal 10T 2.2T 7.2T 23% 39852623 1243142575 3% /vol11 Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 19:15:41 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 167C516A415; Thu, 16 Nov 2006 19:15:41 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8581443D7B; Thu, 16 Nov 2006 19:15:33 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA07294; Thu, 16 Nov 2006 21:15:24 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <455CB8CA.8040603@icyb.net.ua> Date: Thu, 16 Nov 2006 21:15:22 +0200 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.8 (X11/20061113) MIME-Version: 1.0 To: Doug Ambrisko References: <1163701391.00638085.1163691003@10.7.7.3> In-Reply-To: <1163701391.00638085.1163691003@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 19:15:41 -0000 on 16/11/2006 17:21 Doug Ambrisko said the following: > I skipped the mkdir and used patch -p0. Everything looked to compile > okay but when I kldload zfs is fails since the kernel doesn't > have memset: > %kldload zfs > link_elf: symbol memset undefined > kldload: can't load zfs: No such file or directory > % > Is there another change required? Hmm, I saw errors like this with some other 3rd party kernel module when its sources had constructs like: struct some_struct s = {0}; Changing the above initialization to explicit bzero() call helped in that case, but I think that there should be some compiler flags or something to handle this. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 19:19:33 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C209516A403; Thu, 16 Nov 2006 19:19:33 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFE4343D67; Thu, 16 Nov 2006 19:19:21 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 5DD7D45696; Thu, 16 Nov 2006 20:19:19 +0100 (CET) Received: from localhost (dlv47.neoplus.adsl.tpnet.pl [83.24.51.47]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 2A7D145681; Thu, 16 Nov 2006 20:19:12 +0100 (CET) Date: Thu, 16 Nov 2006 20:18:59 +0100 From: Pawel Jakub Dawidek To: Doug Ambrisko Message-ID: <20061116191858.GF63195@garage.freebsd.pl> References: <20061116015908.GB63195@garage.freebsd.pl> <200611161521.kAGFLxP5069212@ambrisko.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kR3zbvD4cgoYnS/6" Content-Disposition: inline In-Reply-To: <200611161521.kAGFLxP5069212@ambrisko.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: ** X-Spam-Status: No, score=2.6 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL,RCVD_IN_XBL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 19:19:33 -0000 --kR3zbvD4cgoYnS/6 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 16, 2006 at 07:21:59AM -0800, Doug Ambrisko wrote: > I skipped the mkdir and used patch -p0. Everything looked to compile > okay but when I kldload zfs is fails since the kernel doesn't > have memset: > %kldload zfs > link_elf: symbol memset undefined > kldload: can't load zfs: No such file or directory > % > Is there another change required? I applied the patch before publishing on clean source and I don't see such problem... Interesting thing is that there is no memset() use in ZFS kernel source: # grep -r memset sys/ | grep -v zap_memset # Does anyone else seeing this problem? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --kR3zbvD4cgoYnS/6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFXLmiForvXbEpPzQRAmg6AJ9B9Vm6w59XL3zU6+ZU0++8WqyPOQCgxfXK +kygh5MdWPLchCb9BYGEPPg= =i+2z -----END PGP SIGNATURE----- --kR3zbvD4cgoYnS/6-- From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 19:36:00 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC3EE16A512; Thu, 16 Nov 2006 19:36:00 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 482C043D83; Thu, 16 Nov 2006 19:35:47 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.66.8.19] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis), id 0ML25U-1Gkn1S2kMq-00035f; Thu, 16 Nov 2006 20:35:45 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Thu, 16 Nov 2006 20:35:35 +0100 User-Agent: KMail/1.9.4 References: <20061116015908.GB63195@garage.freebsd.pl> <200611161521.kAGFLxP5069212@ambrisko.com> <20061116191858.GF63195@garage.freebsd.pl> In-Reply-To: <20061116191858.GF63195@garage.freebsd.pl> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3023635.OcQkhFFqoK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200611162035.41595.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-fs@freebsd.org, Doug Ambrisko , Pawel Jakub Dawidek Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 19:36:00 -0000 --nextPart3023635.OcQkhFFqoK Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 16 November 2006 20:18, Pawel Jakub Dawidek wrote: > On Thu, Nov 16, 2006 at 07:21:59AM -0800, Doug Ambrisko wrote: > > I skipped the mkdir and used patch -p0. Everything looked to compile > > okay but when I kldload zfs is fails since the kernel doesn't > > have memset: > > %kldload zfs > > link_elf: symbol memset undefined > > kldload: can't load zfs: No such file or directory > > % > > Is there another change required? > > I applied the patch before publishing on clean source and I don't see > such problem... Interesting thing is that there is no memset() use in > ZFS kernel source: > > # grep -r memset sys/ | grep -v zap_memset > # > > Does anyone else seeing this problem? There is an older thread about this problem:=20 http://lists.freebsd.org/pipermail/freebsd-stable/2005-March/thread.html#13= 132 As pointed out by Andriy "struct foo =3D { 0 }" seems to be the culprit. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3023635.OcQkhFFqoK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFXL2NXyyEoT62BG0RAlQUAJsH0zhOk1ZQJkoNXBhj7sCn49HSDACfZRy6 hoX23Uwain7Z3W9n67tuTNs= =haH7 -----END PGP SIGNATURE----- --nextPart3023635.OcQkhFFqoK-- From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 20:06:24 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD90016A49E; Thu, 16 Nov 2006 20:06:24 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id D48C843DE4; Thu, 16 Nov 2006 20:05:09 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 16 Nov 2006 12:02:25 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id kAGK58xr084522; Thu, 16 Nov 2006 12:05:08 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id kAGK58cB084521; Thu, 16 Nov 2006 12:05:08 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200611162005.kAGK58cB084521@ambrisko.com> In-Reply-To: <20061116191858.GF63195@garage.freebsd.pl> To: Pawel Jakub Dawidek Date: Thu, 16 Nov 2006 12:05:08 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Doug Ambrisko Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 20:06:24 -0000 Pawel Jakub Dawidek writes: | On Thu, Nov 16, 2006 at 07:21:59AM -0800, Doug Ambrisko wrote: | > I skipped the mkdir and used patch -p0. Everything looked to compile | > okay but when I kldload zfs is fails since the kernel doesn't | > have memset: | > %kldload zfs | > link_elf: symbol memset undefined | > kldload: can't load zfs: No such file or directory | > % | > Is there another change required? | | I applied the patch before publishing on clean source and I don't see | such problem... Interesting thing is that there is no memset() use in | ZFS kernel source: | | # grep -r memset sys/ | grep -v zap_memset | # | | Does anyone else seeing this problem? This is on i386: one% grep memset zfs_20061117.patch + (void) memset(p, 0, n); + (void) memset(wp, 0, sizeof (*wp)); + (void) memset(wp, 0, sizeof (*wp)); +zap_memset(void *a, int c, size_t n) + zap_memset(&l->l_phys->l_hdr, 0, sizeof (struct zap_leaf_header)); + zap_memset(l->l_phys->l_hash, CHAIN_END, 2*ZAP_LEAF_HASH_NUMENTRIES(l)); + zap_memset(l->l_phys->l_hash, CHAIN_END, 2*ZAP_LEAF_HASH_NUMENTRIES(l)); one% In contrib/opensolaris/lib/libuutil/common/uu_alloc.c +void * +uu_zalloc(size_t n) +{ + void *p = malloc(n); + + if (p == NULL) { + uu_set_error(UU_ERROR_SYSTEM); + return (NULL); + } + + (void) memset(p, 0, n); + + return (p); +} + %nm dmu_objset.o | grep memset U memset % If I run it compile -E I see static __inline void * memset(void *b, int c, size_t len) { char *bb; if (c == 0) bzero(b, len); else for (bb = (char *)b; len--; ) *bb++ = c; return (b); } and nothing calling it unless it is what Max. is talking about. I don't see other stuff breaking. Doug A. From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 20:08:33 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4548016A4D2; Thu, 16 Nov 2006 20:08:33 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A01F343D5F; Thu, 16 Nov 2006 20:07:46 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id kAGK7DqK054308; Thu, 16 Nov 2006 15:07:13 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Thu, 16 Nov 2006 15:06:56 -0500 User-Agent: KMail/1.6.2 References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> In-Reply-To: <455CB8CA.8040603@icyb.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200611161506.58128.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2200/Thu Nov 16 09:10:16 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-fs@FreeBSD.org, Doug Ambrisko , Andriy Gapon Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 20:08:33 -0000 On Thursday 16 November 2006 02:15 pm, Andriy Gapon wrote: > Hmm, I saw errors like this with some other 3rd party kernel module > when its sources had constructs like: > > struct some_struct s = {0}; > > Changing the above initialization to explicit bzero() call helped > in that case, but I think that there should be some compiler flags > or something to handle this. AFAIK, there was no way to handle this GCC bug with compiler flags. '-ffreestanding' should prevent this to happen but it does not. As Max Laier pointed out, it was discussed long time ago. Bruce Evans had good analysis on this issue, too. Jung-uk Kim From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 21:24:21 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A6DF16A415; Thu, 16 Nov 2006 21:24:21 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BD1343D7D; Thu, 16 Nov 2006 21:24:12 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id kAGLNajb058333; Thu, 16 Nov 2006 16:23:46 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Thu, 16 Nov 2006 16:23:07 -0500 User-Agent: KMail/1.6.2 References: <200611162005.kAGK58cB084521@ambrisko.com> In-Reply-To: <200611162005.kAGK58cB084521@ambrisko.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200611161623.10758.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2200/Thu Nov 16 09:10:16 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-fs@FreeBSD.org, Pawel Jakub Dawidek , Doug Ambrisko Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 21:24:21 -0000 On Thursday 16 November 2006 03:05 pm, Doug Ambrisko wrote: > This is on i386: > one% grep memset zfs_20061117.patch > + (void) memset(p, 0, n); > + (void) memset(wp, 0, sizeof (*wp)); > + (void) memset(wp, 0, sizeof (*wp)); > +zap_memset(void *a, int c, size_t n) > + zap_memset(&l->l_phys->l_hdr, 0, sizeof (struct > zap_leaf_header)); + zap_memset(l->l_phys->l_hash, CHAIN_END, > 2*ZAP_LEAF_HASH_NUMENTRIES(l)); + > zap_memset(l->l_phys->l_hash, CHAIN_END, > 2*ZAP_LEAF_HASH_NUMENTRIES(l)); one% > > In contrib/opensolaris/lib/libuutil/common/uu_alloc.c > +void * > +uu_zalloc(size_t n) > +{ > + void *p = malloc(n); > + > + if (p == NULL) { > + uu_set_error(UU_ERROR_SYSTEM); > + return (NULL); > + } > + > + (void) memset(p, 0, n); > + > + return (p); > +} > + > > %nm dmu_objset.o | grep memset > U memset > % > > If I run it compile -E I see > static __inline void * > memset(void *b, int c, size_t len) > { > char *bb; > > if (c == 0) > bzero(b, len); > else > for (bb = (char *)b; len--; ) > *bb++ = c; > return (b); > } > > and nothing calling it unless it is what Max. is talking about. > I don't see other stuff breaking. It seems the memset() is not used in the kernel part. However, there are at least three places, which does 'struct foo bar = { 0 }': %grep '{ 0 }' zfs_20061117_sys.patch + struct oscarg oa = { 0 }; + struct snaparg sn = { 0 }; + zfs_create_data_t cbdata = { 0 }; (Note: zfs_20061117_sys.patch is extracted from the original patch.) The first two are from dmu_objset_create() and dmu_objset_snapshot() in sys/contrib/opensolaris/uts/common/fs/zfs/dmu_objset.c and that is what you saw. The third one is from zfs_ioc_create() in sys/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c. FYI... Jung-uk Kim From owner-freebsd-fs@FreeBSD.ORG Thu Nov 16 22:01:35 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 179EC16A407; Thu, 16 Nov 2006 22:01:35 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id B37BA43D46; Thu, 16 Nov 2006 22:01:34 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 16 Nov 2006 13:58:49 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id kAGM1WFO090828; Thu, 16 Nov 2006 14:01:32 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id kAGM1W2w090827; Thu, 16 Nov 2006 14:01:32 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200611162201.kAGM1W2w090827@ambrisko.com> In-Reply-To: <200611161623.10758.jkim@FreeBSD.org> To: Jung-uk Kim Date: Thu, 16 Nov 2006 14:01:32 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-fs@FreeBSD.org, Pawel Jakub Dawidek , freebsd-current@FreeBSD.org, Doug Ambrisko Subject: Re: ZFS patches for FreeBSD. 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, 16 Nov 2006 22:01:35 -0000 Okay, I have it compile and linked in: %kldload zfs ZFS filesystem version 3 ZFS storage pool version 3 %kldstat Id Refs Address Size Name 1 15 0xc0400000 662a78 kernel 2 1 0xc0a63000 1ff8 mfi_linux.ko 3 4 0xc0a65000 237c8 linux.ko 4 1 0xc0a89000 a690 mfi.ko 5 1 0xc0a94000 5b700 acpi.ko 6 1 0xc4df6000 6000 linprocfs.ko 7 1 0xc4dfd000 3000 linsysfs.ko 8 1 0xc5051000 9b000 zfs.ko % I "fixed" it by uncommented out: CFLAGS+=-O0 then it works. So it appears to be a compiler thing. Thanks, Doug A. From owner-freebsd-fs@FreeBSD.ORG Fri Nov 17 02:56:47 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81FB416A412 for ; Fri, 17 Nov 2006 02:56:47 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0829943D5D for ; Fri, 17 Nov 2006 02:56:45 +0000 (GMT) (envelope-from kabaev@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so716203wxc for ; Thu, 16 Nov 2006 18:56:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=mu7dc/RhClrdLnWlTYVKXtI00Wup2RZA0OoPEShUZWLaqsKrb5H2/9hgiZs8yWbN7WQ45WAOI6BnMzRZlj8jGwqLyjs7WjnDaXAwCDHpLhvhHIGOChte0N2lSNGWapROi4wcSD1AA0jxt+XIzinZiHCS84fToZT/S3IBmeBRdpk= Received: by 10.90.25.7 with SMTP id 7mr1159365agy.1163732205269; Thu, 16 Nov 2006 18:56:45 -0800 (PST) Received: from kan.dnsalias.net ( [24.34.98.164]) by mx.google.com with ESMTP id 34sm4803445wra.2006.11.16.18.56.44; Thu, 16 Nov 2006 18:56:44 -0800 (PST) Date: Thu, 16 Nov 2006 21:56:39 -0500 From: Alexander Kabaev To: Jung-uk Kim Message-ID: <20061116215639.73d00824@kan.dnsalias.net> In-Reply-To: <200611161506.58128.jkim@FreeBSD.org> References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> <200611161506.58128.jkim@FreeBSD.org> X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_Fy.h/80.Q_ScLGLPieVjIY3"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Andriy Gapon Subject: Re: ZFS patches for FreeBSD. 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, 17 Nov 2006 02:56:47 -0000 --Sig_Fy.h/80.Q_ScLGLPieVjIY3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 16 Nov 2006 15:06:56 -0500 Jung-uk Kim wrote: > On Thursday 16 November 2006 02:15 pm, Andriy Gapon wrote: > > Hmm, I saw errors like this with some other 3rd party kernel module > > when its sources had constructs like: > > > > struct some_struct s =3D {0}; > > > > Changing the above initialization to explicit bzero() call helped > > in that case, but I think that there should be some compiler flags > > or something to handle this. >=20 > AFAIK, there was no way to handle this GCC bug with compiler flags. =20 > '-ffreestanding' should prevent this to happen but it does not. As=20 > Max Laier pointed out, it was discussed long time ago. Bruce Evans=20 > had good analysis on this issue, too. >=20 > Jung-uk Kim > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" This is not a GCC bug. -ffreestanding is _documented_ as requiring memset and friends as resolvable extern symbols. We were just lucky to get away without it before. --=20 Alexander Kabaev --Sig_Fy.h/80.Q_ScLGLPieVjIY3 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFXSTqQ6z1jMm+XZYRAsjxAKCSietsAqGiPX6N3SQOBlHy3fuLXACg52MT DLASmMhgEraxIEFNxiNU9wI= =rzgl -----END PGP SIGNATURE----- --Sig_Fy.h/80.Q_ScLGLPieVjIY3-- From owner-freebsd-fs@FreeBSD.ORG Fri Nov 17 07:57:23 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D529716A407; Fri, 17 Nov 2006 07:57:23 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FEEC43D55; Fri, 17 Nov 2006 07:57:22 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 43C3F5E25; Fri, 17 Nov 2006 10:57:21 +0300 (MSK) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id 2150F5DEA; Fri, 17 Nov 2006 10:57:21 +0300 (MSK) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id kAH7vOiX021821; Fri, 17 Nov 2006 10:57:24 +0300 (MSK) (envelope-from ru) Date: Fri, 17 Nov 2006 10:57:24 +0300 From: Ruslan Ermilov To: Alexander Kabaev Message-ID: <20061117075724.GB21627@rambler-co.ru> References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> <200611161506.58128.jkim@FreeBSD.org> <20061116215639.73d00824@kan.dnsalias.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ftEhullJWpWg/VHq" Content-Disposition: inline In-Reply-To: <20061116215639.73d00824@kan.dnsalias.net> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Andriy Gapon , Jung-uk Kim Subject: Re: ZFS patches for FreeBSD. 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, 17 Nov 2006 07:57:23 -0000 --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 16, 2006 at 09:56:39PM -0500, Alexander Kabaev wrote: > On Thu, 16 Nov 2006 15:06:56 -0500 > Jung-uk Kim wrote: >=20 > > On Thursday 16 November 2006 02:15 pm, Andriy Gapon wrote: > > > Hmm, I saw errors like this with some other 3rd party kernel module > > > when its sources had constructs like: > > > > > > struct some_struct s =3D {0}; > > > > > > Changing the above initialization to explicit bzero() call helped > > > in that case, but I think that there should be some compiler flags > > > or something to handle this. > >=20 > > AFAIK, there was no way to handle this GCC bug with compiler flags. =20 > > '-ffreestanding' should prevent this to happen but it does not. As=20 > > Max Laier pointed out, it was discussed long time ago. Bruce Evans=20 > > had good analysis on this issue, too. > >=20 > This is not a GCC bug. -ffreestanding is _documented_ as requiring > memset and friends as resolvable extern symbols. We were just lucky to > get away without it before. >=20 Yes. But to make it clear: it's there in libkern.h, just not external. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --ftEhullJWpWg/VHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFXWtkqRfpzJluFF4RAnONAKCEnwh1SR3Qxv+Y5PlgplswawZ6nQCfRCbN mkPoAAB1u+A9sDnSaqaANzY= =dmYW -----END PGP SIGNATURE----- --ftEhullJWpWg/VHq-- From owner-freebsd-fs@FreeBSD.ORG Fri Nov 17 10:08:19 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89AFC16A407; Fri, 17 Nov 2006 10:08:19 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24AD943D58; Fri, 17 Nov 2006 10:08:19 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout1.pacific.net.au (Postfix) with ESMTP id 889FA5A0538; Fri, 17 Nov 2006 21:08:17 +1100 (EST) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (Postfix) with ESMTP id 5B6998C13; Fri, 17 Nov 2006 21:08:16 +1100 (EST) Date: Fri, 17 Nov 2006 21:08:15 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Jung-uk Kim In-Reply-To: <200611161506.58128.jkim@FreeBSD.org> Message-ID: <20061117210000.S11101@delplex.bde.org> References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> <200611161506.58128.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Doug Ambrisko , Andriy Gapon Subject: Re: ZFS patches for FreeBSD. 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, 17 Nov 2006 10:08:19 -0000 On Thu, 16 Nov 2006, Jung-uk Kim wrote: > On Thursday 16 November 2006 02:15 pm, Andriy Gapon wrote: >> Hmm, I saw errors like this with some other 3rd party kernel module >> when its sources had constructs like: >> >> struct some_struct s = {0}; >> >> Changing the above initialization to explicit bzero() call helped >> in that case, but I think that there should be some compiler flags >> or something to handle this. > > AFAIK, there was no way to handle this GCC bug with compiler flags. > '-ffreestanding' should prevent this to happen but it does not. As > Max Laier pointed out, it was discussed long time ago. Bruce Evans > had good analysis on this issue, too. Source code that triggers this bug might be broken anyway. gcc should only call a function to do the zeroing for large structs, but large structs might be too large for the kernel stack. Bruce From owner-freebsd-fs@FreeBSD.ORG Fri Nov 17 13:33:20 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B2DC16A416 for ; Fri, 17 Nov 2006 13:33:20 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73C1843D58 for ; Fri, 17 Nov 2006 13:33:18 +0000 (GMT) (envelope-from kabaev@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so830618wxc for ; Fri, 17 Nov 2006 05:33:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=Ud86v0LGt1ZOpA/RiuiixFzocEdogwuhLyTPJrV+lQ3dphjfaW5tGrTLjaywu2e4eYb3QpbIvKAlgQ9wbpJmTt6AET2qJD1H9tVRGX1/4GXe6I9t0gNtDm0vduoVEQDrkCc4dTefNjDo4gBy/MPrI8CY/GM3wO6H1GiEJX6uVvQ= Received: by 10.70.76.13 with SMTP id y13mr3105687wxa.1163770397391; Fri, 17 Nov 2006 05:33:17 -0800 (PST) Received: from kan.dnsalias.net ( [24.34.98.164]) by mx.google.com with ESMTP id i11sm4514444wxd.2006.11.17.05.33.15; Fri, 17 Nov 2006 05:33:16 -0800 (PST) Date: Fri, 17 Nov 2006 08:33:11 -0500 From: Alexander Kabaev To: Ruslan Ermilov Message-ID: <20061117083311.5ec6aee2@kan.dnsalias.net> In-Reply-To: <20061117075724.GB21627@rambler-co.ru> References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> <200611161506.58128.jkim@FreeBSD.org> <20061116215639.73d00824@kan.dnsalias.net> <20061117075724.GB21627@rambler-co.ru> X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_yFa1scru.N6g2kcEU0vGrD3; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Andriy Gapon , Jung-uk Kim Subject: Re: ZFS patches for FreeBSD. 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, 17 Nov 2006 13:33:20 -0000 --Sig_yFa1scru.N6g2kcEU0vGrD3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 17 Nov 2006 10:57:24 +0300 Ruslan Ermilov wrote: > On Thu, Nov 16, 2006 at 09:56:39PM -0500, Alexander Kabaev wrote: > > On Thu, 16 Nov 2006 15:06:56 -0500 > > Jung-uk Kim wrote: > >=20 > > > On Thursday 16 November 2006 02:15 pm, Andriy Gapon wrote: > > > > Hmm, I saw errors like this with some other 3rd party kernel > > > > module when its sources had constructs like: > > > > > > > > struct some_struct s =3D {0}; > > > > > > > > Changing the above initialization to explicit bzero() call > > > > helped in that case, but I think that there should be some > > > > compiler flags or something to handle this. > > >=20 > > > AFAIK, there was no way to handle this GCC bug with compiler > > > flags. '-ffreestanding' should prevent this to happen but it does > > > not. As Max Laier pointed out, it was discussed long time ago. > > > Bruce Evans had good analysis on this issue, too. > > >=20 > > This is not a GCC bug. -ffreestanding is _documented_ as requiring > > memset and friends as resolvable extern symbols. We were just lucky > > to get away without it before. > >=20 > Yes. But to make it clear: it's there in libkern.h, just not > external. >=20 inline definitions do not satisfy the requirement. So memset is NOT there. I implemented simple-minded amd64 and i386 vesrions for GCC4 import. =20 --=20 Alexander Kabaev --Sig_yFa1scru.N6g2kcEU0vGrD3 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFXboaQ6z1jMm+XZYRAhc+AJ9Ih12+/0eewcWbCkWR5O00Xz5vuwCgi/NO zgmz97+DwmSD1g1CbSoOTDs= =5Ty4 -----END PGP SIGNATURE----- --Sig_yFa1scru.N6g2kcEU0vGrD3-- From owner-freebsd-fs@FreeBSD.ORG Fri Nov 17 13:40:40 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90A1316A47E; Fri, 17 Nov 2006 13:40:40 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA33E43D6D; Fri, 17 Nov 2006 13:40:08 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA27017; Fri, 17 Nov 2006 15:40:05 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <455DBBB4.7010501@icyb.net.ua> Date: Fri, 17 Nov 2006 15:40:04 +0200 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.8 (X11/20061113) MIME-Version: 1.0 To: Alexander Kabaev References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> <200611161506.58128.jkim@FreeBSD.org> <20061116215639.73d00824@kan.dnsalias.net> <20061117075724.GB21627@rambler-co.ru> <20061117083311.5ec6aee2@kan.dnsalias.net> In-Reply-To: <20061117083311.5ec6aee2@kan.dnsalias.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Ruslan Ermilov , Jung-uk Kim Subject: Re: ZFS patches for FreeBSD. 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, 17 Nov 2006 13:40:40 -0000 on 17/11/2006 15:33 Alexander Kabaev said the following: > On Fri, 17 Nov 2006 10:57:24 +0300 > Ruslan Ermilov wrote: > >> On Thu, Nov 16, 2006 at 09:56:39PM -0500, Alexander Kabaev wrote: >>> This is not a GCC bug. -ffreestanding is _documented_ as requiring >>> memset and friends as resolvable extern symbols. We were just lucky >>> to get away without it before. >>> >> Yes. But to make it clear: it's there in libkern.h, just not >> external. >> > > inline definitions do not satisfy the requirement. So memset is NOT > there. I implemented simple-minded amd64 and i386 vesrions for GCC4 > import. And just for the record: I got an impression from a message in a parallel branch of this discussion thread that the compiler behavior in this respect might also depend on optimization level, which probably doesn't mean much for practical usage, but might be an interesting factoid. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Nov 17 17:55:15 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0609816A415 for ; Fri, 17 Nov 2006 17:55:15 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4871A43D4C for ; Fri, 17 Nov 2006 17:55:14 +0000 (GMT) (envelope-from freebsd-fs@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Gl7va-0003JC-Vc for freebsd-fs@freebsd.org; Fri, 17 Nov 2006 18:55:03 +0100 Received: from 89-172-54-252.adsl.net.t-com.hr ([89.172.54.252]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Nov 2006 18:55:02 +0100 Received: from ivoras by 89-172-54-252.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Nov 2006 18:55:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Fri, 17 Nov 2006 18:43:28 +0100 Lines: 14 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-54-252.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) In-Reply-To: Sender: news Subject: Re: what is the safe <2 TB number, precisely ? 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, 17 Nov 2006 17:55:15 -0000 Ensel Sharon wrote: > So the question is, do I type in 1999 ? 2000 ? 2047 ? 2048 ? > > What number is totally, absolutely safe and will shield me from _all > possible_ BIGDISK related issues ? As Eric said, the 2 TB issue is not tied to the file system. It's tied to the fdisk and disklabel. A perfectly valid workaround is not to use fdisk & disklabel to partition your drive, but to partition it in the array creation utility (safest) or use gpt (but you can't modify the gpt table if there are mounted partitions on it). Thus, you can do "newfs /dev/da1", "mount /dev/da1 /whatever", etc. From owner-freebsd-fs@FreeBSD.ORG Fri Nov 17 20:23:00 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9FF816A403 for ; Fri, 17 Nov 2006 20:23:00 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.4.150.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C472443D4C for ; Fri, 17 Nov 2006 20:23:00 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id 6482926393; Fri, 17 Nov 2006 15:22:55 -0500 (EST) Date: Fri, 17 Nov 2006 15:22:55 -0500 (EST) From: Ensel Sharon To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: final confirmation of sysinstall-method for disk addition... 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, 17 Nov 2006 20:23:01 -0000 First off, thanks for the help the last two days - I appreciate your comments very much. I am going to add my five 500 GB disks to my system today, and I am going to tell my adaptec card to create a 1999 GB array on them. Therefore, the "disk" that will be presented to FreeBSD by the raid card will be <2TB. This means that I should be able to use sysinstall. My question is: - Is there _any reason whatsoever_ that this method: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-adding.html (top item, 17.3.1, adding a new disk to an existing system using sysinstall) will not work with 6.1-RELEASE and a 1999 GB disk ? Any chance this document is slightly out of date, or some minor changes that are in 6.1 that aren't in the docs yet ? Or can I just follow these instructions to the letter and happily add my disk ? Thanks. From owner-freebsd-fs@FreeBSD.ORG Sat Nov 18 07:51:43 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EB0B16AF03 for ; Sat, 18 Nov 2006 07:51:43 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0ABD43FE7 for ; Sat, 18 Nov 2006 04:06:26 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.25] ([192.168.42.25]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id kAI46KHJ002628; Fri, 17 Nov 2006 22:06:20 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <455E86BF.5060801@centtech.com> Date: Fri, 17 Nov 2006 22:06:23 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2202/Fri Nov 17 18:37:07 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: final confirmation of sysinstall-method for disk addition... 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, 18 Nov 2006 07:51:43 -0000 On 11/17/06 14:22, Ensel Sharon wrote: > First off, thanks for the help the last two days - I appreciate your > comments very much. > > > I am going to add my five 500 GB disks to my system today, and I am going > to tell my adaptec card to create a 1999 GB array on them. > > Therefore, the "disk" that will be presented to FreeBSD by the raid card > will be <2TB. This means that I should be able to use sysinstall. > > My question is: > > - Is there _any reason whatsoever_ that this method: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-adding.html > > (top item, 17.3.1, adding a new disk to an existing system using > sysinstall) > > will not work with 6.1-RELEASE and a 1999 GB disk ? Any chance this > document is slightly out of date, or some minor changes that are in 6.1 > that aren't in the docs yet ? > > Or can I just follow these instructions to the letter and happily add my > disk ? > > Thanks. Why not download the recently built 6.2-RC1 disk, experiment with that, and report any issues you *do* hit, that way others can learn from your experience, and we can make FreeBSD better. 'Just do it' Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Sat Nov 18 11:44:45 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A337B16A403 for ; Sat, 18 Nov 2006 11:44:45 +0000 (UTC) (envelope-from zfo@telcontrol.com) Received: from telcontrol.com (ene28.neoplus.adsl.tpnet.pl [83.21.250.28]) by mx1.FreeBSD.org (Postfix) with SMTP id 6E9E843D45 for ; Sat, 18 Nov 2006 11:44:40 +0000 (GMT) (envelope-from zfo@telcontrol.com) Message-ID: <000001c70053$3bfe56c0$8049d1d0@pdaedalusl> From: " M" To: Date: Sat, 18 Nov 2006 12:51:09 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: News Break f X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: M List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2006 11:44:45 -0000 THIS ONE IS BEING PROMOTED, TAKE ADVANTAGE This advisory is based on exclusive insiders/agents information. (AVLN.OB) Avalon Energy Corporation has an undivided 85% working interest in the Shotgun Draw Prospect in the prolific natural gas producing Uinta Basin , located in the US Rockies, Utah . The lease comprises 13,189 acres with a potential 4 TCF recoverable gas and is overpressured by a 0.55 . 0.85 gradient. ON MONDAY NOV 6th: at 11 cents its a STEAL - Volume: 389,001 - Volume: + 50% - Price: +5.77% The key to any tade is buying low and selling high, WELL the energy market has bottomed out and time to get in is now. We specialise in calling market bottom and when it comes to energy THIS IS THE BOTTOM, SO GET IN FOLKS AS REAL AS IT GETS AS REAL AS IT GETS Last week's fire was stoked by Santa Ana winds as it swept southwest through the mountains about 90 miles east of Los Angeles. The flames overran the fire crew, destroyed 34 homes and charred more than 60 square miles before being contained Monday. President Bush, working a southwest Missouri campaign crowd like a yell leader, blasted Democrats on Friday, saying they have no plan to keep Americans safe from terrorists. Last week's fire was stoked by Santa Ana winds as it swept southwest through the mountains about 90 miles east of Los Angeles. The flames overran the fire crew, destroyed 34 homes and charred more than 60 square miles before being contained Monday. President Bush, working a southwest Missouri campaign crowd like a yell leader, blasted Democrats on Friday, saying they have no plan to keep Americans safe from terrorists.