From owner-freebsd-fs@FreeBSD.ORG Sun Oct 27 22:11:33 2013 Return-Path: Delivered-To: freebsd-fs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0B669405; Sun, 27 Oct 2013 22:11:33 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D4BCB20CA; Sun, 27 Oct 2013 22:11:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9RMBWt2005268; Sun, 27 Oct 2013 22:11:32 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9RMBWEk005267; Sun, 27 Oct 2013 22:11:32 GMT (envelope-from linimon) Date: Sun, 27 Oct 2013 22:11:32 GMT Message-Id: <201310272211.r9RMBWEk005267@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/183230: [ext2fs] ext2fs hash function incompatible with linux X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Oct 2013 22:11:33 -0000 Old Synopsis: ext2fs hash function incompatible with linux New Synopsis: [ext2fs] ext2fs hash function incompatible with linux Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sun Oct 27 22:11:01 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=183230 From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 06:56:03 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ADB80825; Mon, 28 Oct 2013 06:56:03 +0000 (UTC) (envelope-from Ivailo.TANUSHEFF@raiffeisen.bg) Received: from mg2.raiffeisen.bg (mg2.raiffeisen.bg [194.48.206.15]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 42DA1264A; Mon, 28 Oct 2013 06:56:02 +0000 (UTC) X-WSS-ID: 0MVD9X2-03-ECB-02 X-M-MSG: Received: from bgrbbl2.rbblan.internal (unknown [10.3.66.167]) by mg2.raiffeisen.bg (Postfix) with ESMTP id 2841722C045; Mon, 28 Oct 2013 08:55:50 +0200 (EET) In-Reply-To: To: "Steven Hartland" Subject: Re: [ADMIN] ZFS-FreeBSD + postgresql performance From: Ivailo.TANUSHEFF@raiffeisen.bg Message-ID: Date: Mon, 28 Oct 2013 08:55:29 +0200 References: <20131023162545.GA19794@pcjas.obspm.fr> <1382548465.32073.37624113.6AA8DB42@webmail.messagingengine.com> <52683855.6060609@gmx.net> <1382716422.13782.YahooMailNeo@web193504.mail.sg3.yahoo.com> MIME-Version: 1.0 X-KeepSent: A2082B0A:0C83667D-C2257C12:0025E1CF; name=$KeepSent; type=4 X-Mailer: Raiffeisenbank (Bulgaria) X-Disclaimed: 37427 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Patrick Dung , pgsql-admin@postgresql.org, owner-freebsd-fs@freebsd.org, freebsd-fs@freebsd.org, freebsd-jail@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 06:56:03 -0000 IlN0ZXZlbiBIYXJ0bGFuZCIgPGtpbGxpbmdAbXVsdGlwbGF5LmNvLnVrPiB3cm90ZSBvbiAyNS4x MC4yMDEzIDE5OjE5OjU0Og0KDQo+IEZyb206DQo+IA0KPiAiU3RldmVuIEhhcnRsYW5kIiA8a2ls bGluZ0BtdWx0aXBsYXkuY28udWs+DQo+IA0KPiBUbzoNCj4gDQo+ICJQYXRyaWNrIER1bmciIDxw YXRyaWNrX2RrdEB5YWhvby5jb20uaGs+LCANCj4gPEl2YWlsby5UQU5VU0hFRkZAcmFpZmZlaXNl bi5iZz4sICJNaWNoYWVsIFNjaG1pZWRnZW4iIA0KPHNjaG1pZWRnZW5AZ214Lm5ldD4sIA0KPiAN Cj4gQ2M6DQo+IA0KPiA8b3duZXItZnJlZWJzZC1mc0BmcmVlYnNkLm9yZz4sIDxmcmVlYnNkLWZz QGZyZWVic2Qub3JnPiwgPHBnc3FsLQ0KPiBhZG1pbkBwb3N0Z3Jlc3FsLm9yZz4sIDxmcmVlYnNk LWphaWxAZnJlZWJzZC5vcmc+DQo+IA0KPiBEYXRlOg0KPiANCj4gMjUuMTAuMjAxMyAxOToyMA0K PiANCj4gU3ViamVjdDoNCj4gDQo+IFJlOiBbQURNSU5dIFpGUy1GcmVlQlNEICsgcG9zdGdyZXNx bCBwZXJmb3JtYW5jZQ0KPiANCj4gLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCj4gRnJv bTogIlBhdHJpY2sgRHVuZyIgPHBhdHJpY2tfZGt0QHlhaG9vLmNvbS5oaz4NCj4gU2VudDogRnJp ZGF5LCBPY3RvYmVyIDI1LCAyMDEzIDQ6NTMgUE0NCj4gU3ViamVjdDogUmU6IFtBRE1JTl0gWkZT LUZyZWVCU0QgKyBwb3N0Z3Jlc3FsIHBlcmZvcm1hbmNlDQo+IA0KPiANCj4gPj4gSSB3b3VsZCBh bHNvIHJlY29tbWVuZCB0byB1c2UgNEsgc2VjdG9yIHNpemUgdXNpbmcNCj4gPg0KPiA+IGdub3Ag YW5kIHpwb29sIGV4cG9ydC9pbXBvcnQuDQo+IA0KPiBUaGlzIHdpbGwgaGF2ZSBubyBlZmZlY3Qs IHRoZSBhc2hpZnQgZm9yIGEgcG9vbCBpcyBzZXQgYXQgY3JlYXRpb24uDQo+IA0KPiAgICAgUmVn YXJkcw0KPiAgICAgU3RldmUNCj4gDQoNClRoYXQncyB0aGUgaWRlYTogdG8gc2V0IHRoZSBhc2hp ZnQgZHVyaW5nIHRoZSBjcmVhdGlvbiBvZiB0aGUgcG9vbC4gTmV2ZXIgDQpkaWQgdGhhdCBiZWZv cmU/DQoNCmdub3AgY3JlYXRlIC1TIDQwOTYgL2Rldi9ncHQvZGlzazANCmdub3AgY3JlYXRlIC1T IDQwOTYgL2Rldi9ncHQvZGlzazENCnpwb29sIGNyZWF0ZSBtaXJyb3IgL2Rldi9ncHQvZGlzazAu bm9wIC9kZXYvZ3B0L2Rpc2sxLm5vcA0KenBvb2wgZXhwb3J0IHpyb290DQpnbm9wIGRlc3Ryb3kg L2Rldi9ncHQvZGlzazAubm9wDQpnbm9wIGRlc3Ryb3kgL2Rldi9ncHQvZGlzazEubm9wDQp6cG9v bCBpbXBvcnQgenJvb3QNCg0KQmVzdCByZWdhcmRzLA0KSXZhaWxvIFRhbnVzaGVmZg0KDQpESVND TEFJTUVSOiBUaGUgY29udGVudHMgb2YgdGhpcyBlLW1haWwgYXJlIGludGVuZGVkIGZvciB0aGUg bmFtZWQgYWRkcmVzc2VlIG9ubHkuIEl0IGNvbnRhaW5zIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJl IHByaXZpbGVnZWQgYW5kL29yIGNvbmZpZGVudGlhbC4gVW5sZXNzIHlvdSBhcmUgdGhlIG5hbWVk IGFkZHJlc3NlZSBvciBhbiBhdXRob3JpemVkIGRlc2lnbmVlLCB5b3UgbWF5IG5vdCBjb3B5IG9y IHVzZSBpdCwgb3IgZGlzY2xvc2UgaXQgdG8gYW55b25lIGVsc2UuIElmIHlvdSByZWNlaXZlZCBp dCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHVzIGltbWVkaWF0ZWx5IGFuZCB0aGVuIGRlc3Ryb3kg aXQuIE1lc3NhZ2VzIHRyYW5zcG9ydGVkIG92ZXIgdGhlIHB1YmxpYyBJbnRlcm5ldCBhcmUgc3Vz Y2VwdGlibGUgdG8gYWx0ZXJhdGlvbi4gUmFpZmZlaXNlbmJhbmsgKEJ1bGdhcmlhKSBFQUQsIFJh aWZmZWlzZW4gQXNzZXQgTWFuYWdlbWVudCAoQnVsZ2FyaWEpIEVBRCwgUmFpZmZlaXNlbiBJbnN1 cmFuY2UgQnJva2VyIEVPT0QsIFJhaWZmZWlzZW4gU2VydmljZXMgRUFELCBSYWlmZmVpc2VuIExl YXNpbmcgQnVsZ2FyaWEgT09ELCBSYWlmZmVpc2VuIEF1dG8gTGVhc2luZyBCdWxnYXJpYSBFT09E IGFuZCBSYWlmZmVpc2VuIFJlYWwgRXN0YXRlIEVPT0Qgc2hhbGwgbm90IGJlIGxpYWJsZSBmb3Ig dGhlIG1lc3NhZ2UgaWYgYWx0ZXJlZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuICDv5/Lh7un+5e7p 5SDu4SDv9Ofv9+/y7u/z9PThOiDz38Tf0tbBzsnF1M8gzsEg1M/XwSDFzMXL1NLPzs7PINPfz8Ld xc7JxSDFINDSxcTOwdrOwd7Fzs8gxcTJztPU18XOzyDawSDQz9PP3sXOydEg0M/M1d7B1MXMLiDz 38/C3cXOycXUzyDT38Tf0tbBIMnOxs/SzcHDydEsIMvP0dTPIM3P1sUgxMEgwt/ExSDQ0sXEzsHa zsHexc7BINrBIM/H0sHOyd7Fzs8g0M/M2tfBzsUgyS/JzMkg0M/XxdLJ1MXMzsEuIPcg08zV3sHK IN7FIM7FINPUxSDVy8Hawc7J0SDQz8zV3sHUxcwgzsEg1M/XwSDT38/C3cXOycUgyczJIM7Fx8/X IM/Uz9LJ2snSwc4g0NLFxNPUwdfJ1MXMLCDO0c3B1MUg0NLB188gxMEgx88gy8/QydLB1MUgyczJ IMna0M/M2tfB1MUsIMvBy9TPIMkgxMEg0sHay9LJ18HUxSDT38Tf0tbBzsnF1M8gzdUg0NLFxCDU 0sXUySDMycPBLiDhy88g09TFIMfPINDPzNXeyczJINDPIMfSxdvLwSwgzc/M0SDEwSDV18XEz83J 1MUg0M/EwdTFzNEgzsXawcLB187PIMkgxMEgydrU0snF1MUg1M/XwSDT38/C3cXOycUgz9Qg08nT 1MXNwdTBLiDlzMXL1NLPzs7J1MUg09/Pwt3FzsnRLCDSwdrQ0s/T1NLBztHXwc7JINDPIOnO1MXS zsXUIM3Px8HUIMTBIMLfxMHUINDSz83FztHOyS4g8sHKxsHK2sXOwsHOyyAo4t/Mx8HSydEpIOXh 5Cwg8sHKxsHK2sXOIOHTxdQg7cXOycTWzd/O1CAo4t/Mx8HSydEpIOXh5Cwg8sHKxsHK2sXOIPrB 09TSwcjP18HUxczFziDi0s/LxdIg5e/v5Cwg8sHKxsHK2sXOIPPf0tfJ08naIOXh5Cwg8sHKxsHK 2sXOIOzJ2snOxyDi38zHwdLJ0SDv7+QsIPLBysbBytrFziDh1dTPIOzJ2snOxyDi38zHwdLJ0SDl 7+/kIMkg8sHKxsHK2sXOIOnNz9TJIOXv7+QgzsUgzs/T0dQgz9THz9fP0s7P09Qg2sEgzc/EycbJ w8nSwc7JLCDQ0s/Nxc7FzskgyczJIMbBzNvJxsnDydLBzskg09/Pwt3FzsnRLiAg From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 09:26:47 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 196F651C; Mon, 28 Oct 2013 09:26:47 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id D07392E08; Mon, 28 Oct 2013 09:26:46 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Vaj7s-0006hr-K9; Mon, 28 Oct 2013 13:28:44 +0400 Date: Mon, 28 Oct 2013 13:28:44 +0400 From: Slawa Olhovchenkov To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: ZFS txg implementation flaw Message-ID: <20131028092844.GA24997@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 09:26:47 -0000 I can be wrong. As I see ZFS cretate seperate thread for earch txg writing. Also for writing to L2ARC. As result -- up to several thousands threads created and destoyed per second. And hundreds thousands page allocations, zeroing, maping unmaping and freeing per seconds. Very high overhead. In systat -vmstat I see totfr up to 600000, prcfr up to 200000. Estimated overhead -- 30% of system time. Can anybody implement thread and page pool for txg? From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 09:27:31 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5FE4177F; Mon, 28 Oct 2013 09:27:31 +0000 (UTC) (envelope-from prvs=10136994e7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 86E3E2E23; Mon, 28 Oct 2013 09:27:30 +0000 (UTC) Received: from r2d2 ([82.69.179.245]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50006524437.msg; Mon, 28 Oct 2013 09:27:29 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Mon, 28 Oct 2013 09:27:29 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.179.245 X-Return-Path: prvs=10136994e7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <5E70894E80E24CF5AF894DAF80DCF04E@multiplay.co.uk> From: "Steven Hartland" To: References: <20131023162545.GA19794@pcjas.obspm.fr> <1382548465.32073.37624113.6AA8DB42@webmail.messagingengine.com> <52683855.6060609@gmx.net> <1382716422.13782.YahooMailNeo@web193504.mail.sg3.yahoo.com> Subject: Re: [ADMIN] ZFS-FreeBSD + postgresql performance Date: Mon, 28 Oct 2013 09:27:42 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: Patrick Dung , pgsql-admin@postgresql.org, owner-freebsd-fs@freebsd.org, freebsd-fs@freebsd.org, freebsd-jail@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 09:27:31 -0000 ----- Original Message ----- From: >> ----- Original Message ----- >> From: "Patrick Dung" >> Sent: Friday, October 25, 2013 4:53 PM >> Subject: Re: [ADMIN] ZFS-FreeBSD + postgresql performance >> >> >> >> I would also recommend to use 4K sector size using >> > >> > gnop and zpool export/import. >> >> This will have no effect, the ashift for a pool is set at creation. >> >> Regards >> Steve >> > > That's the idea: to set the ashift during the creation of the pool. Never > did that before? > > gnop create -S 4096 /dev/gpt/disk0 > gnop create -S 4096 /dev/gpt/disk1 > zpool create mirror /dev/gpt/disk0.nop /dev/gpt/disk1.nop > zpool export zroot > gnop destroy /dev/gpt/disk0.nop > gnop destroy /dev/gpt/disk1.nop > zpool import zroot First if your on 10 or 11 you don't need this unless you have a disk which is 4k but is reporting 512b and isnt in our list of quirks. If you still need to do this you only need to do gnop create / destroy onone disk per top level vdev so in your example thats only one disk. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 11:06:48 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2FDA4AAF for ; Mon, 28 Oct 2013 11:06:48 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0F3262469 for ; Mon, 28 Oct 2013 11:06:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9SB6mpA055074 for ; Mon, 28 Oct 2013 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9SB6lZ8055072 for freebsd-fs@FreeBSD.org; Mon, 28 Oct 2013 11:06:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Oct 2013 11:06:47 GMT Message-Id: <201310281106.r9SB6lZ8055072@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 11:06:48 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/183230 fs [ext2fs] ext2fs hash function incompatible with linux o kern/182570 fs [zfs] [patch] ZFS panic in receive o kern/182536 fs [zfs] zfs deadlock o kern/181966 fs [zfs] Kernel panic in ZFS I/O: solaris assert: BP_EQUA o kern/181834 fs [nfs] amd mounting NFS directories can drive a dead-lo o kern/181565 fs [swap] Problem with vnode-backed swap space. o kern/181377 fs [zfs] zfs recv causes an inconsistant pool o kern/181281 fs [msdosfs] stack trace after successfull 'umount /mnt' o kern/181082 fs [fuse] [ntfs] Write to mounted NTFS filesystem using F o kern/180979 fs [netsmb][patch]: Fix large files handling o kern/180876 fs [zfs] [hast] ZFS with trim,bio_flush or bio_delete loc o kern/180678 fs [NFS] succesfully exported filesystems being reported o kern/180438 fs [smbfs] [patch] mount_smbfs fails on arm because of wr p kern/180236 fs [zfs] [nullfs] Leakage free space using ZFS with nullf o kern/178854 fs [ufs] FreeBSD kernel crash in UFS s kern/178467 fs [zfs] [request] Optimized Checksum Code for ZFS o kern/178412 fs [smbfs] Coredump when smbfs mounted o kern/178388 fs [zfs] [patch] allow up to 8MB recordsize o kern/178387 fs [zfs] [patch] sparse files performance improvements o kern/178349 fs [zfs] zfs scrub on deduped data could be much less see o kern/178329 fs [zfs] extended attributes leak o kern/178238 fs [nullfs] nullfs don't release i-nodes on unlink. f kern/178231 fs [nfs] 8.3 nfsv4 client reports "nfsv4 client/server pr o kern/177985 fs [zfs] disk usage problem when copying from one zfs dat o kern/177971 fs [nfs] FreeBSD 9.1 nfs client dirlist problem w/ nfsv3, o kern/177966 fs [zfs] resilver completes but subsequent scrub reports o kern/177658 fs [ufs] FreeBSD panics after get full filesystem with uf o kern/177536 fs [zfs] zfs livelock (deadlock) with high write-to-disk o kern/177445 fs [hast] HAST panic o kern/177240 fs [zfs] zpool import failed with state UNAVAIL but all d o kern/176978 fs [zfs] [panic] zfs send -D causes "panic: System call i o kern/176857 fs [softupdates] [panic] 9.1-RELEASE/amd64/GENERIC panic o bin/176253 fs zpool(8): zfs pool indentation is misleading/wrong o kern/176141 fs [zfs] sharesmb=on makes errors for sharenfs, and still o kern/175950 fs [zfs] Possible deadlock in zfs after long uptime o kern/175897 fs [zfs] operations on readonly zpool hang o kern/175449 fs [unionfs] unionfs and devfs misbehaviour o kern/175179 fs [zfs] ZFS may attach wrong device on move o kern/175071 fs [ufs] [panic] softdep_deallocate_dependencies: unrecov o kern/174372 fs [zfs] Pagefault appears to be related to ZFS o kern/174315 fs [zfs] chflags uchg not supported o kern/174310 fs [zfs] root point mounting broken on CURRENT with multi o kern/174279 fs [ufs] UFS2-SU+J journal and filesystem corruption o kern/173830 fs [zfs] Brain-dead simple change to ZFS error descriptio o kern/173718 fs [zfs] phantom directory in zraid2 pool f kern/173657 fs [nfs] strange UID map with nfsuserd o kern/173363 fs [zfs] [panic] Panic on 'zpool replace' on readonly poo o kern/173136 fs [unionfs] mounting above the NFS read-only share panic o kern/172942 fs [smbfs] Unmounting a smb mount when the server became o kern/172348 fs [unionfs] umount -f of filesystem in use with readonly o kern/172334 fs [unionfs] unionfs permits recursive union mounts; caus o kern/171626 fs [tmpfs] tmpfs should be noisier when the requested siz o kern/171415 fs [zfs] zfs recv fails with "cannot receive incremental o kern/170945 fs [gpt] disk layout not portable between direct connect o bin/170778 fs [zfs] [panic] FreeBSD panics randomly o kern/170680 fs [nfs] Multiple NFS Client bug in the FreeBSD 7.4-RELEA o kern/170497 fs [xfs][panic] kernel will panic whenever I ls a mounted o kern/169945 fs [zfs] [panic] Kernel panic while importing zpool (afte o kern/169480 fs [zfs] ZFS stalls on heavy I/O o kern/169398 fs [zfs] Can't remove file with permanent error o kern/169339 fs panic while " : > /etc/123" o kern/169319 fs [zfs] zfs resilver can't complete o kern/168947 fs [nfs] [zfs] .zfs/snapshot directory is messed up when o kern/168942 fs [nfs] [hang] nfsd hangs after being restarted (not -HU o kern/168158 fs [zfs] incorrect parsing of sharenfs options in zfs (fs o kern/167979 fs [ufs] DIOCGDINFO ioctl does not work on 8.2 file syste o kern/167977 fs [smbfs] mount_smbfs results are differ when utf-8 or U o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene o kern/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161864 fs [ufs] removing journaling from UFS partition fails on o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic f kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o bin/153142 fs [zfs] ls -l outputs `ls: ./.zfs: Operation not support o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server o kern/145750 fs [unionfs] [hang] unionfs locks the machine s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an f bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141950 fs [unionfs] [lor] ufs/unionfs/ufs Lock order reversal o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/137588 fs [unionfs] [lor] LOR nfs/ufs/nfs o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis p kern/133174 fs [msdosfs] [patch] msdosfs must support multibyte inter o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126973 fs [unionfs] [hang] System hang with unionfs and init chr o kern/126553 fs [unionfs] unionfs move directory problem 2 (files appe o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o bin/123574 fs [unionfs] df(1) -t option destroys info for unionfs (a o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o kern/121385 fs [unionfs] unionfs cross mount -> kernel panic o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/67326 fs [msdosfs] crash after attempt to mount write protected o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t o kern/9619 fs [nfs] Restarting mountd kills existing mounts 337 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 15:07:28 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 230ABD3B for ; Mon, 28 Oct 2013 15:07:28 +0000 (UTC) (envelope-from cjpugmed@gmail.com) Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DA90F25C0 for ; Mon, 28 Oct 2013 15:07:27 +0000 (UTC) Received: by mail-ve0-f178.google.com with SMTP id jy13so6201277veb.9 for ; Mon, 28 Oct 2013 08:07:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=fqHCwoiQAP/FnD3O7btrxcXkToiIWtcB1EQcDpGD9tQ=; b=pBTRwWntO2P9n4hffrqNERB3XgV4I9KtPExYboY5BF7gvBLjwcqpgBUisqLjKHt/uw d4gvZ3POtfrREp93qC3Uf2MjDpM7zMS09Xf/s2FGwkyeAPNheLlJI9yABhqTz+mt7+9U w1qqDd6Dg35xSsdQi3WBJ+RO1XUIYJs0uAs/JJkzhP7bKiYkB5VvOgoe3vhAzIUAeePH BYGk28bpCT3Z6AiBDYZ5JkxEhipEsKvN/NkrIewcw2z3XapUmbIuFpar+/bJSuHtUqin l8EtFv/NAHOPya23J3+NE73RnEpLHYV4sn5G8a88lGnhVxNpp23cBzvLM5xjuHrbdK55 FwuA== MIME-Version: 1.0 X-Received: by 10.220.78.18 with SMTP id i18mr13543734vck.3.1382972846912; Mon, 28 Oct 2013 08:07:26 -0700 (PDT) Received: by 10.220.1.17 with HTTP; Mon, 28 Oct 2013 08:07:26 -0700 (PDT) Date: Mon, 28 Oct 2013 16:07:26 +0100 Message-ID: Subject: fusefs-ntfs crashes on FreeBSD 9.2 From: Carlos Jacobo Puga Medina To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 15:07:28 -0000 I can mount properly a external USB hard disk, but when I try to copy/move something the system crashes and it need a hard reset to recover. I just installed an updated version of sysutils/fusefs-kmod [1] and it doesn't solved the problem. I can not provide any information because after blocking all the system there is no trace of logs. Does someone know what happens? [1] http://lists.freebsd.org/pipermail/freebsd-hackers/2013-October/043519.html From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 17:45:05 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2F942FFA; Mon, 28 Oct 2013 17:45:05 +0000 (UTC) (envelope-from aurfalien@gmail.com) Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 040DC20A0; Mon, 28 Oct 2013 17:45:04 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id xb4so3932857pbc.8 for ; Mon, 28 Oct 2013 10:45:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ne8RnvFSIZi5FRW7OTIi+ypUewIfwVjBXdJTfHBnYVU=; b=zUqsyegrxSSv0gEgvRfpEXco5izLXafKcEfhxaJgAuBza+bcjzX1+XiyJ3giLcR8yM KLqZOVP5N3Tq2XgUokzPyoi1zcAFsRR/su0NGxdMMbTEBKTQ8XB2pHAgPCrxjR67xmzm fAoPqKwlZowkpBpsfMHtU6y+FnnSIgiLptoTmFtUEISG8rByb4UJiwmcM66XKPttMrSc Cqh6AwQIkEh3moIRFrBFe09aaoCi7ZRSHqvVQim9UMEHuZKTl1034m3Y0yopCjx91mOb AH/I/5dzeo+g9c17b7oXWq3mrFpCKsSlOUiXTWG0Ixuns9wpC6D+uZbSJk+h7bT94Wh7 ZT5g== X-Received: by 10.68.129.40 with SMTP id nt8mr17365753pbb.108.1382982304662; Mon, 28 Oct 2013 10:45:04 -0700 (PDT) Received: from briankrusicw.logan.tv ([64.17.255.138]) by mx.google.com with ESMTPSA id bp5sm29922154pbb.18.2013.10.28.10.45.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Oct 2013 10:45:03 -0700 (PDT) Subject: Re: ZFS txg implementation flaw Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: aurfalien In-Reply-To: <20131028092844.GA24997@zxy.spb.ru> Date: Mon, 28 Oct 2013 10:45:02 -0700 Content-Transfer-Encoding: 7bit Message-Id: <0F1D571E-2806-4392-A5EC-BE66A3C92BF7@gmail.com> References: <20131028092844.GA24997@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1085) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 17:45:05 -0000 On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov wrote: > I can be wrong. > As I see ZFS cretate seperate thread for earch txg writing. > Also for writing to L2ARC. > As result -- up to several thousands threads created and destoyed per > second. And hundreds thousands page allocations, zeroing, maping > unmaping and freeing per seconds. Very high overhead. > > In systat -vmstat I see totfr up to 600000, prcfr up to 200000. > > Estimated overhead -- 30% of system time. > > Can anybody implement thread and page pool for txg? Would lowering vfs.zfs.txg.timeout be a way to tame or mitigate this? - aurf From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 18:14:34 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B07EADB; Mon, 28 Oct 2013 18:14:34 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id ED389226C; Mon, 28 Oct 2013 18:14:33 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VarMd-000I4J-NG; Mon, 28 Oct 2013 22:16:31 +0400 Date: Mon, 28 Oct 2013 22:16:31 +0400 From: Slawa Olhovchenkov To: aurfalien Subject: Re: ZFS txg implementation flaw Message-ID: <20131028181631.GV63359@zxy.spb.ru> References: <20131028092844.GA24997@zxy.spb.ru> <0F1D571E-2806-4392-A5EC-BE66A3C92BF7@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0F1D571E-2806-4392-A5EC-BE66A3C92BF7@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 18:14:34 -0000 On Mon, Oct 28, 2013 at 10:45:02AM -0700, aurfalien wrote: > > On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov wrote: > > > I can be wrong. > > As I see ZFS cretate seperate thread for earch txg writing. > > Also for writing to L2ARC. > > As result -- up to several thousands threads created and destoyed per > > second. And hundreds thousands page allocations, zeroing, maping > > unmaping and freeing per seconds. Very high overhead. > > > > In systat -vmstat I see totfr up to 600000, prcfr up to 200000. > > > > Estimated overhead -- 30% of system time. > > > > Can anybody implement thread and page pool for txg? > > Would lowering vfs.zfs.txg.timeout be a way to tame or mitigate this? vfs.zfs.txg.timeout: 5 Only x5 lowering (less in real case with burst writing). And more fragmentation on writing and etc. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 18:25:27 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5169E813; Mon, 28 Oct 2013 18:25:27 +0000 (UTC) (envelope-from aurfalien@gmail.com) Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 242212353; Mon, 28 Oct 2013 18:25:27 +0000 (UTC) Received: by mail-pb0-f50.google.com with SMTP id uo5so4779806pbc.37 for ; Mon, 28 Oct 2013 11:25:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/P2Ss+Z1ml4fOoiue5EKRevYEqLdRZ+6YdZQOXIvelI=; b=VDl+P+9vfxcfk/2S9OChqIElWNtrZM37VgHP5A/g4HKbmtkl9adaNr90382G/pqJ6w suuSky+V1AvLYqtyn4vlEDI5i6tyCoWPq7HnAd3MZw6I6J+NY7NmUK7VqISC43pWiOSL jE1SSItGphRXXV8Lw01Nucn0tSD1NVTWCovuaK8wvKcQJOHAJG8SIyskjF5YO+fGEIRb OdMnJ6bfFGT1o7rWg54/suxvPOnmI9LE4Kh+DtuU5Y3ueYWq/HquYRDWlg3NPUA9Gzm9 RsyNqEE/ZGT01e2Q2U0nvVigaw+cuHQUIhrEreYRsU9YKLi2w5f821qv8uM9uLLIK06r 8/wA== X-Received: by 10.68.235.72 with SMTP id uk8mr17585581pbc.93.1382984726746; Mon, 28 Oct 2013 11:25:26 -0700 (PDT) Received: from briankrusicw.logan.tv ([64.17.255.138]) by mx.google.com with ESMTPSA id lm2sm36883671pab.2.2013.10.28.11.25.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Oct 2013 11:25:26 -0700 (PDT) Subject: Re: ZFS txg implementation flaw Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: aurfalien In-Reply-To: <20131028181631.GV63359@zxy.spb.ru> Date: Mon, 28 Oct 2013 11:25:25 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20131028092844.GA24997@zxy.spb.ru> <0F1D571E-2806-4392-A5EC-BE66A3C92BF7@gmail.com> <20131028181631.GV63359@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1085) Cc: freebsd-fs , freebsd-current@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 18:25:27 -0000 On Oct 28, 2013, at 11:16 AM, Slawa Olhovchenkov wrote: > On Mon, Oct 28, 2013 at 10:45:02AM -0700, aurfalien wrote: >=20 >>=20 >> On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov wrote: >>=20 >>> I can be wrong. >>> As I see ZFS cretate seperate thread for earch txg writing. >>> Also for writing to L2ARC. >>> As result -- up to several thousands threads created and destoyed = per >>> second. And hundreds thousands page allocations, zeroing, maping >>> unmaping and freeing per seconds. Very high overhead. >>>=20 >>> In systat -vmstat I see totfr up to 600000, prcfr up to 200000. >>>=20 >>> Estimated overhead -- 30% of system time. >>>=20 >>> Can anybody implement thread and page pool for txg? >>=20 >> Would lowering vfs.zfs.txg.timeout be a way to tame or mitigate this? >=20 > vfs.zfs.txg.timeout: 5 >=20 > Only x5 lowering (less in real case with burst writing). And more = fragmentation on writing and etc. So leave it default in other words. Good to know. - aurf From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 18:36:42 2013 Return-Path: Delivered-To: freebsd-fs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D316E202; Mon, 28 Oct 2013 18:36:42 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A72592437; Mon, 28 Oct 2013 18:36:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9SIagWh062757; Mon, 28 Oct 2013 18:36:42 GMT (envelope-from pfg@freefall.freebsd.org) Received: (from pfg@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9SIagYn062756; Mon, 28 Oct 2013 18:36:42 GMT (envelope-from pfg) Date: Mon, 28 Oct 2013 18:36:42 GMT Message-Id: <201310281836.r9SIagYn062756@freefall.freebsd.org> To: pfg@FreeBSD.org, freebsd-fs@FreeBSD.org, pfg@FreeBSD.org From: pfg@FreeBSD.org Subject: Re: kern/183230: [ext2fs] ext2fs hash function incompatible with linux X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 18:36:42 -0000 Synopsis: [ext2fs] ext2fs hash function incompatible with linux Responsible-Changed-From-To: freebsd-fs->pfg Responsible-Changed-By: pfg Responsible-Changed-When: Mon Oct 28 18:34:51 UTC 2013 Responsible-Changed-Why: I will take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=183230 From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 21:22:18 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3725B650; Mon, 28 Oct 2013 21:22:18 +0000 (UTC) (envelope-from jkh@ixsystems.com) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 17C3B2F72; Mon, 28 Oct 2013 21:22:17 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id 74A1864E86; Mon, 28 Oct 2013 14:22:17 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 03121-05; Mon, 28 Oct 2013 14:22:17 -0700 (PDT) Received: from kruse-49.3.ixsystems.com (kruse-49.3.ixsystems.com [10.2.3.49]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id C568264E7E; Mon, 28 Oct 2013 14:22:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1382995337; bh=Tc+T0xy794JoySftCRqrdMHTWgd1lQY92gZ8PAZ0mBo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=GENb2RmIJQh83sGRYHsZUWC8uRUgW7ZGDupA/vyCPIXx2lA/v4mhgDTBHK/FRZDFF jTgmTRG35dMPGXgB1FJpoCDeTyDa0vLnxZnp51rWIwjGTm+F4k2us2APQa9394Om7c K0HdBQ5P7rTsBrrs5Vgx1gOvcZx/H4adhIhLvWW4= Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: ZFS txg implementation flaw From: Jordan Hubbard In-Reply-To: <20131028092844.GA24997@zxy.spb.ru> Date: Mon, 28 Oct 2013 14:22:16 -0700 Message-Id: <9A00B135-7D28-47EB-ADB3-E87C38BAC6B6@ixsystems.com> References: <20131028092844.GA24997@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1816) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 21:22:18 -0000 On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov wrote: > As I see ZFS cretate seperate thread for earch txg writing. > Also for writing to L2ARC. > As result -- up to several thousands threads created and destoyed per > second. And hundreds thousands page allocations, zeroing, maping > unmaping and freeing per seconds. Very high overhead. How are you measuring the number of threads being created / destroyed? = This claim seems erroneous given how the ZFS thread pool mechanism = actually works (and yes, there are thread pools already). It would be helpful to both see your measurement methodology and the = workload you are using in your tests. - Jordan From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 21:30:07 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A07D4E08; Mon, 28 Oct 2013 21:30:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 5EBE32FEE; Mon, 28 Oct 2013 21:30:07 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VauPs-000PCK-GJ; Tue, 29 Oct 2013 01:32:04 +0400 Date: Tue, 29 Oct 2013 01:32:04 +0400 From: Slawa Olhovchenkov To: Jordan Hubbard Subject: Re: ZFS txg implementation flaw Message-ID: <20131028213204.GX63359@zxy.spb.ru> References: <20131028092844.GA24997@zxy.spb.ru> <9A00B135-7D28-47EB-ADB3-E87C38BAC6B6@ixsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9A00B135-7D28-47EB-ADB3-E87C38BAC6B6@ixsystems.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 21:30:07 -0000 On Mon, Oct 28, 2013 at 02:22:16PM -0700, Jordan Hubbard wrote: > > On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov wrote: > > > As I see ZFS cretate seperate thread for earch txg writing. > > Also for writing to L2ARC. > > As result -- up to several thousands threads created and destoyed per > > second. And hundreds thousands page allocations, zeroing, maping > > unmaping and freeing per seconds. Very high overhead. > > How are you measuring the number of threads being created / destroyed? This claim seems erroneous given how the ZFS thread pool mechanism actually works (and yes, there are thread pools already). > > It would be helpful to both see your measurement methodology and the workload you are using in your tests. Semi-indirect. dtrace -n 'fbt:kernel:vm_object_terminate:entry { @traces[stack()] = count(); }' After some (2-3) seconds kernel`vnode_destroy_vobject+0xb9 zfs.ko`zfs_freebsd_reclaim+0x2e kernel`VOP_RECLAIM_APV+0x78 kernel`vgonel+0x134 kernel`vnlru_free+0x362 kernel`vnlru_proc+0x61e kernel`fork_exit+0x11f kernel`0xffffffff80cdbfde 2490 I don't have user process created threads nor do fork/exit. From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 21:38:31 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 978AA9FC; Mon, 28 Oct 2013 21:38:31 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7D64D20E4; Mon, 28 Oct 2013 21:38:31 +0000 (UTC) Received: from zeta.ixsystems.com (unknown [69.198.165.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id AF3422A44F; Mon, 28 Oct 2013 14:38:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1382996310; bh=O9C7UuDP78lPI+TJ6kI6phwkDDKMfut4Q5OH4eFW57M=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=RU7IcZpomYUQfPJuORtmudu4OwehlrKv6NesTAUvZ67QFrnYaeXfnEzXMHgMMWl5h ibHfpSmf8vJ5RAK9yp9yGdEBLHKI+v3WgPavy/Yqh4fzCkXnUzr0vkTThCQ01v5uSt nikusMECBknDInZzRXWIL3OGNtNeXQOzhVC+ptos= Message-ID: <526ED956.10202@delphij.net> Date: Mon, 28 Oct 2013 14:38:30 -0700 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Slawa Olhovchenkov , Jordan Hubbard Subject: Re: ZFS txg implementation flaw References: <20131028092844.GA24997@zxy.spb.ru> <9A00B135-7D28-47EB-ADB3-E87C38BAC6B6@ixsystems.com> <20131028213204.GX63359@zxy.spb.ru> In-Reply-To: <20131028213204.GX63359@zxy.spb.ru> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 21:38:31 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 10/28/13 14:32, Slawa Olhovchenkov wrote: > On Mon, Oct 28, 2013 at 02:22:16PM -0700, Jordan Hubbard wrote: > >> >> On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov >> wrote: >> >>> As I see ZFS cretate seperate thread for earch txg writing. >>> Also for writing to L2ARC. As result -- up to several thousands >>> threads created and destoyed per second. And hundreds thousands >>> page allocations, zeroing, maping unmaping and freeing per >>> seconds. Very high overhead. >> >> How are you measuring the number of threads being created / >> destroyed? This claim seems erroneous given how the ZFS thread >> pool mechanism actually works (and yes, there are thread pools >> already). >> >> It would be helpful to both see your measurement methodology and >> the workload you are using in your tests. > > Semi-indirect. dtrace -n 'fbt:kernel:vm_object_terminate:entry { > @traces[stack()] = count(); }' > > After some (2-3) seconds > > kernel`vnode_destroy_vobject+0xb9 zfs.ko`zfs_freebsd_reclaim+0x2e > kernel`VOP_RECLAIM_APV+0x78 kernel`vgonel+0x134 > kernel`vnlru_free+0x362 kernel`vnlru_proc+0x61e > kernel`fork_exit+0x11f kernel`0xffffffff80cdbfde 2490 > > I don't have user process created threads nor do fork/exit. This has nothing to do with fork/exit but does suggest that you are running of vnodes. What does sysctl -a | grep vnode say? Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJSbtlWAAoJEJW2GBstM+ns1BgP/iD89HXV3g/c4/GliMG27yB0 WMoWJVDvHmzvRuHBMC6rUIqvyfSaK4EdFDK2jYUIM9qQwWcrSXRXIDBLNE/5MHwl FgcsaBlFaE17bMwzWrZRCzSb1YMxHXmHG5e10YrGUW8TKkGBVtDD6SIMVK8xg6SQ 5HM2HJR8BVaB65z4S1tLxA+VIqHitUZ0/kTME6X1Z+Y/CwS29F+seXk1DlDYNZM3 W3UVTxJnVwf9HhHRvx/kDtPIPeuIz0O/M5cgtbYq78wjG9Zim6a8SWpuxKeduDoT CTllgyEidc+vtDiEiksRsja3ATwynzjLGlNribnMKP2U4KMu9qfVUXDse3wwKKXa +f9Yfzg+fif3r6d/hdlQCtHJhjNlqfjDjCXHHpuTftLU2ONpj9hwKYKOqp6ykmt9 Ok2QziXqBxRMVXJjDAOybv8P1zCAcTpRtvR25bbE7T0M49dvVw51CdAdX8m8nJR+ tX72r+j4BeoNflQWqSsG8P9ao3AuOk6jGgXdtngbbpteyplaVqLragFo8shfUNmY dWaJp46wUq3gaRBSO/4CkzdyWl99eTTOAW4/Zr78LuYT5wN7FL590AAT3Jmc9N4Z edZsR2a8VwluLAVuJNqf9odg7MW03xxjKKf9Wm/I112XtFHDg/dCIrdf4cWc5iuA SvGKci6yZfy5e6hj+ZH5 =aVMu -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 21:43:56 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CC6EC2DF; Mon, 28 Oct 2013 21:43:56 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 8858A2166; Mon, 28 Oct 2013 21:43:56 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VaudE-000POV-Qi; Tue, 29 Oct 2013 01:45:52 +0400 Date: Tue, 29 Oct 2013 01:45:52 +0400 From: Slawa Olhovchenkov To: d@delphij.net Subject: Re: ZFS txg implementation flaw Message-ID: <20131028214552.GY63359@zxy.spb.ru> References: <20131028092844.GA24997@zxy.spb.ru> <9A00B135-7D28-47EB-ADB3-E87C38BAC6B6@ixsystems.com> <20131028213204.GX63359@zxy.spb.ru> <526ED956.10202@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <526ED956.10202@delphij.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Jordan Hubbard X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 21:43:56 -0000 On Mon, Oct 28, 2013 at 02:38:30PM -0700, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 10/28/13 14:32, Slawa Olhovchenkov wrote: > > On Mon, Oct 28, 2013 at 02:22:16PM -0700, Jordan Hubbard wrote: > > > >> > >> On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov > >> wrote: > >> > >>> As I see ZFS cretate seperate thread for earch txg writing. > >>> Also for writing to L2ARC. As result -- up to several thousands > >>> threads created and destoyed per second. And hundreds thousands > >>> page allocations, zeroing, maping unmaping and freeing per > >>> seconds. Very high overhead. > >> > >> How are you measuring the number of threads being created / > >> destroyed? This claim seems erroneous given how the ZFS thread > >> pool mechanism actually works (and yes, there are thread pools > >> already). > >> > >> It would be helpful to both see your measurement methodology and > >> the workload you are using in your tests. > > > > Semi-indirect. dtrace -n 'fbt:kernel:vm_object_terminate:entry { > > @traces[stack()] = count(); }' > > > > After some (2-3) seconds > > > > kernel`vnode_destroy_vobject+0xb9 zfs.ko`zfs_freebsd_reclaim+0x2e > > kernel`VOP_RECLAIM_APV+0x78 kernel`vgonel+0x134 > > kernel`vnlru_free+0x362 kernel`vnlru_proc+0x61e > > kernel`fork_exit+0x11f kernel`0xffffffff80cdbfde 2490 0xffffffff80cdbfd0 : mov %r12,%rdi 0xffffffff80cdbfd3 : mov %rbx,%rsi 0xffffffff80cdbfd6 : mov %rsp,%rdx 0xffffffff80cdbfd9 : callq 0xffffffff808db560 0xffffffff80cdbfde : jmpq 0xffffffff80cdca80 0xffffffff80cdbfe3 : nopw 0x0(%rax,%rax,1) 0xffffffff80cdbfe9 : nopl 0x0(%rax) > > I don't have user process created threads nor do fork/exit. > > This has nothing to do with fork/exit but does suggest that you are > running of vnodes. What does sysctl -a | grep vnode say? kern.maxvnodes: 1095872 kern.minvnodes: 273968 vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_vnodepgsin: 62399 vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodein: 10680 vfs.freevnodes: 275107 vfs.wantfreevnodes: 273968 vfs.numvnodes: 316321 debug.sizeof.vnode: 504 From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 21:56:18 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0BBCB8B4; Mon, 28 Oct 2013 21:56:18 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CD5452244; Mon, 28 Oct 2013 21:56:17 +0000 (UTC) Received: from zeta.ixsystems.com (unknown [69.198.165.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 6A10A2A681; Mon, 28 Oct 2013 14:56:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1382997377; bh=hFDiaefO6Vyv9Pm+hXXEAYlFoqxtdxhMDc9lG75NM9c=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=xhA5qE177C3gHdztxLSH5p+1SGKeOpuA1GwDjWdDcKh4My6TyG1xOA8ldbbw/RrjN jMzfYFLxPEjb3ZQGfKA3O6GDAQeu6nRd/mA9XQRieOcxitCAeBSg3hxNJuJXKL10Rb 5IaesbjzSiHAS+5wjp1Bfm57SaYsXOpoNzF+aQQ8= Message-ID: <526EDD81.8000109@delphij.net> Date: Mon, 28 Oct 2013 14:56:17 -0700 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Slawa Olhovchenkov , d@delphij.net Subject: Re: ZFS txg implementation flaw References: <20131028092844.GA24997@zxy.spb.ru> <9A00B135-7D28-47EB-ADB3-E87C38BAC6B6@ixsystems.com> <20131028213204.GX63359@zxy.spb.ru> <526ED956.10202@delphij.net> <20131028214552.GY63359@zxy.spb.ru> In-Reply-To: <20131028214552.GY63359@zxy.spb.ru> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Jordan Hubbard X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 21:56:18 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 10/28/13 14:45, Slawa Olhovchenkov wrote: > On Mon, Oct 28, 2013 at 02:38:30PM -0700, Xin Li wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >> >> On 10/28/13 14:32, Slawa Olhovchenkov wrote: >>> On Mon, Oct 28, 2013 at 02:22:16PM -0700, Jordan Hubbard >>> wrote: >>> >>>> >>>> On Oct 28, 2013, at 2:28 AM, Slawa Olhovchenkov >>>> wrote: >>>> >>>>> As I see ZFS cretate seperate thread for earch txg writing. >>>>> Also for writing to L2ARC. As result -- up to several >>>>> thousands threads created and destoyed per second. And >>>>> hundreds thousands page allocations, zeroing, maping >>>>> unmaping and freeing per seconds. Very high overhead. >>>> >>>> How are you measuring the number of threads being created / >>>> destroyed? This claim seems erroneous given how the ZFS >>>> thread pool mechanism actually works (and yes, there are >>>> thread pools already). >>>> >>>> It would be helpful to both see your measurement methodology >>>> and the workload you are using in your tests. >>> >>> Semi-indirect. dtrace -n 'fbt:kernel:vm_object_terminate:entry >>> { @traces[stack()] = count(); }' >>> >>> After some (2-3) seconds >>> >>> kernel`vnode_destroy_vobject+0xb9 >>> zfs.ko`zfs_freebsd_reclaim+0x2e kernel`VOP_RECLAIM_APV+0x78 >>> kernel`vgonel+0x134 kernel`vnlru_free+0x362 >>> kernel`vnlru_proc+0x61e kernel`fork_exit+0x11f >>> kernel`0xffffffff80cdbfde 2490 > > 0xffffffff80cdbfd0 : mov %r12,%rdi > 0xffffffff80cdbfd3 : mov %rbx,%rsi > 0xffffffff80cdbfd6 : mov %rsp,%rdx > 0xffffffff80cdbfd9 : callq 0xffffffff808db560 > 0xffffffff80cdbfde : jmpq > 0xffffffff80cdca80 0xffffffff80cdbfe3 > : nopw 0x0(%rax,%rax,1) > 0xffffffff80cdbfe9 : nopl 0x0(%rax) > > >>> I don't have user process created threads nor do fork/exit. >> >> This has nothing to do with fork/exit but does suggest that you >> are running of vnodes. What does sysctl -a | grep vnode say? > > kern.maxvnodes: 1095872 kern.minvnodes: 273968 > vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_vnodepgsin: 62399 > vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodein: 10680 > vfs.freevnodes: 275107 vfs.wantfreevnodes: 273968 vfs.numvnodes: > 316321 debug.sizeof.vnode: 504 Try setting vfs.wantfreevnodes to 547936 (double it). Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJSbt2BAAoJEJW2GBstM+nsknMP/1QQQ0BHJOu//nG2M2HnYGsQ bS0he2xdom/GpPuMS3AwGYYwZTWwauGwr3c2K4czW5AzghNDxpVfycobuGeWVvcB mvyBgkGhxy33nxVuw9hH4FJW62vJc9sJKlgg5QNQhER81OpCBS2AcVv7qNNtj9f6 svZrhu6X28maas+JnwSr5U82gudC1uhHD3h1pZqc+ogFiEgHlQOoL3Pl6SrpTKUZ WNFnKd9xWQ/28n26r+jzQu9SlTSStKNQcZiCsMO/5TcGs6Ul8Ft2pS0EKYvVMdVF poPLItT7qa38nM9BXZYNiESIoZpe1coYXX0en6NMTa0q7JerN05tk3d8q31Rn/Hp toodJuZB8zA+ZN732s295G06j9gDbSj/iFLumV/0s9OHMVT5lgqVjxmPurmjE+ay nnPrTDpO3Ef45nC6Gb87yN2ML2GG40de5kYWtieLFt5aSJhQjvmDA+zOxdC9orrh raspOHfgysvSh8ykaS9SsNdzgEJr5TTzbxh91Ft06e65TEdIzX9HhnqxOLBT+lC1 E6OKYVuU1rLjZPPTplCFI922JbyKEhSc73Gu03zPma8cJEzP/ztCxm/Jv0PrV+4b SzphVQdMbUr2TMKAUIJXcCwHSWhCCCCmqmODoDcHoTbC0kBAqyAbaTCZ8PJaR/A8 jxbZvQV8dGjSYu0LVhnT =3Xt/ -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Mon Oct 28 22:24:54 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 88753BD7; Mon, 28 Oct 2013 22:24:54 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 43E152428; Mon, 28 Oct 2013 22:24:53 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VavGt-0000xC-2x; Tue, 29 Oct 2013 02:26:51 +0400 Date: Tue, 29 Oct 2013 02:26:51 +0400 From: Slawa Olhovchenkov To: d@delphij.net Subject: Re: ZFS txg implementation flaw Message-ID: <20131028222651.GZ63359@zxy.spb.ru> References: <20131028092844.GA24997@zxy.spb.ru> <9A00B135-7D28-47EB-ADB3-E87C38BAC6B6@ixsystems.com> <20131028213204.GX63359@zxy.spb.ru> <526ED956.10202@delphij.net> <20131028214552.GY63359@zxy.spb.ru> <526EDD81.8000109@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <526EDD81.8000109@delphij.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Jordan Hubbard X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 22:24:54 -0000 On Mon, Oct 28, 2013 at 02:56:17PM -0700, Xin Li wrote: > >>> Semi-indirect. dtrace -n 'fbt:kernel:vm_object_terminate:entry > >>> { @traces[stack()] = count(); }' > >>> > >>> After some (2-3) seconds > >>> > >>> kernel`vnode_destroy_vobject+0xb9 > >>> zfs.ko`zfs_freebsd_reclaim+0x2e kernel`VOP_RECLAIM_APV+0x78 > >>> kernel`vgonel+0x134 kernel`vnlru_free+0x362 > >>> kernel`vnlru_proc+0x61e kernel`fork_exit+0x11f > >>> kernel`0xffffffff80cdbfde 2490 > > > > 0xffffffff80cdbfd0 : mov %r12,%rdi > > 0xffffffff80cdbfd3 : mov %rbx,%rsi > > 0xffffffff80cdbfd6 : mov %rsp,%rdx > > 0xffffffff80cdbfd9 : callq 0xffffffff808db560 > > 0xffffffff80cdbfde : jmpq > > 0xffffffff80cdca80 0xffffffff80cdbfe3 > > : nopw 0x0(%rax,%rax,1) > > 0xffffffff80cdbfe9 : nopl 0x0(%rax) > > > > > >>> I don't have user process created threads nor do fork/exit. > >> > >> This has nothing to do with fork/exit but does suggest that you > >> are running of vnodes. What does sysctl -a | grep vnode say? > > > > kern.maxvnodes: 1095872 kern.minvnodes: 273968 > > vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_vnodepgsin: 62399 > > vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodein: 10680 > > vfs.freevnodes: 275107 vfs.wantfreevnodes: 273968 vfs.numvnodes: > > 316321 debug.sizeof.vnode: 504 > > Try setting vfs.wantfreevnodes to 547936 (double it). Now fork_trampoline was gone, but I still see prcfr (and zfod/totfr too). Currently half of peeak traffic and I can't check impact to IRQ handling. kern.maxvnodes: 1095872 kern.minvnodes: 547936 vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_vnodepgsin: 63134 vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodein: 10836 vfs.freevnodes: 481873 vfs.wantfreevnodes: 547936 vfs.numvnodes: 517331 debug.sizeof.vnode: 504 Now dtrace -n 'fbt:kernel:vm_object_terminate:entry { @traces[stack()] = count(); }' kernel`vm_object_deallocate+0x520 kernel`vm_map_entry_deallocate+0x4c kernel`vm_map_process_deferred+0x3d kernel`sys_munmap+0x16c kernel`amd64_syscall+0x5ea kernel`0xffffffff80cdbd97 56 I think this is nginx memory management (allocation|dealocation). Can I tune malloc to disable free pages? From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 07:28:27 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 13A5F5EC for ; Tue, 29 Oct 2013 07:28:27 +0000 (UTC) (envelope-from alex.wilkinson@cba.com.au) Received: from igw12blk.cba.com.au (igwx12.cba.com.au [140.168.71.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7D56F2FB7 for ; Tue, 29 Oct 2013 07:28:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cba.com.au; i=@cba.com.au; q=dns/txt; s=CBAdkim-110609; t=1383031706; x=1698391706; h=date:from:to:subject:message-id:mime-version; bh=F5nG2ua62MfRZP928i9y5itlGcy65GdbhA6q5ai8DTk=; b=daDRqaunsstXNF7dMXD6olluguMIG86hhQ0C7mtAmrOHdnEM5zxEg+pw Ho3hY+v+gEssS/bgQPn56gQcrGUICA==; X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.93,591,1378821600"; d="scan'208";a="75458985" Received: from unknown (HELO aaunswc27.au.cbainet.com) ([10.30.10.34]) by igw12.cba.com.au with ESMTP; 29 Oct 2013 18:27:13 +1100 Received: from margz.perth.internal ([10.138.102.216]) by aaunswc27.au.cbainet.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 29 Oct 2013 18:27:13 +1100 Date: Tue, 29 Oct 2013 18:27:08 +1100 From: "Wilkinson, Alex" To: freebsd-fs@freebsd.org Subject: HAST - Unable to receive request header: Socket is not connected (10.0-BETA1) Message-ID: <20131029072708.GC86932@margz.perth.internal> Mail-Followup-To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organisation: Commonwealth Bank Australia X-Message-Flag: "Please Restore Line Breaks If Necessary" User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginalArrivalTime: 29 Oct 2013 07:27:13.0310 (UTC) FILETIME=[4968EBE0:01CED478] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 07:28:27 -0000 Hi all, Using FreeBSD 10.0-BETA1, setting up a HAST cluster as such: listen tcp://0.0.0.0 on host-a { listen tcp4://172.18.3.11 } on host-b { listen tcp4://172.18.3.12 } resource export { on host-a { local /dev/mfid0p4 remote tcp4://172.18.3.12 } on host-b { local /dev/mfid0p4 remote tcp4://172.18.3.11 } } Running hastd in foreground + debug on primary I see: [DEBUG][2] Checking hooks. [DEBUG][2] [export] (primary) remote_send: Taking request. [DEBUG][2] [export] (primary) remote_guard: Checking connections. [DEBUG][2] Checking hooks. [DEBUG][2] [export] (primary) remote_guard: Reconnecting to tcp4://172.18.3.12. [DEBUG][1] [export] (primary) Negotiated protocol version 2. [WARNING] [export] (primary) Data size differs between nodes (local=128819612160, remote=128848941568). [DEBUG][2] [export] (primary) remote_guard: Reconnect to tcp4://172.18.3.12 failed. [DEBUG][2] Checking hooks. [DEBUG][2] Checking hooks. [DEBUG][2] [export] (primary) remote_send: Taking request. [DEBUG][2] [export] (primary) remote_guard: Checking connections. [DEBUG][2] [export] (primary) remote_guard: Reconnecting to tcp4://172.18.3.12. [DEBUG][1] [export] (primary) Negotiated protocol version 2. [WARNING] [export] (primary) Data size differs between nodes (local=128819612160, remote=128848941568). [DEBUG][2] [export] (primary) remote_guard: Reconnect to tcp4://172.18.3.12 failed. Running hastd in foreground + debug on secondary I see: [INFO] Connection from tcp://172.18.3.11:41306 to tcp://172.18.3.12:8457. [DEBUG][2] tcp://172.18.3.11:41306: resource=export [DEBUG][2] tcp://172.18.3.11:41306: version=0 [DEBUG][1] Negotiated protocol version 1. [DEBUG][1] [export] (secondary) Outgoing connection to tcp://172.18.3.11:41306 configured. [DEBUG][1] [export] (secondary) Obtained info about /dev/mfid0p4. [DEBUG][1] [export] (secondary) Locked /dev/mfid0p4. [DEBUG][1] [export] (secondary) Privileges successfully dropped using capsicum+jail+setgid+setuid. [INFO] [export] (secondary) Privileges successfully dropped. [DEBUG][2] [export] (secondary) [DEBUG][2]disk: Taking request. [DEBUG][2] [export] (secondary) recv: Taking free request. [DEBUG][2] [export] (secondary) recv: (0x80204a330) Got request. [export] (secondary) send: Taking request. [ERROR] [export] (secondary) Unable to receive request header: Socket is not connected. [DEBUG][1] Unable to receive event header: Socket is not connected. [DEBUG][2] Checking hooks. [ERROR] [export] (secondary) Worker process exited ungracefully (pid=2341, exitcode=75). I can successfully open a socket via netcat. Any ideas ? -Alex ************** IMPORTANT MESSAGE ***************************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ************************************************************** From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 09:54:17 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E47836AF for ; Tue, 29 Oct 2013 09:54:16 +0000 (UTC) (envelope-from cjpugmed@gmail.com) Received: from mail-vb0-x233.google.com (mail-vb0-x233.google.com [IPv6:2607:f8b0:400c:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A4FC32811 for ; Tue, 29 Oct 2013 09:54:16 +0000 (UTC) Received: by mail-vb0-f51.google.com with SMTP id x16so6388481vbf.10 for ; Tue, 29 Oct 2013 02:54:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iujCJMjsBCzzB3oMRN+Wqk02rf+CaUO66NPOTLVX/lI=; b=DruDfSTIu41wTr5Ev5rwuid+rLtDXVj7pzm/OpBpTLwh3yhxNhYxiCMIPfBS/kHV+o 2AOozosfB4Mw73WBfRhy7aHSHXYL/MoNVH/7j14RJk6Fnjw+oiynxcvacFRSBIuuZ/0q bGXBDjrPOyPYC7J5K6Iuj84rk2/0PWICYs24XC2NVNzUFrWvzzvR/h2liDZwprnZvCzj 2Mw1/vAEMXh1imRELRt4ZDIu/kTsB3QgpgWEOjfvLZv3d3Vn54SbobOPG3TG+hPaYqnn oH5+8TgQs978Ogsd268EWU0MRy18gI2ia3E3kCLs+qKIsZvkxEPC65SrKICYxJKy/Eaq PIwA== MIME-Version: 1.0 X-Received: by 10.58.38.200 with SMTP id i8mr16326074vek.6.1383040455647; Tue, 29 Oct 2013 02:54:15 -0700 (PDT) Received: by 10.220.1.17 with HTTP; Tue, 29 Oct 2013 02:54:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 29 Oct 2013 10:54:15 +0100 Message-ID: Subject: Re: fusefs-ntfs crashes on FreeBSD 9.2 From: Carlos Jacobo Puga Medina To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 09:54:17 -0000 Seems to me that it doesn't load properly the new fuse filesystem. After some digging I was able to load it again. Since I load the module from /boot/loader.conf, now I can perform all operations on NTFS as before. 2013/10/28 Carlos Jacobo Puga Medina > I can mount properly a external USB hard disk, but when I try to copy/move > something the system crashes and it need a hard reset to recover. I just > installed an updated version of sysutils/fusefs-kmod [1] and it doesn't > solved the problem. I can not provide any information because after > blocking all the system there is no trace of logs. > > Does someone know what happens? > > [1] > http://lists.freebsd.org/pipermail/freebsd-hackers/2013-October/043519.html > From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 13:17:31 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 204E6DAB for ; Tue, 29 Oct 2013 13:17:31 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AE0CB265D for ; Tue, 29 Oct 2013 13:17:30 +0000 (UTC) Received: by mail-ee0-f43.google.com with SMTP id b47so2663377eek.16 for ; Tue, 29 Oct 2013 06:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=N40p25gECZewuhmwVYjxbWLrPsiIEBxrZ/Fj01KLbEw=; b=ARHPSJmivBwNa51LF0pByWUKjtCd991OJJzRWIyYWMmgkuDlHu+50k7PmER1ykOEmt YODiv2mLHVZU1hbgbKGoWpHP97qmikb5IDoKeB8xIY9I47vQ0rxKRStvQZA/5hbYlyKQ aE1cLyfvdi+n6iBuu5Q82m12ZGGbk8SwFrsf5AcJwg2W2C3PkvyqsDYumkdCiK6vBgxN kwbIIilcuoZ8KW53zTZXPJuutzzawyYZE/TtQhCjq1W6B0WLNLy9yxQlLuwb6u6C+roa je+y9G+2dBnh4J354RhARJ+MbI6vx6LOo9rMpbdbwFEKz7sHcV4Gqfd8v/UsVis8LF3T i94w== X-Received: by 10.14.6.73 with SMTP id 49mr1721014eem.117.1383052649101; Tue, 29 Oct 2013 06:17:29 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPSA id bn13sm70262466eeb.11.2013.10.29.06.17.27 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 29 Oct 2013 06:17:28 -0700 (PDT) Date: Tue, 29 Oct 2013 15:17:26 +0200 From: Mikolaj Golub To: freebsd-fs@freebsd.org Subject: Re: HAST - Unable to receive request header: Socket is not connected (10.0-BETA1) Message-ID: <20131029131612.GA43106@gmail.com> References: <20131029072708.GC86932@margz.perth.internal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131029072708.GC86932@margz.perth.internal> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 13:17:31 -0000 On Tue, Oct 29, 2013 at 06:27:08PM +1100, Wilkinson, Alex wrote: > [DEBUG][2] Checking hooks. > [DEBUG][2] [export] (primary) remote_send: Taking request. > [DEBUG][2] [export] (primary) remote_guard: Checking connections. > [DEBUG][2] Checking hooks. > [DEBUG][2] [export] (primary) remote_guard: Reconnecting to tcp4://172.18.3.12. > [DEBUG][1] [export] (primary) Negotiated protocol version 2. > [WARNING] [export] (primary) Data size differs between nodes (local=128819612160, remote=128848941568). It looks like you created resources of different size on differen nodes. If the primary detects media size mismatch it closes the connection. Does mfid0p4 size differs on host-a and host-b? If it does use -m option in `hastctl create' to specify the same size on both nodes. You can run `hastctl dump' (on both nodes) to see what HAST currently thinks about media size. > [ERROR] [export] (secondary) Unable to receive request header: Socket is not connected. This is a consequence of the primary closing the connection after detecting media size mismatch. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 13:48:09 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4632ED5E for ; Tue, 29 Oct 2013 13:48:09 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 18F462832 for ; Tue, 29 Oct 2013 13:48:09 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id qd12so13844936ieb.5 for ; Tue, 29 Oct 2013 06:48:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=d5sIlRahulkyAXOzkiukCCAuM1Ps40zOVRP445jlu+w=; b=I5Y2NqZLA+10iodyhScK/SJ5O5YNe9O7xXNdRh2NpQDlaF97OpT8JHh0b49aYzLaMA zeQV42ZfOkD/H27iGNS1dWW/NaTtF8gnOFAjAns+lohWpvVCM6kDxJ+sgChXx6fHR50V pLY8t/wtvoiFaGdy8Rh7wGIwczhIKLMPr7/Y1B+EeuGBYQg+M4f7NVpHfdi29aSt7zjj qPXQLOpR4gkLglKPMBdtMLC7k3Giwl/YXAcERrNXspQ3QS/nQWIFgukfwM9V1p5+uGC2 puPsenikvR+wXgNytafMgISKbHbfGnTGZtIFvBwulu6Af3SdpDZgPcKbNfVXUvfMloeY /6Cg== MIME-Version: 1.0 X-Received: by 10.43.80.67 with SMTP id zt3mr16894543icb.23.1383054488108; Tue, 29 Oct 2013 06:48:08 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.43.180.131 with HTTP; Tue, 29 Oct 2013 06:48:08 -0700 (PDT) In-Reply-To: References: Date: Tue, 29 Oct 2013 09:48:08 -0400 X-Google-Sender-Auth: Kj4zDwfjY9J33qbA0i1i1xEBALs Message-ID: Subject: Re: 9.2 + ZFS + i386 = panic: pmap_enter: attempted pmap_enter on 4MB page From: J David To: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 13:48:09 -0000 On Tue, Oct 15, 2013 at 11:17 AM, J David wrote: > This machine was rock solid under 8.4, but since upgrading to 9.2 it > has been a disaster. It crashes every few hours with "panic: > pmap_enter: attempted pmap_enter on 4MB page." In the absence of a fix, the best workaround we have found for this issue has been to set vm.pmap.pg_ps_enabled=0 in /boot/loader.conf. Thanks! From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 15:28:31 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9B8EEF77 for ; Tue, 29 Oct 2013 15:28:31 +0000 (UTC) (envelope-from proks@skylinetele.com) Received: from mail.sky.od.ua (relay.sky.od.ua [81.25.224.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 255752E99 for ; Tue, 29 Oct 2013 15:28:30 +0000 (UTC) Received: from relay.sky.od.ua (mail [81.25.224.8]) by mail.sky.od.ua (Postfix) with ESMTP id 6CC221069A6; Tue, 29 Oct 2013 17:20:58 +0200 (EET) X-Virus-Scanned: amavisd-new at sky.od.ua Received: from mail.sky.od.ua ([81.25.224.8]) by relay.sky.od.ua (relay.sky.od.ua [81.25.224.8]) (amavisd-new, port 10024) with ESMTP id PAVIzy9rxfzJ; Tue, 29 Oct 2013 17:20:55 +0200 (EET) Received: from logos.sky.od.ua (logos.sky.od.ua [81.25.224.11]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sky.od.ua (Postfix) with ESMTPS id 9646C1069A0; Tue, 29 Oct 2013 17:20:55 +0200 (EET) Message-ID: <526FD257.6010201@skylinetele.com> Date: Tue, 29 Oct 2013 17:20:55 +0200 From: "Prokofiev S.P." Organization: Skyline Telecom. User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Rick Macklem Subject: Re: Mapping POSIX ACLs to NFSv4 ACLs for Samba storage References: <317463358.40289383.1381537328684.JavaMail.root@uoguelph.ca> In-Reply-To: <317463358.40289383.1381537328684.JavaMail.root@uoguelph.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 15:28:31 -0000 Thank you for your answer. Sorry for my delay, I was very busy. In my opinion, if we don't take account of windows requirements of rule ordering, then draft proposes more or less correct solution. As for me there are two solutions of this problem. The first, create ufs on zvol and move data there. The second as you said as is a simple translation for my application, i. e. samba. In my example the solution could be look like this (it's formal and for compatibility with Windows applications ) : owner@:--------------:fd----:deny user:10015:-w-p---A---C--:fd----:deny user:10049:-w-p---A---C--:fd----:deny user:10072:-------A---C--:fd----:deny owner@:rwxpD-aA--cC-s:fd----:allow user:10015:r-x---a---c--s:fd----:allow user:10049:r-x---a---c--s:fd----:allow user:10072:rwxpD-a---c--s:fd----:allow group@:------a---c--s:fd----:allow group:10008:rwxpD-a---c--s:fd----:allow group:544:rwxpD-a---c--s:fd----:allow group:10131:r-x---a---c--s:fd----:allow everyone@:--------------:fd----:allow The last rule is deny rule for other groups. In common case the solution is more complicated of course. We should take count into that the groups could have the same users and moreover users of user's list could be members of these groups. Therefore we couldn't place all of deny rules in front of allow rules as that require Windows applications. On 12.10.2013 03:22, Rick Macklem wrote: > Prokofiev S.P. wrote: >> Hi all, >> >> I propose to talk about an issue. I have a task of moving data from >> UFS+ACLs storage to a ZFS pool. Dump/restrore is the best way. But >> only >> owner/owner_group is saved. I've written a Perl script to translate >> POSIX ACLs to NFSv4 ACLs. I referred to the last draft of it >> (http://tools.ietf.org/html/draft-iet...acl-mapping-05 >> ) to >> emulate >> POSIX behaviour of permissions. I got something like that, for >> instance: >> > It probably isn't of much help to you, but eventually the NFSv4 > working group realized that mapping between POSIX<->NFSv4 ACLs > wasn't possible. Those drafts were just failed attempts. > > Also, if you are going to put all deny ACEs before all allow > ACEs, then the deny ACEs must not specify anything that is > allowed by the allow ACEs. (I suspect you already know, but > the NFSv4 ACL is evaluated by testing each ACE in order and > any match for a deny ACE denies access and any matching allow ACE > allows access. As such, re-ordering ACEs in the ACL changes > the ACL's semantics.) > > Good luck with this. I do not believe there is a correct solution > in general, so all you can hope for is a simple translation > that captures enough semantics for your application. > > rick > >> Source directory on UFS: >> Code: >> >>> getfacl /zjail/ads/home/samba-old/docs/SECRETARY/CERTIFICATE/ >> # file: /zjail/ads/home/samba-old/docs/SECRETARY/CERTIFICATE/ >> # owner: 10051 >> # group: 513 >> user::rwx >> user:10015:r-x >> user:10049:r-x >> user:10072:rwx >> group::--- >> group:544:rwx >> group:10008:rwx >> group:10131:r-x >> mask::rwx >> other::--- >> >>> getfacl -d /zjail/ads/home/samba-old/docs/SECRETARY/CERTIFICATE/ >> # file: /zjail/ads/home/samba-old/docs/SECRETARY/CERTIFICATE/ >> # owner: 10051 >> # group: 513 >> user::rwx >> user:10015:r-x >> user:10049:r-x >> user:10072:rwx >> group::--- >> group:544:rwx >> group:10008:rwx >> group:10131:r-x >> mask::rwx >> other::--- >> >> Target directory on ZFS: >> Code: >> >> # getfacl /zjail/ads/home/samba-new/docs/SECRETARY/CERTIFICATE/ >> # file: /zjail/ads/home/samba-new/docs/SECRETARY/CERTIFICATE/ >> # owner: 10051 >> # group: 513 >> owner@:--------------:fd----:deny >> owner@:rwxpD-aA--cC-s:fd----:allow >> user:10015:-w-p---A---C--:fd----:deny >> user:10015:r-x---a---c--s:fd----:allow >> user:10049:-w-p---A---C--:fd----:deny >> user:10049:r-x---a---c--s:fd----:allow >> user:10072:-------A---C--:fd----:deny >> user:10072:rwxpD-a---c--s:fd----:allow >> group@:------a---c--s:fd----:allow >> group:10008:rwxpD-a---c--s:fd----:allow >> group:544:rwxpD-a---c--s:fd----:allow >> group:10131:r-x---a---c--s:fd----:allow >> group@:rwxp---A---C--:fd----:deny >> group:10008:-------A---C--:fd----:deny >> group:544:-------A---C--:fd----:deny >> group:10131:-w-p---A---C--:fd----:deny >> everyone@:rwxp---A---C--:fd----:deny >> everyone@:------a---c--s:fd----:allow >> >> I was happy, but Windows made me sad. When I tried to look at >> permissions of a file or a directory with a Windows file browser I >> had >> warning about ordering of permissions. Then I tried to edit >> permissions >> and allowed reordering and got this result of that: >> >> Code: >> >> getfacl /zjail/ads/home/samba-new/docs/SECRETARY/CERTIFICATE/ >> # file: /zjail/ads/home/samba-new/docs/SECRETARY/CERTIFICATE/ >> # owner: 10051 >> # group: 513 >> user:10015:-w-pD--A---C--:fd----:deny >> user:10049:-w-pD--A---C--:fd----:deny >> user:10072:-------A---C--:fd----:deny >> group@:rwxpD--A---C--:fd----:deny >> group:10008:-------A---C--:fd----:deny >> group:544:-------A---C--:fd----:deny >> group:10131:-w-pD--A---C--:fd----:deny >> everyone@:rwxpD--A---C--:fd----:deny <<<<<<<<< >> owner@:rwxpD-aA--cC--:fd----:allow >> user:10015:r-x---a---c---:fd----:allow >> user:10049:r-x---a---c---:fd----:allow >> user:10072:rwxpD-a---c---:fd----:allow >> group@:------a---c---:fd----:allow >> group:10008:rwxpD-a---c---:fd----:allow >> group:544:rwxpD-a---c---:fd----:allow >> group:10131:r-x---a---c---:fd----:allow >> everyone@:------a---c---:fd----:allow >> >> But it won't work, because of (everyone@:rwxpD--A---C--:fd----:deny). >> It's a mess. As it turned out according to >> http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx >> >> it's a rule of ordering of Windows permissions. >> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to"freebsd-fs-unsubscribe@freebsd.org" >> -- Prokofiev Sergiiproks@skylinetele.com System and Network Administrator, PROK-RIPE ISP Skyline Telecom Odessa, Ukraine From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 15:37:42 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 61979751 for ; Tue, 29 Oct 2013 15:37:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B2E712F6C for ; Tue, 29 Oct 2013 15:37:41 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA11919; Tue, 29 Oct 2013 17:37:39 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VbBMR-0005dU-2U; Tue, 29 Oct 2013 17:37:39 +0200 Message-ID: <526FD60B.6000101@FreeBSD.org> Date: Tue, 29 Oct 2013 17:36:43 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: J David , "freebsd-fs@freebsd.org" Subject: Re: 9.2 + ZFS + i386 = panic: pmap_enter: attempted pmap_enter on 4MB page References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 15:37:42 -0000 on 29/10/2013 15:48 J David said the following: > On Tue, Oct 15, 2013 at 11:17 AM, J David wrote: >> This machine was rock solid under 8.4, but since upgrading to 9.2 it >> has been a disaster. It crashes every few hours with "panic: >> pmap_enter: attempted pmap_enter on 4MB page." > > In the absence of a fix, the best workaround we have found for this > issue has been to set vm.pmap.pg_ps_enabled=0 in /boot/loader.conf. > And with that you are not getting any panic any more? What CPU do you have? Relevant lines from the beginning of dmesg will do. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed Oct 30 11:03:35 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7B89F80F for ; Wed, 30 Oct 2013 11:03:35 +0000 (UTC) (envelope-from vusa@tuxsystems.co.za) Received: from MOY07-NIX1.wadns.net (moy07-nix1.wadns.net [41.185.26.137]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9085026ED for ; Wed, 30 Oct 2013 11:03:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by MOY07-NIX1.wadns.net (Postfix) with ESMTP id 73F942245A for ; Wed, 30 Oct 2013 12:56:30 +0200 (SAST) X-Virus-Scanned: Debian amavisd-new at doggle.co.za Received: from MOY07-NIX1.wadns.net ([127.0.0.1]) by localhost (MOY07-NIX1.wadns.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OsSUHBYH75Lc for ; Wed, 30 Oct 2013 12:56:21 +0200 (SAST) Received: from [192.168.88.103] (105-208-135-83.access.mtnbusiness.co.za [105.208.135.83]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by MOY07-NIX1.wadns.net (Postfix) with ESMTPSA id 6BCE322432 for ; Wed, 30 Oct 2013 12:56:19 +0200 (SAST) From: Vusa Moyo Subject: zpool upgrade and lz4 compression. Message-Id: Date: Wed, 30 Oct 2013 12:56:10 +0200 To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) X-Mailer: Apple Mail (2.1816) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 11:03:35 -0000 Greetings all.=20 I=92ve upgraded 2 FreeBSD 9.0 servers to 9.2=20 FreeBSD qaMKSYSB01.sars.gov.za 9.2-RELEASE FreeBSD 9.2-RELEASE #0 = r255898: Thu Sep 26 22:50:31 UTC 2013 = root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 ..using the exact same procedure.=20 On Server 1, I successfully managed to upgrade the zpool=92s to the = version that supports lz4 compression. On Server 2, I do not have the option to upgrade the version of zfs.=20 [root@qaMKSYSB02 ~]# zfs upgrade This system is currently running ZFS filesystem version 5. All filesystems are formatted with the current version. [root@qaMKSYSB02 ~]# zfs upgrade -v The following filesystem versions are supported: VER DESCRIPTION --- -------------------------------------------------------- 1 Initial ZFS filesystem version 2 Enhanced directory entries 3 Case insensitive and File system unique identifier (FUID) 4 userquota, groupquota properties 5 System attributes For more information on a particular version, including supported = releases, see the ZFS Administration Guide. [root@qaMKSYSB02 ~]# zpool upgrade -v This system is currently running ZFS pool version 28. The following versions are supported: VER DESCRIPTION --- -------------------------------------------------------- 1 Initial ZFS version 2 Ditto blocks (replicated metadata) 3 Hot spares and double parity RAID-Z 4 zpool history 5 Compression using the gzip algorithm 6 bootfs pool property 7 Separate intent log devices 8 Delegated administration 9 refquota and refreservation properties 10 Cache devices 11 Improved scrub performance 12 Snapshot properties 13 snapused property 14 passthrough-x aclinherit 15 user/group space accounting 16 stmf property support 17 Triple-parity RAID-Z 18 Snapshot user holds 19 Log device removal 20 Compression using zle (zero-length encoding) 21 Deduplication 22 Received properties 23 Slim ZIL 24 System attributes 25 Improved scrub stats 26 Improved snapshot deletion performance 27 Improved snapshot creation performance 28 Multiple vdev replacements For more information on a particular version, including supported = releases, see the ZFS Administration Guide. [root@qaMKSYSB02 ~]# zpool upgrade =20 This system is currently running ZFS pool version 28. All pools are formatted using this version. [root@qaMKSYSB02 ~]#=20 I think the problem may lie in the=20 freebsd-update fetch=20 program.=20 [root@qaMKSYSB02 ~]# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 9.2-RELEASE from update2.freebsd.org... = done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree No updates needed to update system to 9.2-RELEASE-p1. [root@qaMKSYSB02 ~]#=20 mergemaster.mtree is not something I would have touched.=20 Any help to resolve the issue will be highly appreciated.=20 Regards Vusa From owner-freebsd-fs@FreeBSD.ORG Wed Oct 30 11:19:52 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E7EA9AD8 for ; Wed, 30 Oct 2013 11:19:51 +0000 (UTC) (envelope-from vusa@tuxsystems.co.za) Received: from MOY07-NIX1.wadns.net (moy07-nix1.wadns.net [41.185.26.137]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9A027DF for ; Wed, 30 Oct 2013 11:19:50 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by MOY07-NIX1.wadns.net (Postfix) with ESMTP id 145D12245A for ; Wed, 30 Oct 2013 13:19:47 +0200 (SAST) X-Virus-Scanned: Debian amavisd-new at doggle.co.za Received: from MOY07-NIX1.wadns.net ([127.0.0.1]) by localhost (MOY07-NIX1.wadns.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sw1Qyz8VPodz for ; Wed, 30 Oct 2013 13:19:39 +0200 (SAST) Received: from [192.168.88.103] (105-208-135-83.access.mtnbusiness.co.za [105.208.135.83]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by MOY07-NIX1.wadns.net (Postfix) with ESMTPSA id 6FFD522432 for ; Wed, 30 Oct 2013 13:19:38 +0200 (SAST) From: Vusa Moyo Message-Id: <9BBB6E32-AFDF-4B7B-A576-40D59658122B@tuxsystems.co.za> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: zpool upgrade and lz4 compression. Date: Wed, 30 Oct 2013 13:19:26 +0200 References: To: freebsd-fs@freebsd.org In-Reply-To: X-Mailer: Apple Mail (2.1816) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 11:19:52 -0000 To elaborate,=20 Server 1=20 [root@qaMKSYSB01 /mksysb/qasediap01]# zfs set compression=3Dlz4 = mksysb/qasediap01 [root@qaMKSYSB01 /mksysb/qasediap01]#=20 Server 2=20 [root@qaMKSYSB02 /var/db]# zfs set compression=3Dlz4 mksysb/qaiam05 cannot set property for 'mksysb/qaiam05': 'compression' must be one of = 'on | off | lzjb | gzip | gzip-[1-9] | zle' [root@qaMKSYSB02 /var/db]#=20 On 30 Oct 2013, at 12:56 PM, Vusa Moyo wrote: > Greetings all.=20 >=20 > I=92ve upgraded 2 FreeBSD 9.0 servers to 9.2=20 >=20 > FreeBSD qaMKSYSB01.sars.gov.za 9.2-RELEASE FreeBSD 9.2-RELEASE #0 = r255898: Thu Sep 26 22:50:31 UTC 2013 = root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >=20 >=20 > ..using the exact same procedure.=20 >=20 > On Server 1, I successfully managed to upgrade the zpool=92s to the = version that supports lz4 compression. >=20 > On Server 2, I do not have the option to upgrade the version of zfs.=20= >=20 >=20 > [root@qaMKSYSB02 ~]# zfs upgrade > This system is currently running ZFS filesystem version 5. >=20 > All filesystems are formatted with the current version. > [root@qaMKSYSB02 ~]# zfs upgrade -v > The following filesystem versions are supported: >=20 > VER DESCRIPTION > --- -------------------------------------------------------- > 1 Initial ZFS filesystem version > 2 Enhanced directory entries > 3 Case insensitive and File system unique identifier (FUID) > 4 userquota, groupquota properties > 5 System attributes >=20 > For more information on a particular version, including supported = releases, > see the ZFS Administration Guide. >=20 > [root@qaMKSYSB02 ~]# zpool upgrade -v > This system is currently running ZFS pool version 28. >=20 > The following versions are supported: >=20 > VER DESCRIPTION > --- -------------------------------------------------------- > 1 Initial ZFS version > 2 Ditto blocks (replicated metadata) > 3 Hot spares and double parity RAID-Z > 4 zpool history > 5 Compression using the gzip algorithm > 6 bootfs pool property > 7 Separate intent log devices > 8 Delegated administration > 9 refquota and refreservation properties > 10 Cache devices > 11 Improved scrub performance > 12 Snapshot properties > 13 snapused property > 14 passthrough-x aclinherit > 15 user/group space accounting > 16 stmf property support > 17 Triple-parity RAID-Z > 18 Snapshot user holds > 19 Log device removal > 20 Compression using zle (zero-length encoding) > 21 Deduplication > 22 Received properties > 23 Slim ZIL > 24 System attributes > 25 Improved scrub stats > 26 Improved snapshot deletion performance > 27 Improved snapshot creation performance > 28 Multiple vdev replacements >=20 > For more information on a particular version, including supported = releases, > see the ZFS Administration Guide. >=20 > [root@qaMKSYSB02 ~]# zpool upgrade =20 > This system is currently running ZFS pool version 28. >=20 > All pools are formatted using this version. > [root@qaMKSYSB02 ~]#=20 >=20 >=20 > I think the problem may lie in the=20 >=20 > freebsd-update fetch=20 >=20 > program.=20 >=20 > [root@qaMKSYSB02 ~]# freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > Fetching metadata signature for 9.2-RELEASE from = update2.freebsd.org... done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. >=20 > The following files are affected by updates, but no changes have > been downloaded because the files have been modified locally: > /var/db/mergemaster.mtree >=20 > No updates needed to update system to 9.2-RELEASE-p1. > [root@qaMKSYSB02 ~]#=20 >=20 >=20 > mergemaster.mtree is not something I would have touched.=20 >=20 > Any help to resolve the issue will be highly appreciated.=20 >=20 > Regards >=20 > Vusa > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Wed Oct 30 17:01:03 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E4C6CEB9 for ; Wed, 30 Oct 2013 17:01:03 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B981F2215 for ; Wed, 30 Oct 2013 17:01:03 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id AA6A722032 for ; Wed, 30 Oct 2013 13:01:01 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Wed, 30 Oct 2013 13:01:01 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=QRHbPN8GVJZgPKVeiZraZhRMgH8=; b=gMZ NC7VbIK52fc1c6B/9dgegotWSpD8BQ1wQC1H9HvbtD4GVuojJGTjgKFR84T9khUa E1t7bVdBbO4rmUScAdXPCczZUmi6tkgah6rFrZMgF1bhNagkLb1j3KFFU7wjVoDu +qkNZX6/u+Wwj16Neo02Fu/FNupFUhijjllNwhBs= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 870011128CE; Wed, 30 Oct 2013 13:01:01 -0400 (EDT) Message-Id: <1383152461.16117.40786897.62BCE80A@webmail.messagingengine.com> X-Sasl-Enc: GIQf+L1zVSc5LPCRBApsSFOowuynX2zxj2yR6Euna0rL 1383152461 From: Mark Felder To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-d4893488 In-Reply-To: References: Subject: Re: zpool upgrade and lz4 compression. Date: Wed, 30 Oct 2013 12:01:01 -0500 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 17:01:04 -0000 On Wed, Oct 30, 2013, at 5:56, Vusa Moyo wrote: > Greetings all.=20 >=20 > I=E2=80=99ve upgraded 2 FreeBSD 9.0 servers to 9.2=20 >=20 On the one that isn't working try running # freebsd-update install because I think you only installed the new kernel and didn't finish updating the world From owner-freebsd-fs@FreeBSD.ORG Wed Oct 30 18:31:16 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DE01E454; Wed, 30 Oct 2013 18:31:16 +0000 (UTC) (envelope-from vusa@tuxsystems.co.za) Received: from MOY07-NIX1.wadns.net (moy07-nix1.wadns.net [41.185.26.137]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4347C2935; Wed, 30 Oct 2013 18:31:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by MOY07-NIX1.wadns.net (Postfix) with ESMTP id 2F2F22245A; Wed, 30 Oct 2013 20:31:12 +0200 (SAST) X-Virus-Scanned: Debian amavisd-new at doggle.co.za Received: from MOY07-NIX1.wadns.net ([127.0.0.1]) by localhost (MOY07-NIX1.wadns.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9iS2dap+K2Hv; Wed, 30 Oct 2013 20:31:05 +0200 (SAST) Received: from [10.0.0.113] (196-210-175-123.dynamic.isadsl.co.za [196.210.175.123]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by MOY07-NIX1.wadns.net (Postfix) with ESMTPSA id 67B231FC96; Wed, 30 Oct 2013 20:31:05 +0200 (SAST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: zpool upgrade and lz4 compression. From: Vusa Moyo In-Reply-To: <1383152461.16117.40786897.62BCE80A@webmail.messagingengine.com> Date: Wed, 30 Oct 2013 20:30:07 +0200 Message-Id: <6F9748EB-4CE5-4F18-A428-0FE935F9C767@tuxsystems.co.za> References: <1383152461.16117.40786897.62BCE80A@webmail.messagingengine.com> To: Mark Felder X-Mailer: Apple Mail (2.1510) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2013 18:31:16 -0000 Hello Mark.=20 > # freebsd-update fetch The merge master tree is what appears to need fixing.=20 When I run freebsd-update IDS I have millions of files without valid = keys. See below [root@qaMKSYSB02 ~]# freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. [root@qaMKSYSB02 ~]# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching metadata signature for 9.2-RELEASE from update2.freebsd.org... = done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files are affected by updates, but no changes have been downloaded because the files have been modified locally: /var/db/mergemaster.mtree No updates needed to update system to 9.2-RELEASE-p1. [root@qaMKSYSB02 ~]#=20 On Oct 30, 2013, at 7:01 PM, Mark Felder wrote: >=20 >=20 > On Wed, Oct 30, 2013, at 5:56, Vusa Moyo wrote: >> Greetings all.=20 >>=20 >> I=92ve upgraded 2 FreeBSD 9.0 servers to 9.2=20 >>=20 >=20 > On the one that isn't working try running >=20 > # freebsd-update install >=20 > because I think you only installed the new kernel and didn't finish > updating the world > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Thu Oct 31 08:25:08 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 75E6F74F; Thu, 31 Oct 2013 08:25:08 +0000 (UTC) (envelope-from vusa@tuxsystems.co.za) Received: from MOY07-NIX1.wadns.net (moy07-nix1.wadns.net [41.185.26.137]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 14F3E28D6; Thu, 31 Oct 2013 08:25:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by MOY07-NIX1.wadns.net (Postfix) with ESMTP id E080E2243E; Thu, 31 Oct 2013 10:25:02 +0200 (SAST) X-Virus-Scanned: Debian amavisd-new at doggle.co.za Received: from MOY07-NIX1.wadns.net ([127.0.0.1]) by localhost (MOY07-NIX1.wadns.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oUPy69h2hiW; Thu, 31 Oct 2013 10:24:57 +0200 (SAST) Received: from [192.168.88.207] (8ta-228-51-112.telkomadsl.co.za [197.228.51.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by MOY07-NIX1.wadns.net (Postfix) with ESMTPSA id 0EEA71FAA0; Thu, 31 Oct 2013 10:24:56 +0200 (SAST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: zpool upgrade and lz4 compression. From: Vusa Moyo In-Reply-To: <6F9748EB-4CE5-4F18-A428-0FE935F9C767@tuxsystems.co.za> Date: Thu, 31 Oct 2013 10:24:54 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8F9EC9B6-B23B-45BE-939F-A47E3438B697@tuxsystems.co.za> References: <1383152461.16117.40786897.62BCE80A@webmail.messagingengine.com> <6F9748EB-4CE5-4F18-A428-0FE935F9C767@tuxsystems.co.za> To: Mark Felder X-Mailer: Apple Mail (2.1816) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2013 08:25:08 -0000 I decided to export the ZFS filesystem and import it into a new build.=20= Regards Vusa=20 On 30 Oct 2013, at 8:30 PM, Vusa Moyo wrote: > Hello Mark.=20 >=20 >> # freebsd-update fetch >=20 > The merge master tree is what appears to need fixing.=20 >=20 > When I run freebsd-update IDS I have millions of files without valid = keys. >=20 > See below >=20 > [root@qaMKSYSB02 ~]# freebsd-update install > No updates are available to install. > Run '/usr/sbin/freebsd-update fetch' first. > [root@qaMKSYSB02 ~]# freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > Fetching metadata signature for 9.2-RELEASE from = update2.freebsd.org... done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. >=20 > The following files are affected by updates, but no changes have > been downloaded because the files have been modified locally: > /var/db/mergemaster.mtree >=20 > No updates needed to update system to 9.2-RELEASE-p1. > [root@qaMKSYSB02 ~]#=20 >=20 >=20 >=20 >=20 >=20 > On Oct 30, 2013, at 7:01 PM, Mark Felder wrote: >=20 >>=20 >>=20 >> On Wed, Oct 30, 2013, at 5:56, Vusa Moyo wrote: >>> Greetings all.=20 >>>=20 >>> I=92ve upgraded 2 FreeBSD 9.0 servers to 9.2=20 >>>=20 >>=20 >> On the one that isn't working try running >>=20 >> # freebsd-update install >>=20 >> because I think you only installed the new kernel and didn't finish >> updating the world >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Thu Oct 31 14:57:52 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 515D3514; Thu, 31 Oct 2013 14:57:52 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 19FAB24B2; Thu, 31 Oct 2013 14:57:52 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id ar20so5181718iec.14 for ; Thu, 31 Oct 2013 07:57:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=i/b2hBOuzXQt3kZ+n2+YCsyjdbm6xzQikWOtUOK0Y6k=; b=nyGQTPsJMPutrCtB4wFhoiZ4fWn3wVsAmkSB0+dKyKIY2bLM1iIl9hO0v3eptXhnQd EiBY4rZxNtky6L1X9yUbmpSuEyrmzAzXN0eYRt8koGqZOTpM6lHzg5qPBEt/0q04WDn2 PIjbfbvwZSO/v/UdslGgRqmXVgrQ5cTwfhZOLbmbGXBjiIuFSjerbu2qQNlG0KB6feW4 /dIrJ0zbwg1LOPzanC6V/QLZwvJWRneHO55FPO8gr7T/YsQaVbOC5UJFabSkcUZA4MC+ X0UIX5Mgpe5LwB9/jnkP0ga9zDR6eI0qNXTwzQ9XO/UzOUz1i0Ee/ny+P6tpBJtJjJyZ fSSA== MIME-Version: 1.0 X-Received: by 10.50.115.35 with SMTP id jl3mr2928238igb.37.1383231471492; Thu, 31 Oct 2013 07:57:51 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.43.180.131 with HTTP; Thu, 31 Oct 2013 07:57:51 -0700 (PDT) In-Reply-To: <526FD60B.6000101@FreeBSD.org> References: <526FD60B.6000101@FreeBSD.org> Date: Thu, 31 Oct 2013 10:57:51 -0400 X-Google-Sender-Auth: ZFRSQiDWwicw4dBkV5-L6YYPCws Message-ID: Subject: Re: 9.2 + ZFS + i386 = panic: pmap_enter: attempted pmap_enter on 4MB page From: J David To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2013 14:57:52 -0000 On Tue, Oct 29, 2013 at 11:36 AM, Andriy Gapon wrote: > And with that you are not getting any panic any more? Not so far: $ uptime 2:49PM up 9 days, 2 hrs, 2 users, load averages: 0.25, 0.41, 0.42 > What CPU do you have? It's an Intel Xeon L5410 @ 2.333Ghz. Thanks! From owner-freebsd-fs@FreeBSD.ORG Fri Nov 1 04:44:23 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41012E66 for ; Fri, 1 Nov 2013 04:44:23 +0000 (UTC) (envelope-from alex.wilkinson@cba.com.au) Received: from igw10blk.cba.com.au (igwx12.cba.com.au [140.168.71.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 90CC02B7F for ; Fri, 1 Nov 2013 04:44:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cba.com.au; i=@cba.com.au; q=dns/txt; s=CBAdkim-110609; t=1383281062; x=1698641062; h=date:from:to:subject:message-id:references:mime-version: in-reply-to; bh=3Qzc8kJbWm1mHSZ/Pg0o4hLZS+USxr+OiiZJA9sdMSI=; b=rjsWoEFu610VzAPsA14njjfDizYHu4n5d8/5bDsiyKUqArDzG5hGGDrd uPi0cgnnk++rGmwv21zfJ70Wlfb3Yg==; X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.93,614,1378821600"; d="scan'208";a="84951170" Received: from unknown (HELO aaunswc27.au.cbainet.com) ([10.30.10.34]) by igw10.cba.com.au with ESMTP; 01 Nov 2013 15:44:12 +1100 Received: from margz.perth.internal ([10.138.102.216]) by aaunswc27.au.cbainet.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 1 Nov 2013 15:44:12 +1100 Date: Fri, 1 Nov 2013 15:44:03 +1100 From: "Wilkinson, Alex" To: "freebsd-fs@freebsd.org" Subject: Re: HAST - Unable to receive request header: Socket is not connected (10.0-BETA1) Message-ID: <20131101044402.GA99992@margz.perth.internal> Mail-Followup-To: "freebsd-fs@freebsd.org" References: <20131029072708.GC86932@margz.perth.internal> <20131029131612.GA43106@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131029131612.GA43106@gmail.com> Organisation: Commonwealth Bank Australia X-Message-Flag: "Please Restore Line Breaks If Necessary" User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginalArrivalTime: 01 Nov 2013 04:44:12.0630 (UTC) FILETIME=[02E8D760:01CED6BD] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 04:44:23 -0000 0n Wed, Oct 30, 2013 at 12:17:26AM +1100, Mikolaj Golub wrote: >On Tue, Oct 29, 2013 at 06:27:08PM +1100, Wilkinson, Alex wrote: > >> [DEBUG][2] Checking hooks. >> [DEBUG][2] [export] (primary) remote_send: Taking request. >> [DEBUG][2] [export] (primary) remote_guard: Checking connections. >> [DEBUG][2] Checking hooks. >> [DEBUG][2] [export] (primary) remote_guard: Reconnecting to tcp4://172.18.3.12. >> [DEBUG][1] [export] (primary) Negotiated protocol version 2. >> [WARNING] [export] (primary) Data size differs between nodes (local=128819612160, remote=128848941568). > >It looks like you created resources of different size on differen >nodes. If the primary detects media size mismatch it closes the >connection. > >Does mfid0p4 size differs on host-a and host-b? If it does use -m >option in `hastctl create' to specify the same size on both nodes. >You can run `hastctl dump' (on both nodes) to see what HAST currently >thinks about media size. > >> [ERROR] [export] (secondary) Unable to receive request header: Socket is not connected. > >This is a consequence of the primary closing the connection after >detecting media size mismatch. You are right! using -m when creating solved my problem! Thanks! -Alex ************** IMPORTANT MESSAGE ***************************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ************************************************************** From owner-freebsd-fs@FreeBSD.ORG Fri Nov 1 05:21:34 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 81178B35 for ; Fri, 1 Nov 2013 05:21:34 +0000 (UTC) (envelope-from shawn.wallbridge@imaginaryforces.com) Received: from barracuda.imaginaryforces.com (199.193.209.132.static.oneiricsys.com [199.193.209.132]) by mx1.freebsd.org (Postfix) with ESMTP id 57AED2D99 for ; Fri, 1 Nov 2013 05:21:32 +0000 (UTC) X-ASG-Debug-ID: 1383283291-0413ad4d7f375880001-3nHGF7 Received: from newman.IMAGINARYFORCES.LOCAL (newman.imaginaryforces.local [192.168.23.34]) by barracuda.imaginaryforces.com with ESMTP id 4QDC2nOoMVCSSc4D for ; Thu, 31 Oct 2013 22:21:31 -0700 (PDT) X-Barracuda-Envelope-From: shawn.wallbridge@imaginaryforces.com Received: from NEWMAN.IMAGINARYFORCES.LOCAL ([192.168.23.34]) by newman.IMAGINARYFORCES.LOCAL ([192.168.23.34]) with mapi id 14.01.0438.000; Thu, 31 Oct 2013 22:21:22 -0700 From: Shawn Wallbridge To: "freebsd-fs@freebsd.org" Subject: FFS Softdep Kernel Panic Thread-Topic: FFS Softdep Kernel Panic X-ASG-Orig-Subj: FFS Softdep Kernel Panic Thread-Index: AQHO1sIzIuLAB/zMt02zzLSQnMMkjg== Date: Fri, 1 Nov 2013 05:21:21 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.23.68] Content-Type: text/plain; charset="us-ascii" Content-ID: <031400DEEE5CA2468E3E40E97F434017@IMAGINARYFORCES.COM> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: newman.imaginaryforces.local[192.168.23.34] X-Barracuda-Start-Time: 1383283291 X-Barracuda-URL: http://barracuda.imaginaryforces.com:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at imaginaryforces.com X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.141956 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 05:21:34 -0000 I am running a large (71TB) file (NFS w/ some Samba) server (9.2-RELEASE) and it has been crashing almost daily. I have been trying to track down the issue, but I haven't had any luck. The panic is.. panic: handle_workitem_remove: bad file delta cpuid =3D 9 KDB: stack backtrace: #0 0xffffffff80947986 at kdb_backtrace+0x66 #1 0xffffffff8090d9ae at panic+0x1ce #2 0xffffffff80b4143f at handle_workitem_remove+0x46f #3 0xffffffff80b4133a at handle_workitem_remove+0x36a #4 0xffffffff80b4069d at process_worklist_item+0x2bd #5 0xffffffff80b450da at softdep_process_worklist+0x8a #6 0xffffffff80b47a4d at softdep_flush+0x1ad #7 0xffffffff808db67f at fork_exit+0x11f #8 0xffffffff80cdc23e at fork_trampoline+0xe I looked at the source for ffs_softdep.c and found this, which seems to be the only place "bad file delta" shows up. /* * Normal file deletion. */ if ((dirrem->dm_state & RMDIR) =3D=3D 0) { ip->i_nlink--; DIP_SET(ip, i_nlink, ip->i_nlink); ip->i_flag |=3D IN_CHANGE; if (ip->i_nlink < ip->i_effnlink) panic("handle_workitem_remove: bad file delta"); if (ip->i_nlink =3D=3D 0) unlinked_inodedep(mp, inodedep); inodedep->id_nlinkdelta =3D ip->i_nlink - ip->i_effnlink; KASSERT(LIST_EMPTY(&dirrem->dm_jwork), ("handle_workitem_remove: worklist not empty. %s", TYPENAME(LIST_FIRST(&dirrem->dm_jwork)->wk_type))); WORKITEM_FREE(dirrem, D_DIRREM); FREE_LOCK(&lk); goto out; } I have created a PR, but I haven't had any response (no one has even downloaded the crash dumps I linked to). http://www.freebsd.org/cgi/query-pr.cgi?pr=3D183424 Because this is a file server, in production, this is becoming a HUGE problem and is costing us quite a bit of lost production each time it crashes (and takes 4hrs to fsck). Thanks shawn ________________________________ This e-mail is intended only for the named person or entity to which it is = addressed and contains valuable business information that is proprietary, p= rivileged, confidential and/or otherwise protected from disclosure. If you = received this e-mail in error, any review, use, dissemination, distribution= or copying of this e-mail is strictly prohibited. Please notify us immedia= tely of the error via e-mail to postmaster@imaginaryforces.c= om and please delete the e-mail from your system, retaining no copies in an= y media. We appreciate your cooperation. ...imaginaryforces.com...=0D From owner-freebsd-fs@FreeBSD.ORG Fri Nov 1 17:31:08 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B018FA2F for ; Fri, 1 Nov 2013 17:31:08 +0000 (UTC) (envelope-from shawn.wallbridge@imaginaryforces.com) Received: from barracuda.imaginaryforces.com (199.193.209.132.static.oneiricsys.com [199.193.209.132]) by mx1.freebsd.org (Postfix) with ESMTP id 8ED502C27 for ; Fri, 1 Nov 2013 17:31:07 +0000 (UTC) X-ASG-Debug-ID: 1383327066-0413ad4d7f37dfc0001-3nHGF7 Received: from newman.IMAGINARYFORCES.LOCAL (newman.imaginaryforces.local [192.168.23.34]) by barracuda.imaginaryforces.com with ESMTP id DE77CfkjkvgUn95N; Fri, 01 Nov 2013 10:31:06 -0700 (PDT) X-Barracuda-Envelope-From: shawn.wallbridge@imaginaryforces.com Received: from NEWMAN.IMAGINARYFORCES.LOCAL ([192.168.23.34]) by newman.IMAGINARYFORCES.LOCAL ([192.168.23.34]) with mapi id 14.01.0438.000; Fri, 1 Nov 2013 10:30:57 -0700 From: Shawn Wallbridge To: Kirk McKusick , "freebsd-fs@freebsd.org" Subject: Re: FFS Softdep Kernel Panic Thread-Topic: FFS Softdep Kernel Panic X-ASG-Orig-Subj: Re: FFS Softdep Kernel Panic Thread-Index: AQHO1ygfRN1puknhSUmkxjIIrFy/ag== Date: Fri, 1 Nov 2013 17:30:57 +0000 Message-ID: In-Reply-To: <201311011656.rA1GuWCp045991@chez.mckusick.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.23.68] Content-Type: text/plain; charset="us-ascii" Content-ID: <351AC073AD8C6C40BC673679239140C7@IMAGINARYFORCES.COM> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: newman.imaginaryforces.local[192.168.23.34] X-Barracuda-Start-Time: 1383327066 X-Barracuda-URL: http://barracuda.imaginaryforces.com:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at imaginaryforces.com X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.141968 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 17:31:08 -0000 On 11/1/13 9:56 AM, "Kirk McKusick" wrote: >> From: Shawn Wallbridge >> To: "freebsd-fs@freebsd.org" >> Subject: FFS Softdep Kernel Panic >> Date: Fri, 1 Nov 2013 05:21:21 +0000 >> >> I am running a large (71TB) file (NFS w/ some Samba) server >>(9.2-RELEASE) >> and it has been crashing almost daily. I have been trying to track down >> the issue, but I haven't had any luck. >> >> The panic is.. >> >> panic: handle_workitem_remove: bad file delta >> cpuid =3D 9 >> KDB: stack backtrace: >> #0 0xffffffff80947986 at kdb_backtrace+0x66 >> #1 0xffffffff8090d9ae at panic+0x1ce >> #2 0xffffffff80b4143f at handle_workitem_remove+0x46f >> #3 0xffffffff80b4133a at handle_workitem_remove+0x36a >> #4 0xffffffff80b4069d at process_worklist_item+0x2bd >> #5 0xffffffff80b450da at softdep_process_worklist+0x8a >> #6 0xffffffff80b47a4d at softdep_flush+0x1ad >> #7 0xffffffff808db67f at fork_exit+0x11f >> #8 0xffffffff80cdc23e at fork_trampoline+0xe >> >> >> I looked at the source for ffs_softdep.c and found this, which seems to >>be >> the only place "bad file delta" shows up. >> >> /* >> * Normal file deletion. >> */ >> if ((dirrem->dm_state & RMDIR) =3D=3D 0) { >> ip->i_nlink--; >> DIP_SET(ip, i_nlink, ip->i_nlink); >> ip->i_flag |=3D IN_CHANGE; >> if (ip->i_nlink < ip->i_effnlink) >> panic("handle_workitem_remove: bad file delta"); >> if (ip->i_nlink =3D=3D 0) >> unlinked_inodedep(mp, inodedep); >> inodedep->id_nlinkdelta =3D ip->i_nlink - ip->i_effnlink; >> KASSERT(LIST_EMPTY(&dirrem->dm_jwork), >> ("handle_workitem_remove: worklist not empty. %s", >> TYPENAME(LIST_FIRST(&dirrem->dm_jwork)->wk_type))); >> WORKITEM_FREE(dirrem, D_DIRREM); >> FREE_LOCK(&lk); >> goto out; >> } >> >> I have created a PR, but I haven't had any response (no one has even >> downloaded the crash dumps I linked to). >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D183424 >> >> Because this is a file server, in production, this is becoming a HUGE >> problem and is costing us quite a bit of lost production each time it >> crashes (and takes 4hrs to fsck). >> >> Thanks >> shawn > >I have taken a look at your bug report and have a couple of questions >about your system: > >Your kernel was built at the end of September. Has this problem >persisted since that kernel was build, or has it showed up more recently? > >Are you running with journaled soft updates or just regular soft >updates? You can use the mount command with no arguments to find out. > > Kirk McKusick > Thank you. This machine was originally built using 9.1-RELEASE, which had the problem as well, so I updated to 9.2-RELEASE to try to resolve the issue. I am running both, /dev/da0p1 on /sam (ufs, NFS exported, local, journaled soft-updates) I am building a kernel with invariants right now. shawn ________________________________ This e-mail is intended only for the named person or entity to which it is = addressed and contains valuable business information that is proprietary, p= rivileged, confidential and/or otherwise protected from disclosure. If you = received this e-mail in error, any review, use, dissemination, distribution= or copying of this e-mail is strictly prohibited. Please notify us immedia= tely of the error via e-mail to postmaster@imaginaryforces.c= om and please delete the e-mail from your system, retaining no copies in an= y media. We appreciate your cooperation. ...imaginaryforces.com...=0D From owner-freebsd-fs@FreeBSD.ORG Fri Nov 1 17:45:43 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 038B230F; Fri, 1 Nov 2013 17:45:43 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C43092CF4; Fri, 1 Nov 2013 17:45:42 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id rA1HjbL9057122; Fri, 1 Nov 2013 10:45:38 -0700 (PDT) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201311011745.rA1HjbL9057122@chez.mckusick.com> To: Shawn Wallbridge Subject: Re: FFS Softdep Kernel Panic In-reply-to: Date: Fri, 01 Nov 2013 10:45:37 -0700 From: Kirk McKusick Cc: "freebsd-fs@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2013 17:45:43 -0000 > From: Shawn Wallbridge > To: Kirk McKusick , > "freebsd-fs@freebsd.org" > > CC: John Baldwin > Subject: Re: FFS Softdep Kernel Panic > Date: Fri, 1 Nov 2013 17:30:57 +0000 > > On 11/1/13 9:56 AM, "Kirk McKusick" wrote: > >>I have taken a look at your bug report and have a couple of questions >>about your system: >> >>Your kernel was built at the end of September. Has this problem >>persisted since that kernel was build, or has it showed up more recently? >> >>Are you running with journaled soft updates or just regular soft >>updates? You can use the mount command with no arguments to find out. >> >> Kirk McKusick >> > > Thank you. > > This machine was originally built using 9.1-RELEASE, which had the problem > as well, so I updated to 9.2-RELEASE to try to resolve the issue. > > I am running both, > > /dev/da0p1 on /sam (ufs, NFS exported, local, journaled soft-updates) > > I am building a kernel with invariants right now. > > shawn The problem that you are seeing is probably not related to the journaling, but it would be helpful if you could try running with just soft updates to see if the problem goes away. To do this you need to unmount /sam (or at least downgrade it to read-only), then run: tunefs -j disable /sam Then remount /sam (or reenable writing) and use `mount' to verify that it worked. Also `rm /sam/.sujournal'. Run with that configuration and see if the problem persists. Kirk McKusick