From owner-freebsd-fs@FreeBSD.ORG Sun Dec 31 15:05:08 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE4E216A4A0 for ; Sun, 31 Dec 2006 15:05:08 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9362713C4B0 for ; Sun, 31 Dec 2006 15:05:08 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H11yu-0002xq-NK for freebsd-fs@freebsd.org; Sun, 31 Dec 2006 15:48:12 +0100 Received: from 89-172-61-192.adsl.net.t-com.hr ([89.172.61.192]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Dec 2006 15:48:12 +0100 Received: from ivoras by 89-172-61-192.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Dec 2006 15:48:12 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Sun, 31 Dec 2006 15:47:59 +0100 Lines: 47 Message-ID: References: <45929D22.9070008@quip.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDFDFDAA403E3BA832C58D025" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-61-192.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) In-Reply-To: <45929D22.9070008@quip.cz> X-Enigmail-Version: 0.94.1.2 Sender: news Subject: Re: gjournal info X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2006 15:05:09 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDFDFDAA403E3BA832C58D025 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Miroslav Lachman wrote: > Hi all, >=20 > is there any webpage summary about current status of gjournal? A can no= t > find any by google. Only messages in archive of this list. AFAIK it's currently being evaluated before including it in the OS. > Can I add journaling to these existing filesystems without data loss an= d > repartitioning?=20 Yes. > Is it better to have journal for external array on > internal drive or on array itself? If you put the journal on a separate drive, it will probably be a bit faster. > And can I set up gjournal on gmirrored partition? Just like on real dis= k? Yes. --------------enigDFDFDAA403E3BA832C58D025 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFl82lldnAQVacBcgRAsy9AKDmZwGIOrOLiY7Adj/jEUnbN/w7dACg+RLp ySlxyS7Wjv/CuI2loDF32bU= =O+7x -----END PGP SIGNATURE----- --------------enigDFDFDAA403E3BA832C58D025-- From owner-freebsd-fs@FreeBSD.ORG Sun Dec 24 07:08:14 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB97616A40F for ; Sun, 24 Dec 2006 07:08:14 +0000 (UTC) (envelope-from brooklyn@flinet.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 7A5CF13C463 for ; Sun, 24 Dec 2006 07:08:14 +0000 (UTC) (envelope-from brooklyn@flinet.com) Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 24 Dec 2006 01:38:12 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id MRU74898; Sun, 24 Dec 2006 01:38:11 -0500 (EST) Received: from 207-237-238-113.c3-0.avec-ubr15.nyr-avec.ny.cable.rcn.com (HELO ACER1) ([207.237.238.113]) by smtp01.lnh.mail.rcn.net with ESMTP; 24 Dec 2006 01:38:12 -0500 From: "Steven" To: Date: Sun, 24 Dec 2006 01:38:07 -0500 Message-ID: <018e01c72726$12e75720$0201a8c0@ACER1> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AccnJgx8+PmtDT1uTFWlPD4XHc47Uw== X-Junkmail-Status: score=42/50, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=suspect(7), refid=str=0001.0A090209.458E1EE2.0015,ss=2,fgs=0, ip=207.172.4.11, so=2006-05-09 23:27:51, dmn=5.2.121/2006-09-27 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Snap Server File System X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Dec 2006 07:08:14 -0000 =20 =20 Tom, =20 I just read your answer to David and Eric on the Snap 1100. =20 I spoke with Adaptec who I am sure you know inherited this from Quantum. = They told me that BSD is also used on the 4100 and 4500 raid systems. I would like to know where you found out from, unless you can answer me about the software raid, what stripe size they used. I will assume for = the moment that they used BSD default. My other Question is about the extra drive for parity which I understand = is not implemented yet If so Quantum would have to have implemented it. Do you have any sources, web sites or reading information I can go to = that will save my time of trial and error.=20 I am working with a 4100, one of the drives dropped out and the raid 5 didn=92t hold up. The chipset is standard promise 100ATA x2 to handle all 4 drives as = master. =20 =20 Any info you can give me would be helpful =20 =20 Thank you, Steven --=20 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.15.26/598 - Release Date: = 12/22/2006 3:22 PM =20 From owner-freebsd-fs@FreeBSD.ORG Sun Dec 24 14:28:58 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E65516A407; Sun, 24 Dec 2006 14:28:58 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.freebsd.org (Postfix) with ESMTP id A79BD13C463; Sun, 24 Dec 2006 14:28:57 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.8/8.13.8/NinthNine) with SMTP id kBOESts1034256; Sun, 24 Dec 2006 23:28:56 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 24 Dec 2006 23:28:55 +0900 From: Norikatsu Shigemura To: Pawel Jakub Dawidek Message-Id: <20061224232855.b0786250.nork@FreeBSD.org> In-Reply-To: <20061223142332.GA99259@garage.freebsd.pl> References: <20061223111738.6292605a.nork@FreeBSD.org> <20061223142332.GA99259@garage.freebsd.pl> X-Mailer: Sylpheed version 2.3.0beta7 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Sun, 24 Dec 2006 23:28:56 +0900 (JST) Cc: freebsd-fs@FreeBSD.org Subject: Re: [REPORT] Some panics on ZFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Dec 2006 14:28:58 -0000 On Sat, 23 Dec 2006 15:23:32 +0100 Pawel Jakub Dawidek wrote: > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > ZFS filesystem version 3 > > ZFS storage pool version 3 > > Warning: memory type solaris leaked memory on destroy (116 allocations, 7328 bytes leaked). > > ZFS filesystem version 3 > > ZFS storage pool version 3 > > Warning: memory type solaris leaked memory on destroy (116 allocations, 7328 bytes leaked). > > ZFS filesystem version 3 > > ZFS storage pool version 3 > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > This one is already fixed. Thank you. > > But 'kldload zfs; mount -t zfs tank /mnt' didn't panic. f(?_?)? > It can be easly fixed, but bascially in zfs world you should mount file I saw perforce/112119. Thank you. (http://perforce.freebsd.org/chv.cgi?CH=112119) > systems after loading zfs.ko via: > # zfs mount -a > and activate zvols: > # zfs volinit Yes. So I'm using following configuration:-). /etc/rc.conf.d/mountlate - - - - - - - - - - - - - - - - - - - - - - - zfsinit () { kldstat -q -m zfs || kldload zfs } zfsmount () { zfs mount -a zfs volinit } zfsunmount () { zfs unmount -a } start_precmd=zfsinit start_postcmd=zfsmount stop_precmd=zfsunmount /etc/rc.conf.d/mountlate - - - - - - - - - - - - - - - - - - - - - - - I think that /etc/rc.d/mountzfs will be installed. > > 3. When I'm testing with iozone, ZFS panic-ed. > > I saw some memory modified after free. > Are you able to setup memguard(9)? Or maybe you can give me procedure to > reproduce it? I did setup memguard(9). But I cannot get any data. Because I got following panics:-). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - panic: MEMGUARD: You must increase MAX_PAGES_PER_ITEM in memguard.c (requested: 512 pages) cpuid = 0 KDB: enter: panic [thread pid 817 tid 100070 ] Stopped at kdb_enter+0x30: leave db> bt Tracing pid 817 tid 100070 td 0x8e80a360 kdb_enter(806b6baf,0,806d113f,f9ef6a8c,8e80a360,...) at kdb_enter+0x30 panic(806d113f,200,0,f9ef6aa4,200000,...) at panic+0x14e memguard_alloc(200000,1,8ebd359f,200000,20000,...) at memguard_alloc+0x31 malloc(200000,8ec4cb20,1,f9ef6af8,8ebd349e,...) at malloc+0xaf kmem_alloc(200000,1,80000,0,f9ef6b38,...) at kmem_alloc+0x21 kmem_zalloc(200000,1,0,0,100,...) at kmem_zalloc+0x1e dbuf_init(f9ef6b5c,8ec09cc7,8ec56638,8ec08950,1c,...) at dbuf_init+0x81 dmu_init(8ec56638,8ec08950,1c,8,8ebacc80,...) at dmu_init+0x8 spa_init(3,0,0,0,180,...) at spa_init+0x97 zfs_modevent(8ebacc80,0,0,75,f9ef6ba4,...) at zfs_modevent+0x58 module_register_init(8ec4da30,0,806b44ad,dc,0,...) at module_register_init+0xa5 linker_file_sysinit(8eb8a500,8ebad180,f9ef6bec,175,8ebad180,...) at linker_file_sysinit+0xe0 linker_load_file(8ebad180,f9ef6c14,0,72c,d0,...) at linker_load_file+0x125 linker_load_module(0,8e04c400,0,0,f9ef6c40,...) at linker_load_module+0xf9 kern_kldload(8e80a360,8e04c400,f9ef6c68,0,2f8,...) at kern_kldload+0xc4 kldload(8e80a360,f9ef6d00,4,c,f9ef6d38,...) at kldload+0x74 syscall(f9ef6d38) at syscall+0x2e3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x2, esp = 0x213, ebp = 0x7fbfeee4 --- db> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I increased MAX_PAGES_PER_ITEM to 65536. But... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - panic: MEMGUARD: Failed with M_WAITOK: memguard_map too small cpuid = 0 KDB: enter: panic [thread pid 1027 tid 100126 ] Stopped at kdb_enter+0x30: leave db> bt Tracing pid 1027 tid 100126 td 0x8ecd9d80 kdb_enter(806b6b8f,0,806d1172,f9fe3830,8ecd9d80,...) at kdb_enter+0x30 panic(806d1172,0,806d104e,f3,240,...) at panic+0x14e memguard_alloc(240,2,0,240,8ecd8d80,...) at memguard_alloc+0x156 malloc(240,8ec50b20,2,f9fe389c,8ebd749e,...) at malloc+0xaf kmem_alloc(240,2,84607000,9ee80400,f9fe38e4,...) at kmem_alloc+0x21 kmem_zalloc(240,2,8db77000,8db78000,7,...) at kmem_zalloc+0x1e zio_create(25b9,0,9ee80400,aaf2b000,4000,...) at zio_create+0x2d zio_write(8d416000,84607000,6,2,1,...) at zio_write+0x77 arc_write(8d416000,84607000,6,2,1,...) at arc_write+0x105 dbuf_sync(aafb2a50,8d416000,87109000,0,8ec48bf8,...) at dbuf_sync+0x3ca dnode_sync(906d68f0,0,8d416000,87109000,8d416000,...) at dnode_sync+0x51b dmu_objset_sync_dnodes(87109000,400,8ec48b11,806b5ba7,ae,...) at dmu_objset_sync_dnodes+0x97 dmu_objset_sync(85abc000,87109000,25b9,0,f9fe3bac,...) at dmu_objset_sync+0x60 dsl_dataset_sync(85aba000,87109000,0,84f8e1cc,84f8e184,...) at dsl_dataset_sync+0x24 dsl_pool_sync(84f8e000,25b9,0,1,0,...) at dsl_pool_sync+0x8f spa_sync(84607000,25b9,0,84f8e15c,84f8e154,...) at spa_sync+0x453 txg_sync_thread(84f8e000,f9fe3d38,806b3a8a,328,8ecd8d80,...) at txg_sync_thread+0x1d7 fork_exit(8ec0fd20,84f8e000,f9fe3d38) at fork_exit+0xd1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xf9fe3d6c, ebp = 0 --- db> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > I'll try to reproduce iozone panic, I'd also like to reproduce "Memory > modified after free" and "mi_switch: switch in a critical section" > panics, can you tell me how to do it? All cases are using iozone. 1. zpool create tank da0 2. cd /tank; iozone -a |& tee iozone.1.log 3. (panic) get backtrace and reset 4. cd /tank; iozone -a |& tee iozone.2.log 5. (panic) get backtrace and reset 6. cd /tank; ...... : And I got many type of panic messages. So I don't know how to reproduce these behaviors. From owner-freebsd-fs@FreeBSD.ORG Wed Dec 27 14:45:44 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 71DD016A403 for ; Wed, 27 Dec 2006 14:45:44 +0000 (UTC) (envelope-from daw@cs.berkeley.edu) Received: from taverner.cs.berkeley.edu (taverner.CS.Berkeley.EDU [128.32.168.222]) by mx1.freebsd.org (Postfix) with ESMTP id 4857013C466 for ; Wed, 27 Dec 2006 14:45:44 +0000 (UTC) (envelope-from daw@cs.berkeley.edu) Received: from taverner.cs.berkeley.edu (localhost.localdomain [127.0.0.1]) by taverner.cs.berkeley.edu (8.13.8/8.13.7) with ESMTP id kBRDZ8Df024318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Dec 2006 05:35:08 -0800 Received: (from daw@localhost) by taverner.cs.berkeley.edu (8.13.8/8.13.8/Submit) id kBRDZ8Hk024317 for freebsd-fs@freebsd.org; Wed, 27 Dec 2006 05:35:08 -0800 Date: Wed, 27 Dec 2006 05:35:08 -0800 From: David_Wagner Message-Id: <200612271335.kBRDZ8Hk024317@taverner.cs.berkeley.edu> User-Agent: Vacation/1.2.6 http://vacation.sourceforge.net To: freebsd-fs@freebsd.org Subject: away from my mail X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 14:45:44 -0000 I am on sabbatical until June 2007. Be advised that I am not reading my email as regularly as I might otherwise; responses may be delayed. Please accept my apologies. I will not be taking on any new projects during my sabbatical. If you're writing to ask me to review a paper or serve on a program committee, I'm afraid I can't do it. In an emergency, you may contact Tammy Johnson 510-643-4816 . From owner-freebsd-fs@FreeBSD.ORG Wed Dec 27 16:39:32 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 586A716A403 for ; Wed, 27 Dec 2006 16:39:32 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (grimm.quip.cz [213.220.192.218]) by mx1.freebsd.org (Postfix) with ESMTP id 17AB513C487 for ; Wed, 27 Dec 2006 16:39:31 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id 0FF8A628F for ; Wed, 27 Dec 2006 17:19:46 +0100 (CET) Message-ID: <45929D22.9070008@quip.cz> Date: Wed, 27 Dec 2006 17:19:46 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: gjournal info X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 16:39:32 -0000 Hi all, is there any webpage summary about current status of gjournal? A can not find any by google. Only messages in archive of this list. I would like to know about gjournal on FreeBSD 6.x (currenty running 6.2-RC1) and usage on existing filesystem (UFS2) with data. (external SCSI 1.2TB array and internal gmirrored 400GB HDD with 300GB data partition). Can I add journaling to these existing filesystems without data loss and repartitioning? Is it better to have journal for external array on internal drive or on array itself? And can I set up gjournal on gmirrored partition? Just like on real disk? Miroslav Lachman