From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 06:39:49 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B5E31065670 for ; Sun, 7 Jun 2009 06:39:49 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net [70.243.84.13]) by mx1.freebsd.org (Postfix) with ESMTP id E467F8FC0C for ; Sun, 7 Jun 2009 06:39:48 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id n576dmgv021357 for ; Sun, 7 Jun 2009 01:39:48 -0500 (CDT) (envelope-from james-freebsd-fs2@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-fs2@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:content-transfer-encoding; b=lgWQ5dYyLuC6FTcmGMQ8TgdFM+pWrwKT4Uw8oIDfBj9YL5mRWgIklP5jUrYehD8+3 0kJreUORjp6aA53AsS5lzIxlVANDllonh04Q3DZ2GPH8mH1wC4g3qsyG61M5NY4XIrK tLXo7S9behl+7ctdYMQHTDNeHb2TSh3A4CTrVVc= Message-ID: <4A2B609E.4060702@jrv.org> Date: Sun, 07 Jun 2009 01:39:26 -0500 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Reproducible ZFS checksum error, svn192136 (05/14/2009) 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, 07 Jun 2009 06:39:49 -0000 I am able to reproduce a ZFS checksum error. I believe I have ruled out the hard disks, controllers, cables, etc - the usual suspects. I have not ruled out the computer itself as I don't have anything else similar to test with. No other errors are seen on that computer. A Dell 435MT (Core i7) at 2.66 GHz with 12GB of RAM 2 Silicon Imagine 3132 PCI-e cards with 2 eSATA ports each 1 Addonics PCI-e card with 4 ports eSATA ports that identifies itself as a Silicon Imagine 3124 Samsung 1TB disk Error happens with any of the eSATA cards or the onboard Intel chipset eSATA controller. Error happens with any hard disk, enclosure or cabling There are no I/O errors in the logs, and when I use an external hardware RAID it reports no errors from the disks or reported to the host. svn 192136 (Thu, 14 May 2009) amd64, GENERIC config The disk is partitioned like this, with a UFS work area at the end and the area up front being Mac OSX compatible. It boots into UFS land, not ZFS # gpart show => 34 1953525101 ad12 GPT (932G) 34 6 - free - (3.0K) 40 409600 1 efi (200M) 409640 1869229256 2 !6a898cc3-1dd2-11b2-99a6-080020736631 (891G) 1869638896 128 3 freebsd-boot (64K) 1869639024 4194304 4 freebsd-ufs (2.0G) 1873833328 33554432 5 freebsd-swap (16G) 1907387760 4194304 6 freebsd-ufs (2.0G) 1911582064 33554432 7 freebsd-ufs (16G) 1945136496 8388608 8 freebsd-ufs (4.0G) 1953525104 31 - free - (16K) For ease of moving the disk between SATA ports each UFS and swap is labeled with gmirror: # gmirror status Name Status Components mirror/sroot COMPLETE ad12p4 mirror/sswap COMPLETE ad12p5 mirror/stmp COMPLETE ad12p6 mirror/susr COMPLETE ad12p7 mirror/svar COMPLETE ad12p8 /boot/loader.conf contains zfs_load="YES" vm.kmem_size="1536M" vm.kmem_size_min="1536M" vfs.root.mountfrom="ufs:mirror/sroot" kern.maxfiles="32K" kern.ktrace.request_pool="512" geom_mirror_load="YES" # RAID1 disk driver (see gmirror(8)) vfs.zfs.debug=1 #vfs.zfs.prefetch_disable=1 loader_logo="beastie" # Desired logo: fbsdbw, beastiebw, beastie, none boot_verbose="YES" # -v: Causes extra debugging information to be printed 1. Start one buildworld loop thusly on UFS. cd /usr/src while true do make clean make buildworld touch "done-`date`" done 2. Start writes to ZFS with rsync Make a clean pool: zpool create pool ad12p2 Start an rsync copying data to ZFS. I'm copying from a Mac-mini over the network, which gets about 20 MB/s when the systems are not loaded. 3. Run "zpool scrub pool". As each scrub completes start a new one. At some point a scrub will report a checksum error(s), usually within the first 500GB of the rsync, sometimes it takes a few TB. I'm wondering if anyone else is able to try something similar, with I/O to UFS and ZFS, and scrubs, to one disk, on a system with >> 4GB RAM. PS. we need a debug sysctl to make zfs return data from a block with a checksum error so we can easy see what data is on disk. From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 12:01:28 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 034C2106568A for ; Sun, 7 Jun 2009 12:01:28 +0000 (UTC) (envelope-from georg@dts.su) Received: from host4.symbios.ru (host4.symbios.ru [80.84.112.82]) by mx1.freebsd.org (Postfix) with ESMTP id 448DC8FC20 for ; Sun, 7 Jun 2009 12:01:27 +0000 (UTC) (envelope-from georg@dts.su) Received: from [127.0.0.1] (helo=WORLDMY) by host4.symbios.ru with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MDGeM-000Njb-JM; Sun, 07 Jun 2009 15:34:54 +0400 Received: from WORLDMY ([80.84.121.226] helo=WORLDMY) with IPv4:25 by host4.symbios.ru; 7 Jun 2009 15:34:52 +0400 Date: Sun, 7 Jun 2009 15:34:52 +0400 From: georg@dts.su Organization: dts.su X-Priority: 3 (Normal) Message-ID: <49009886.20090607153452@dts.su> To: freebsd-questions@freebsd.org, freebsd-fs@freebsd.org In-Reply-To: <20090606175033.GJ1927@deviant.kiev.zoral.com.ua> References: <20090606161600.GB61928@dchagin.static.corbina.ru> <20090606175033.GJ1927@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable X-Assp-Whitelisted: Yes X-Assp-Envelope-From: georg@dts.su X-Assp-Intended-For: freebsd-questions@freebsd.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host4.symbios.ru X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [26 6] / [26 6] X-AntiAbuse: Sender Address Domain - dts.su Cc: Subject: Re[8]: fatal trap 12 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: georg@dts.su List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jun 2009 12:01:29 -0000 Hello. After patch, whan make kernel I have this: /usr/src/sys/kern/vfs_vnops.c:750:37: error: macro "vn_lock" requires 3 arg= uments, but only 2 given /usr/src/sys/kern/vfs_vnops.c: In function 'vn_ioctl': /usr/src/sys/kern/vfs_vnops.c:750: error: 'vn_lock' undeclared (first use i= n this function) /usr/src/sys/kern/vfs_vnops.c:750: error: (Each undeclared identifier is re= ported only once /usr/src/sys/kern/vfs_vnops.c:750: error: for each function it appears in.) /usr/src/sys/kern/vfs_vnops.c:769: error: too few arguments to function 'VO= P_UNLOCK' *** Error code 1 This problem with crashes I have after cPanel update perl to version 5.10.0... Can some body tell me - is this global problem of FreeBSD or it only with my installation? > [Please, remove the questions@ on the reply, this is the topic for > fs@]. > On Sat, Jun 06, 2009 at 08:16:00PM +0400, Chagin Dmitry wrote: >> ----- Forwarded message from georg@dts.su ----- >>=20 >> Date: Sat, 6 Jun 2009 10:58:11 +0400 >> From: georg@dts.su >> To: freebsd-questions@freebsd.org >> Subject: Re[2]: fatal trap 12 >>=20 >> Hello, Freebsd-questions. >>=20 >> After one of new crash I have this: >>=20 >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you= are >> welcome to change it and/or distribute copies of it under certain condit= ions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for detai= ls. >> This GDB was configured as "amd64-marcel-freebsd"... >>=20 >> Unread portion of the kernel message buffer: >>=20 >>=20 >> Fatal trap 12: page fault while in kernel mode >> cpuid =3D 2; apic id =3D 02 >> fault virtual address =3D 0x0 >> fault code =3D supervisor read data, page not present >> instruction pointer =3D 0x8:0xffffffff804c4eb8 >> stack pointer =3D 0x10:0xffffff807a0478f0 >> frame pointer =3D 0x10:0xffffff807a047930 >> code segment =3D base 0x0, limit 0xfffff, type 0x1b >> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >> current process =3D 32668 (perl5.10.0) >> Physical memory: 4082 MB >> Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 = 1456 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 = 1216 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 9= 76 960 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 = 672 656 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384= 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 = 64 48 32 16 >>=20 >> Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from /b= oot/kernel/accf_http.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/accf_http.ko >> #0 doadump () at pcpu.h:195 >> 195 __asm __volatile("movq %%gs:0,%0" : "=3Dr" (td)); >> (kgdb) list *0xffffffff804c4eb8 >> 0xffffffff804c4eb8 is in pfs_ioctl (/usr/src/sys/fs/pseudofs/pseudofs_vn= ops.c:265). >> 260 static int >> 261 pfs_ioctl(struct vop_ioctl_args *va) >> 262 { >> 263 struct vnode *vn =3D va->a_vp; >> 264 struct pfs_vdata *pvd =3D vn->v_data; >> 265 struct pfs_node *pn =3D pvd->pvd_pn; >> 266 struct proc *proc; >> 267 int error; >> 268 >> 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); >> (kgdb) backtrace >> #0 doadump () at pcpu.h:195 >> #1 0xffffffff801c8dac in db_fncall (dummy1=3DVariable "dummy1" is not a= vailable. >> ) at /usr/src/sys/ddb/db_command.c:516 >> #2 0xffffffff801c92df in db_command (last_cmdp=3D0xffffffff80b30c88, cm= d_table=3D0x0, dopager=3D1) at /usr/src/sys/ddb/db_command.c:413 >> #3 0xffffffff801c94f0 in db_command_loop () at /usr/src/sys/ddb/db_comm= and.c:466 >> #4 0xffffffff801cb0d9 in db_trap (type=3DVariable "type" is not availab= le. >> ) at /usr/src/sys/ddb/db_main.c:228 >> #5 0xffffffff80554e55 in kdb_trap (type=3D12, code=3D0, tf=3D0xffffff80= 7a047840) at /usr/src/sys/kern/subr_kdb.c:524 >> #6 0xffffffff807fae80 in trap_fatal (frame=3D0xffffff807a047840, eva=3D= Variable "eva" is not available. >> ) at /usr/src/sys/amd64/amd64/trap.c:752 >> #7 0xffffffff807fb254 in trap_pfault (frame=3D0xffffff807a047840, userm= ode=3D0) at /usr/src/sys/amd64/amd64/trap.c:673 >> #8 0xffffffff807fbc02 in trap (frame=3D0xffffff807a047840) at /usr/src/= sys/amd64/amd64/trap.c:444 >> #9 0xffffffff807df35e in calltrap () at /usr/src/sys/amd64/amd64/except= ion.S:209 >> #10 0xffffffff804c4eb8 in pfs_ioctl (va=3D0xffffff807a047a10) at /usr/sr= c/sys/fs/pseudofs/pseudofs_vnops.c:264 >> #11 0xffffffff805bb1d3 in vn_ioctl (fp=3DVariable "fp" is not available. >> ) at vnode_if.h:437 >> #12 0xffffffff80562d02 in kern_ioctl (td=3D0xffffff0006682000, fd=3D3, c= om=3D1076655123, data=3D0xffffff00ad2b7d40 "") at file.h:269 >> #13 0xffffffff80563029 in ioctl (td=3D0xffffff0006682000, uap=3D0xffffff= 807a047bf0) at /usr/src/sys/kern/sys_generic.c:571 >> #14 0xffffffff807fb4d6 in syscall (frame=3D0xffffff807a047c80) at /usr/s= rc/sys/amd64/amd64/trap.c:900 >> #15 0xffffffff807df56b in Xfast_syscall () at /usr/src/sys/amd64/amd64/e= xception.S:330 >> #16 0x0000000800c9c0ec in ?? () >> Previous frame inner to this frame (corrupt stack?) >> (kgdb) >>=20 >>=20 >> Can You help me? What can I do? Server crash periodicaly... > The issue is that VOP_IOCTL interface takes unlocked vnode, which > may be reclaimed at any moment. The right thing to do is to fix > this before 8.0 freezed KPI. Please, try the patch below. > diff --git > a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c > b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c > index a7f47b2..018e6bd 100644 > --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c > +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c > @@ -258,7 +258,7 @@ zfs_ioctl(vnode_t *vp, u_long com, intptr_t data, int= flag, cred_t *cred, > int *rvalp, caller_context_t *ct) > { > offset_t off; > - int error; > + int error, locked; > zfsvfs_t *zfsvfs; > znode_t *zp; > =20 > @@ -276,6 +276,8 @@ zfs_ioctl(vnode_t *vp, u_long com, intptr_t data, int= flag, cred_t *cred, > =20 > case _FIO_SEEK_DATA: > case _FIO_SEEK_HOLE: > + locked =3D VOP_ISLOCKED(vp); > + VOP_UNLOCK(vp, 0); > if (ddi_copyin((void *)data, &off, sizeof (off), flag)) > return (EFAULT); > =20 > @@ -287,10 +289,15 @@ zfs_ioctl(vnode_t *vp, u_long com, intptr_t data, i= nt flag, cred_t *cred, > /* offset parameter is in/out */ > error =3D zfs_holey(vp, com, &off); > ZFS_EXIT(zfsvfs); > - if (error) > + if (error) { > + vn_lock(vp, locked | LK_RETRY); > return (error); > - if (ddi_copyout(&off, (void *)data, sizeof (off), flag)) > + } > + if (ddi_copyout(&off, (void *)data, sizeof (off), flag)) { > + vn_lock(vp, locked | LK_RETRY); > return (EFAULT); > + } > + vn_lock(vp, locked | LK_RETRY); > return (0); > } > return (ENOTTY); > diff --git a/sys/fs/coda/coda_vnops.c b/sys/fs/coda/coda_vnops.c > index c5c6cb1..0bf84c4 100644 > --- a/sys/fs/coda/coda_vnops.c > +++ b/sys/fs/coda/coda_vnops.c > @@ -420,7 +420,7 @@ coda_ioctl(struct vop_ioctl_args *ap) > struct ucred *cred =3D ap->a_cred; > struct thread *td =3D ap->a_td; > /* locals */ > - int error; > + int error, locked; > struct vnode *tvp; > struct nameidata ndp; > struct PioctlData *iap =3D (struct PioctlData *)data; > @@ -440,6 +440,8 @@ coda_ioctl(struct vop_ioctl_args *ap) > "ctlvp"));); > return (EOPNOTSUPP); > } > + locked =3D VOP_ISLOCKED(vp); > + VOP_UNLOCK(vp, 0); > =20 > /* > * Look up the pathname. > @@ -455,7 +457,7 @@ coda_ioctl(struct vop_ioctl_args *ap) > MARK_INT_FAIL(CODA_IOCTL_STATS); > CODADEBUG(CODA_IOCTL, myprintf(("coda_ioctl error: lookup= " > "returns %d\n", error));); > - return (error); > + goto out; > } > =20 > /* > @@ -469,11 +471,13 @@ coda_ioctl(struct vop_ioctl_args *ap) > CODADEBUG(CODA_IOCTL, > myprintf(("coda_ioctl error: %s not a coda object\n", > iap->path));); > - return (EINVAL); > + error =3D EINVAL; > + goto out; > } > if (iap->vi.in_size > VC_MAXDATASIZE) { > NDFREE(&ndp, 0); > - return (EINVAL); > + error =3D EINVAL; > + goto out; > } > error =3D venus_ioctl(vtomi(tvp), &((VTOC(tvp))->c_fid), com, fla= g, > data, cred, td->td_proc); > @@ -484,6 +488,8 @@ coda_ioctl(struct vop_ioctl_args *ap) > error));); > vrele(tvp); > NDFREE(&ndp, NDF_ONLY_PNBUF); > + out: > + vn_lock(vp, locked | LK_RETRY); > return (error); > } > =20 > diff --git a/sys/fs/deadfs/dead_vnops.c b/sys/fs/deadfs/dead_vnops.c > index 7a07b38..22029a7 100644 > --- a/sys/fs/deadfs/dead_vnops.c > +++ b/sys/fs/deadfs/dead_vnops.c > @@ -180,8 +180,8 @@ dead_ioctl(ap) > struct proc *a_p; > } */ *ap; > { > - /* XXX: Doesn't this just recurse back here ? */ > - return (VOP_IOCTL_AP(ap)); > + > + return (EIO); > } > =20 > /* > diff --git a/sys/fs/fifofs/fifo_vnops.c b/sys/fs/fifofs/fifo_vnops.c > index 66963bc..8d20297 100644 > --- a/sys/fs/fifofs/fifo_vnops.c > +++ b/sys/fs/fifofs/fifo_vnops.c > @@ -89,8 +89,6 @@ struct fifoinfo { > static vop_print_t fifo_print; > static vop_open_t fifo_open; > static vop_close_t fifo_close; > -static vop_ioctl_t fifo_ioctl; > -static vop_kqfilter_t fifo_kqfilter; > static vop_pathconf_t fifo_pathconf; > static vop_advlock_t fifo_advlock; > =20 > @@ -116,8 +114,8 @@ struct vop_vector fifo_specops =3D { > .vop_close =3D fifo_close, > .vop_create =3D VOP_PANIC, > .vop_getattr =3D VOP_EBADF, > - .vop_ioctl =3D fifo_ioctl, > - .vop_kqfilter =3D fifo_kqfilter, > + .vop_ioctl =3D VOP_PANIC, > + .vop_kqfilter =3D VOP_PANIC, > .vop_link =3D VOP_PANIC, > .vop_mkdir =3D VOP_PANIC, > .vop_mknod =3D VOP_PANIC, > @@ -300,42 +298,6 @@ fail1: > return (0); > } > =20 > -/* > - * Now unused vnode ioctl routine. > - */ > -/* ARGSUSED */ > -static int > -fifo_ioctl(ap) > - struct vop_ioctl_args /* { > - struct vnode *a_vp; > - u_long a_command; > - caddr_t a_data; > - int a_fflag; > - struct ucred *a_cred; > - struct thread *a_td; > - } */ *ap; > -{ > - > - printf("WARNING: fifo_ioctl called unexpectedly\n"); > - return (ENOTTY); > -} > - > -/* > - * Now unused vnode kqfilter routine. > - */ > -/* ARGSUSED */ > -static int > -fifo_kqfilter(ap) > - struct vop_kqfilter_args /* { > - struct vnode *a_vp; > - struct knote *a_kn; > - } */ *ap; > -{ > - > - printf("WARNING: fifo_kqfilter called unexpectedly\n"); > - return (EINVAL); > -} > - > static void > filt_fifordetach(struct knote *kn) > { > diff --git a/sys/fs/unionfs/union_vnops.c b/sys/fs/unionfs/union_vnops.c > index 8505cac..6f5d555 100644 > --- a/sys/fs/unionfs/union_vnops.c > +++ b/sys/fs/unionfs/union_vnops.c > @@ -913,12 +913,10 @@ unionfs_ioctl(struct vop_ioctl_args *ap) > =20 > KASSERT_UNIONFS_VNODE(ap->a_vp); > =20 - vn_lock(ap->>a_vp, LK_EXCLUSIVE | LK_RETRY); > unp =3D VTOUNIONFS(ap->a_vp); > unionfs_get_node_status(unp, ap->a_td, &unsp); > ovp =3D (unsp->uns_upper_opencnt ? unp->un_uppervp : unp->un_lowe= rvp); > unionfs_tryrem_node_status(unp, unsp); > - VOP_UNLOCK(ap->a_vp, 0); > =20 > if (ovp =3D=3D NULLVP) > return (EBADF); > diff --git a/sys/gnu/fs/xfs/FreeBSD/xfs_vnops.c > b/sys/gnu/fs/xfs/FreeBSD/xfs_vnops.c > index 6d8d4eb..9b2c4b0 100644 > --- a/sys/gnu/fs/xfs/FreeBSD/xfs_vnops.c > +++ b/sys/gnu/fs/xfs/FreeBSD/xfs_vnops.c > @@ -1163,17 +1163,20 @@ _xfs_ioctl( > struct thread *a_td; > } */ *ap) > { > -/* struct vnode *vp =3D ap->a_vp; */ > + struct vnode *vp =3D ap->a_vp; > /* struct thread *p =3D ap->a_td; */ > /* struct file *fp; */ > - int error; > + int error, locked; > =20 > - xfs_vnode_t *xvp =3D VPTOXFSVP(ap->a_vp); > + xfs_vnode_t *xvp =3D VPTOXFSVP(vp); > =20 > printf("_xfs_ioctl cmd 0x%lx data %p\n",ap->a_command,ap->a_data); > =20 > + locked =3D VOP_ISLOCKED(vp); > + VOP_UNLOCK(vp, 0); > // XVOP_IOCTL(xvp,(void *)NULL,(void > *)NULL,ap->a_fflag,ap->a_command,ap->a_data,error); > error =3D > xfs_ioctl(xvp->v_bh.bh_first,NULL,NULL,ap->a_fflag,ap->a_command,ap->a_da= ta); > + vn_lock(vp, locked | LK_RETRY); > =20 > return error; > } > diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c > index 702faae..e48f81f 100644 > --- a/sys/kern/vfs_vnops.c > +++ b/sys/kern/vfs_vnops.c > @@ -817,13 +817,12 @@ vn_ioctl(fp, com, data, active_cred, td) > =20 > vfslocked =3D VFS_LOCK_GIANT(vp->v_mount); > error =3D ENOTTY; > + vn_lock(vp, LK_EXCLUSIVE | LK_RETRY); > switch (vp->v_type) { > case VREG: > case VDIR: > if (com =3D=3D FIONREAD) { > - vn_lock(vp, LK_EXCLUSIVE | LK_RETRY); > error =3D VOP_GETATTR(vp, &vattr, active_cred); > - VOP_UNLOCK(vp, 0); > if (!error) > *(int *)data =3D vattr.va_size - fp->f_of= fset; > } > @@ -837,6 +836,7 @@ vn_ioctl(fp, com, data, active_cred, td) > default: > break; > } > + VOP_UNLOCK(vp, 0); > VFS_UNLOCK_GIANT(vfslocked); > return (error); > } > diff --git a/sys/kern/vnode_if.src b/sys/kern/vnode_if.src > index 81c0dff..81ef11c 100644 > --- a/sys/kern/vnode_if.src > +++ b/sys/kern/vnode_if.src > @@ -209,7 +209,7 @@ vop_write { > }; > =20 > =20 > -%% ioctl vp U U U > +%% ioctl vp L L L > =20 > vop_ioctl { > IN struct vnode *vp; --=20 Regards Yura mailto:georg@dts.su From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 12:55:44 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C20851065672 for ; Sun, 7 Jun 2009 12:55:44 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by mx1.freebsd.org (Postfix) with ESMTP id 41FC18FC1D for ; Sun, 7 Jun 2009 12:55:43 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: by fxm11 with SMTP id 11so201137fxm.43 for ; Sun, 07 Jun 2009 05:55:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=oe1hpDlw0GPoZmh9Q3iKMtUOq904yM0EiRkDMuKro3E=; b=psfAgPmVoLoMeCWglS6tbvtPLiQg7Er1kmAFtCToVYQt7kG+aftRApZ71zV7w1wpH2 ftOv2fD2/++8GPdtzO6kzjQltKKztlxxGJGHNO2rYvgVIepKAzTFvqVn1jAE+W/HOxIz g1ns41hhI4w6zKSgykF7zHNLCLvNUo0KrtfNU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=LIQ5xsa0Jj0apIfmbapxbJ3BGGoOHsqp0IsOsTloPUGkorr7UTmGnBB7S9RRqewdkF yoWV0+Y9GbasfNCE5uYVs1dq2MCnej6FVMUNkoJdlR0x5cwJ0QtMaC5scSpPT3x9SpA4 nUB7KqNSvwwpSMiLqkyDqelEcoizJx5ZE+jx8= MIME-Version: 1.0 Received: by 10.239.179.19 with SMTP id b19mr400480hbg.2.1244379343066; Sun, 07 Jun 2009 05:55:43 -0700 (PDT) In-Reply-To: <4A2A7DE4.1080008@egr.msu.edu> References: <4A2A7DE4.1080008@egr.msu.edu> From: "Yan V. Batuto" Date: Sun, 7 Jun 2009 16:55:23 +0400 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Strange ZFS pool failure after updating kernel v6->v13 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, 07 Jun 2009 12:55:45 -0000 2009/6/6 Adam McDougall : > Yan V. Batuto wrote: >> >> Hello! >> >> RAID-Z v6 works OK with 7.2-RELEASE, but it fails with recent 7.2-STABLE= . >> -------------------------------------------------- >> # zpool status bigstore >> =A0pool: bigstore >> =A0state: ONLINE >> =A0scrub: scrub completed with 0 errors on Fri Jun =A05 22:28:19 2009 >> config: >> >> =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM >> =A0 =A0 =A0 =A0bigstore =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0raidz1 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 = 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad4 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad6 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad8 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad10 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> >> errors: No known data errors >> -------------------------------------------------- >> After cvsup to 7-STABLE, usual procedure of rebuilding kernel and >> world, and reboot pool is failed. >> It's quite strange that now pool consists of ad8, ad10, and again ad8, >> ad10 drives instead of ad4, ad6, ad8, ad10. >> >> I removed additional disk controller few weeks ago, so raid-z >> originally was created as ad8+ad10+ad12+ad14, and then >> it appeared to be ad4+ad6+ad8+ad10. It was not a trouble for zfs v6, >> but, probably, something is wrong here in zfs v13. >> -------------------------------------------------- >> # zpool status bigstore >> pool: bigstore >> =A0state: UNAVAIL >> status: One or more devices could not be used because the label is missi= ng >> =A0 =A0 =A0 =A0or invalid. =A0There are insufficient replicas for the po= ol to >> continue >> =A0 =A0 =A0 =A0functioning. >> action: Destroy and re-create the pool from a backup source. >> =A0 see: http://www.sun.com/msg/ZFS-8000-5E >> =A0scrub: none requested >> config: >> >> =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM >> =A0 =A0 =A0 =A0bigstore =A0 =A0UNAVAIL =A0 =A0 =A00 =A0 =A0 0 =A0 =A0 0 = =A0insufficient replicas >> =A0 =A0 =A0 =A0 =A0raidz1 =A0 =A0UNAVAIL =A0 =A0 =A00 =A0 =A0 0 =A0 =A0 = 0 =A0insufficient replicas >> =A0 =A0 =A0 =A0 =A0 =A0ad8 =A0 =A0 FAULTED =A0 =A0 =A00 =A0 =A0 0 =A0 = =A0 0 =A0corrupted data >> =A0 =A0 =A0 =A0 =A0 =A0ad10 =A0 =A0FAULTED =A0 =A0 =A00 =A0 =A0 0 =A0 = =A0 0 =A0corrupted data >> =A0 =A0 =A0 =A0 =A0 =A0ad8 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad10 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> > > Please try: > zpool export bigstore > zpool import bigstore > > This should make it find the right hard drives if they are present, > otherwise should give a more informative error. > Thank you! I exported pool on 7.2-release, then upgraded to 7.2-stable and imported the pool back. All works OK. From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 13:40:44 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 793741065678 for ; Sun, 7 Jun 2009 13:40:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id D503F8FC13 for ; Sun, 7 Jun 2009 13:40:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1MDIc5-0007im-SI; Sun, 07 Jun 2009 16:40:42 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n57Dedn2018848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Jun 2009 16:40:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n57Ded7U058833; Sun, 7 Jun 2009 16:40:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n57Dec1M058832; Sun, 7 Jun 2009 16:40:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 7 Jun 2009 16:40:38 +0300 From: Kostik Belousov To: georg@dts.su Message-ID: <20090607134038.GL1927@deviant.kiev.zoral.com.ua> References: <20090606161600.GB61928@dchagin.static.corbina.ru> <20090606175033.GJ1927@deviant.kiev.zoral.com.ua> <49009886.20090607153452@dts.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w7hfNuAEqLXjQNlZ" Content-Disposition: inline In-Reply-To: <49009886.20090607153452@dts.su> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.1 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1MDIc5-0007im-SI 1ac800ff95eb48127254245b76c83af1 X-Terabit: YES Cc: freebsd-fs@freebsd.org Subject: Re: fatal trap 12 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, 07 Jun 2009 13:40:45 -0000 --w7hfNuAEqLXjQNlZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I asked to remove questions@, isn't it ? On Sun, Jun 07, 2009 at 03:34:52PM +0400, georg@dts.su wrote: > Hello. >=20 > After patch, whan make kernel I have this: > /usr/src/sys/kern/vfs_vnops.c:750:37: error: macro "vn_lock" requires 3 a= rguments, but only 2 given > /usr/src/sys/kern/vfs_vnops.c: In function 'vn_ioctl': > /usr/src/sys/kern/vfs_vnops.c:750: error: 'vn_lock' undeclared (first use= in this function) > /usr/src/sys/kern/vfs_vnops.c:750: error: (Each undeclared identifier is = reported only once > /usr/src/sys/kern/vfs_vnops.c:750: error: for each function it appears in= .) > /usr/src/sys/kern/vfs_vnops.c:769: error: too few arguments to function '= VOP_UNLOCK' > *** Error code 1 >=20 The patch is for HEAD. You did not specified the version of your system. For RELENG_7, patch shall be adopted by adding curthread parameter to several calls, among them are vn_lock, VOP_ISLOCKED and VOP_UNLOCK(). The patch probably cannot be merged to RELENG_7 due to KBI breakage. There, I think the following workaround for pseudofs might be enough, but it would be also needed for cd9660 and devfs at least. Try this. Index: fs/pseudofs/pseudofs_vnops.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- fs/pseudofs/pseudofs_vnops.c (revision 193634) +++ fs/pseudofs/pseudofs_vnops.c (working copy) @@ -260,34 +260,51 @@ static int pfs_ioctl(struct vop_ioctl_args *va) { - struct vnode *vn =3D va->a_vp; - struct pfs_vdata *pvd =3D vn->v_data; - struct pfs_node *pn =3D pvd->pvd_pn; + struct vnode *vn; + struct pfs_vdata *pvd; + struct pfs_node *pn; struct proc *proc; + struct thread *td; int error; =20 + vn =3D va->a_vp; + td =3D curthread; + vn_lock(vn, LK_SHARED | LK_RETRY, td); + if (vn->v_iflag & VI_DOOMED) { + VOP_UNLOCK(vn, 0, td); + return (EBADF); + } + pvd =3D vn->v_data; + pn =3D pvd->pvd_pn; PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); pfs_assert_not_owned(pn); =20 - if (vn->v_type !=3D VREG) + if (vn->v_type !=3D VREG) { + VOP_UNLOCK(vn, 0, td); PFS_RETURN (EINVAL); + } KASSERT_PN_IS_FILE(pn); =20 - if (pn->pn_ioctl =3D=3D NULL) + if (pn->pn_ioctl =3D=3D NULL) { + VOP_UNLOCK(vn, 0, td); PFS_RETURN (ENOTTY); + } =20 /* * This is necessary because process' privileges may * have changed since the open() call. */ - if (!pfs_visible(curthread, pn, pvd->pvd_pid, &proc)) + if (!pfs_visible(curthread, pn, pvd->pvd_pid, &proc)) { + VOP_UNLOCK(vn, 0, td); PFS_RETURN (EIO); + } =20 error =3D pn_ioctl(curthread, proc, pn, va->a_command, va->a_data); =20 if (proc !=3D NULL) PROC_UNLOCK(proc); =20 + VOP_UNLOCK(vn, 0, td); PFS_RETURN (error); } =20 Index: fs/devfs/devfs_vnops.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- fs/devfs/devfs_vnops.c (revision 193634) +++ fs/devfs/devfs_vnops.c (working copy) @@ -1240,11 +1240,21 @@ static int devfs_rioctl(struct vop_ioctl_args *ap) { + struct vnode *vp; + struct devfs_mount *dmp; + struct thread *td; int error; - struct devfs_mount *dmp; =20 + vp =3D ap->a_vp; + td =3D ap->a_td; + vn_lock(vp, LK_SHARED | LK_RETRY, td); + if (vp->v_iflag & VI_DOOMED) { + VOP_UNLOCK(vp, 0, td); + return (EBADF); + } dmp =3D VFSTODEVFS(ap->a_vp->v_mount); sx_xlock(&dmp->dm_lock); + VOP_UNLOCK(vp, 0, td); DEVFS_DMP_HOLD(dmp); devfs_populate(dmp); if (DEVFS_DMP_DROP(dmp)) { @@ -1252,7 +1262,7 @@ devfs_unmount_final(dmp); return (ENOENT); } - error =3D devfs_rules_ioctl(dmp, ap->a_command, ap->a_data, ap->a_td); + error =3D devfs_rules_ioctl(dmp, ap->a_command, ap->a_data, td); sx_xunlock(&dmp->dm_lock); return (error); } Index: fs/cd9660/cd9660_vnops.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- fs/cd9660/cd9660_vnops.c (revision 193634) +++ fs/cd9660/cd9660_vnops.c (working copy) @@ -253,20 +253,37 @@ struct thread *a_td; } */ *ap; { - struct vnode *vp =3D ap->a_vp; - struct iso_node *ip =3D VTOI(vp); + struct vnode *vp; + struct iso_node *ip; + struct thread *td; + int error; =20 - if (vp->v_type =3D=3D VCHR || vp->v_type =3D=3D VBLK) - return (EOPNOTSUPP); + vp =3D ap->a_vp; + td =3D ap->a_td; + vn_lock(vp, LK_SHARED | LK_RETRY, td); + if (vp->v_iflag & VI_DOOMED) { + error =3D EBADF; + goto out; + } + ip =3D VTOI(vp); + if (vp->v_type =3D=3D VCHR || vp->v_type =3D=3D VBLK) { + error =3D EOPNOTSUPP; + goto out; + } =20 + error =3D 0; switch (ap->a_command) { - case FIOGETLBA: *(int *)(ap->a_data) =3D ip->iso_start; - return 0; + break; default: - return (ENOTTY); + error =3D ENOTTY; + break; } + +out: + VOP_UNLOCK(vp, 0, td); + return (error); } =20 /* --w7hfNuAEqLXjQNlZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkorw1YACgkQC3+MBN1Mb4jcfgCgoe1ex+B/sAhalWfsrwYsTg/A Jw8AoIb9Rr3Lc9GwuKQ4X/8xQ9TEFhAf =9YF5 -----END PGP SIGNATURE----- --w7hfNuAEqLXjQNlZ-- From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 15:21:50 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB614106566B for ; Sun, 7 Jun 2009 15:21:50 +0000 (UTC) (envelope-from georg@dts.su) Received: from host4.symbios.ru (host4.symbios.ru [80.84.112.82]) by mx1.freebsd.org (Postfix) with ESMTP id 749D88FC08 for ; Sun, 7 Jun 2009 15:21:50 +0000 (UTC) (envelope-from georg@dts.su) Received: from [127.0.0.1] (helo=WORLDMY) by host4.symbios.ru with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MDKBw-000Bxc-0b for freebsd-fs@freebsd.org; Sun, 07 Jun 2009 19:21:48 +0400 Received: from WORLDMY ([80.84.121.226] helo=WORLDMY) with IPv4:25 by host4.symbios.ru; 7 Jun 2009 19:21:47 +0400 Date: Sun, 7 Jun 2009 19:21:46 +0400 From: georg@dts.su Organization: dts.su X-Priority: 3 (Normal) Message-ID: <1186509222.20090607192146@dts.su> To: freebsd-fs@freebsd.org In-Reply-To: <20090607134038.GL1927@deviant.kiev.zoral.com.ua> References: <20090606161600.GB61928@dchagin.static.corbina.ru> <20090606175033.GJ1927@deviant.kiev.zoral.com.ua> <49009886.20090607153452@dts.su> <20090607134038.GL1927@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable X-Assp-Whitelisted: Yes X-Assp-Envelope-From: georg@dts.su X-Assp-Intended-For: freebsd-fs@freebsd.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host4.symbios.ru X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [26 6] / [26 6] X-AntiAbuse: Sender Address Domain - dts.su Subject: Re[2]: fatal trap 12 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: georg@dts.su List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jun 2009 15:21:51 -0000 Hello, Kostik. Have this after apply patch: cc1: warnings being treated as errors /usr/src/sys/fs/pseudofs/pseudofs_vnops.c: In function 'pfs_ioctl': /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265: warning: 'pn' is used uninit= ialized in this function /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:295: warning: 'pvd' is used unini= tialized in this function *** Error code 1 > I asked to remove questions@, isn't it ? > On Sun, Jun 07, 2009 at 03:34:52PM +0400, georg@dts.su wrote: >> Hello. >>=20 >> After patch, whan make kernel I have this: >> /usr/src/sys/kern/vfs_vnops.c:750:37: error: macro "vn_lock" requires 3 = arguments, but only 2 given >> /usr/src/sys/kern/vfs_vnops.c: In function 'vn_ioctl': >> /usr/src/sys/kern/vfs_vnops.c:750: error: 'vn_lock' undeclared (first us= e in this function) >> /usr/src/sys/kern/vfs_vnops.c:750: error: (Each undeclared identifier is= reported only once >> /usr/src/sys/kern/vfs_vnops.c:750: error: for each function it appears i= n.) >> /usr/src/sys/kern/vfs_vnops.c:769: error: too few arguments to function = 'VOP_UNLOCK' >> *** Error code 1 >>=20 > The patch is for HEAD. You did not specified the version of your system. > For RELENG_7, patch shall be adopted by adding curthread parameter > to several calls, among them are vn_lock, VOP_ISLOCKED and VOP_UNLOCK(). > The patch probably cannot be merged to RELENG_7 due to KBI breakage. > There, I think the following workaround for pseudofs might be enough, > but it would be also needed for cd9660 and devfs at least. > Try this. > Index: fs/pseudofs/pseudofs_vnops.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- fs/pseudofs/pseudofs_vnops.c (revision 193634) > +++ fs/pseudofs/pseudofs_vnops.c (working copy) > @@ -260,34 +260,51 @@ > static int > pfs_ioctl(struct vop_ioctl_args *va) > { > - struct vnode *vn =3D va->a_vp; > - struct pfs_vdata *pvd =3D vn->v_data; > - struct pfs_node *pn =3D pvd->pvd_pn; > + struct vnode *vn; > + struct pfs_vdata *pvd; > + struct pfs_node *pn; > struct proc *proc; > + struct thread *td; > int error; > =20 + vn =3D va->>a_vp; > + td =3D curthread; > + vn_lock(vn, LK_SHARED | LK_RETRY, td); + if (vn->>v_iflag & VI_DOOMED) { > + VOP_UNLOCK(vn, 0, td); > + return (EBADF); > + } + pvd =3D vn->>v_data; + pn =3D pvd->>pvd_pn; > PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); > pfs_assert_not_owned(pn); > =20 - if (vn->>v_type !=3D VREG) + if (vn->>v_type !=3D VREG) { > + VOP_UNLOCK(vn, 0, td); > PFS_RETURN (EINVAL); > + } > KASSERT_PN_IS_FILE(pn); > =20 - if (pn->>pn_ioctl =3D=3D NULL) + if (pn->>pn_ioctl =3D=3D NULL) { > + VOP_UNLOCK(vn, 0, td); > PFS_RETURN (ENOTTY); > + } > =20 > /* > * This is necessary because process' privileges may > * have changed since the open() call. > */ > - if (!pfs_visible(curthread, pn, pvd->pvd_pid, &proc)) > + if (!pfs_visible(curthread, pn, pvd->pvd_pid, &proc)) { > + VOP_UNLOCK(vn, 0, td); > PFS_RETURN (EIO); > + } > =20 > error =3D pn_ioctl(curthread, proc, pn, va->a_command, va->a_data= ); > =20 > if (proc !=3D NULL) > PROC_UNLOCK(proc); > =20 > + VOP_UNLOCK(vn, 0, td); > PFS_RETURN (error); > } > =20 > Index: fs/devfs/devfs_vnops.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- fs/devfs/devfs_vnops.c (revision 193634) > +++ fs/devfs/devfs_vnops.c (working copy) > @@ -1240,11 +1240,21 @@ > static int > devfs_rioctl(struct vop_ioctl_args *ap) > { > + struct vnode *vp; > + struct devfs_mount *dmp; > + struct thread *td; > int error; > - struct devfs_mount *dmp; > =20 + vp =3D ap->>a_vp; + td =3D ap->>a_td; > + vn_lock(vp, LK_SHARED | LK_RETRY, td); + if (vp->>v_iflag & VI_DOOMED) { > + VOP_UNLOCK(vp, 0, td); > + return (EBADF); > + } > dmp =3D VFSTODEVFS(ap->a_vp->v_mount); > sx_xlock(&dmp->dm_lock); > + VOP_UNLOCK(vp, 0, td); > DEVFS_DMP_HOLD(dmp); > devfs_populate(dmp); > if (DEVFS_DMP_DROP(dmp)) { > @@ -1252,7 +1262,7 @@ > devfs_unmount_final(dmp); > return (ENOENT); > } > - error =3D devfs_rules_ioctl(dmp, ap->a_command, ap->a_data, ap->a= _td); > + error =3D devfs_rules_ioctl(dmp, ap->a_command, ap->a_data, td); > sx_xunlock(&dmp->dm_lock); > return (error); > } > Index: fs/cd9660/cd9660_vnops.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- fs/cd9660/cd9660_vnops.c (revision 193634) > +++ fs/cd9660/cd9660_vnops.c (working copy) > @@ -253,20 +253,37 @@ > struct thread *a_td; > } */ *ap; > { > - struct vnode *vp =3D ap->a_vp; > - struct iso_node *ip =3D VTOI(vp); > + struct vnode *vp; > + struct iso_node *ip; > + struct thread *td; > + int error; > =20 - if (vp->>v_type =3D=3D VCHR || vp->v_type =3D=3D VBLK) > - return (EOPNOTSUPP); + vp =3D ap->>a_vp; + td =3D ap->>a_td; > + vn_lock(vp, LK_SHARED | LK_RETRY, td); + if (vp->>v_iflag & VI_DOOMED) { > + error =3D EBADF; > + goto out; > + } > + ip =3D VTOI(vp); + if (vp->>v_type =3D=3D VCHR || vp->v_type =3D=3D VBLK) { > + error =3D EOPNOTSUPP; > + goto out; > + } > =20 > + error =3D 0; > switch (ap->a_command) { > - > case FIOGETLBA: > *(int *)(ap->a_data) =3D ip->iso_start; > - return 0; > + break; > default: > - return (ENOTTY); > + error =3D ENOTTY; > + break; > } > + > +out: > + VOP_UNLOCK(vp, 0, td); > + return (error); > } > =20 > /* --=20 Regards, Yura mailto:georg@dts.su From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 15:30:17 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A966106566C for ; Sun, 7 Jun 2009 15:30:17 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id B1BEB8FC0C for ; Sun, 7 Jun 2009 15:30:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1MDKK7-000FV2-AD; Sun, 07 Jun 2009 18:30:15 +0300 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n57FU0CB023947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Jun 2009 18:30:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n57FU0a6061759; Sun, 7 Jun 2009 18:30:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n57FU019061758; Sun, 7 Jun 2009 18:30:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 7 Jun 2009 18:30:00 +0300 From: Kostik Belousov To: georg@dts.su Message-ID: <20090607153000.GM1927@deviant.kiev.zoral.com.ua> References: <20090606161600.GB61928@dchagin.static.corbina.ru> <20090606175033.GJ1927@deviant.kiev.zoral.com.ua> <49009886.20090607153452@dts.su> <20090607134038.GL1927@deviant.kiev.zoral.com.ua> <1186509222.20090607192146@dts.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LM+hxBhiTm1iA4lZ" Content-Disposition: inline In-Reply-To: <1186509222.20090607192146@dts.su> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.1 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1MDKK7-000FV2-AD bcbc3bba4dc2343f073b10da5899ef16 X-Terabit: YES Cc: freebsd-fs@freebsd.org Subject: Re: fatal trap 12 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, 07 Jun 2009 15:30:17 -0000 --LM+hxBhiTm1iA4lZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 07, 2009 at 07:21:46PM +0400, georg@dts.su wrote: > Hello, Kostik. >=20 > Have this after apply patch: > cc1: warnings being treated as errors > /usr/src/sys/fs/pseudofs/pseudofs_vnops.c: In function 'pfs_ioctl': > /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265: warning: 'pn' is used unin= itialized in this function > /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:295: warning: 'pvd' is used uni= nitialized in this function > *** Error code 1 I already asked about the version of your source tree. Please answer. I do not see how these warnings might happen on the RELENG_7, and line numbers do not correspond to line numbers of RELENG_7 + patch. --LM+hxBhiTm1iA4lZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkor3PcACgkQC3+MBN1Mb4hckwCgp96C+EHmOBLumQc4sjV6PDaP wSUAoMzEMOE1XtYyjVKDdNr+Sjc0NA5Z =9VlD -----END PGP SIGNATURE----- --LM+hxBhiTm1iA4lZ-- From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 19:24:18 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34967106566B for ; Sun, 7 Jun 2009 19:24:18 +0000 (UTC) (envelope-from georg@dts.su) Received: from host4.symbios.ru (host4.symbios.ru [80.84.112.82]) by mx1.freebsd.org (Postfix) with ESMTP id DB00E8FC18 for ; Sun, 7 Jun 2009 19:24:17 +0000 (UTC) (envelope-from georg@dts.su) Received: from [127.0.0.1] (helo=WORLDMY) by host4.symbios.ru with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MDNyZ-000Lq6-0w for freebsd-fs@freebsd.org; Sun, 07 Jun 2009 23:24:15 +0400 Received: from WORLDMY ([80.84.121.226] helo=WORLDMY) with IPv4:25 by host4.symbios.ru; 7 Jun 2009 23:24:13 +0400 Date: Sun, 7 Jun 2009 23:24:12 +0359 From: georg@dts.su Organization: dts.su X-Priority: 3 (Normal) Message-ID: <954682534.20090607232412@dts.su> To: freebsd-fs@freebsd.org In-Reply-To: <20090607153000.GM1927@deviant.kiev.zoral.com.ua> References: <20090606161600.GB61928@dchagin.static.corbina.ru> <20090606175033.GJ1927@deviant.kiev.zoral.com.ua> <49009886.20090607153452@dts.su> <20090607134038.GL1927@deviant.kiev.zoral.com.ua> <1186509222.20090607192146@dts.su> <20090607153000.GM1927@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Assp-Whitelisted: Yes X-Assp-Envelope-From: georg@dts.su X-Assp-Intended-For: freebsd-fs@freebsd.org X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host4.symbios.ru X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [26 6] / [26 6] X-AntiAbuse: Sender Address Domain - dts.su Subject: Re[2]: fatal trap 12 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: georg@dts.su List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jun 2009 19:24:18 -0000 Hello, Kostik Belousov. > On Sun, Jun 07, 2009 at 07:21:46PM +0400, georg@dts.su wrote: >> Hello, Kostik. >>=20 >> Have this after apply patch: >> cc1: warnings being treated as errors >> /usr/src/sys/fs/pseudofs/pseudofs_vnops.c: In function 'pfs_ioctl': >> /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265: warning: 'pn' is used uni= nitialized in this function >> /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:295: warning: 'pvd' is used un= initialized in this function >> *** Error code 1 > I already asked about the version of your source tree. Please answer. > I do not see how these warnings might happen on the RELENG_7, > and line numbers do not correspond to line numbers of RELENG_7 + patch. FreeBSD 7.2-STABLE amd64 RELENG_7 --=20 Regards, Yura mailto:georg@dts.su From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 00:56:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA98C1065672 for ; Mon, 8 Jun 2009 00:56:04 +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 741FD8FC15 for ; Mon, 8 Jun 2009 00:56:04 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MDT9f-00047z-42 for freebsd-fs@freebsd.org; Mon, 08 Jun 2009 00:56:03 +0000 Received: from 93-138-27-194.adsl.net.t-com.hr ([93.138.27.194]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Jun 2009 00:56:03 +0000 Received: from ivoras by 93-138-27-194.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 08 Jun 2009 00:56:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Mon, 08 Jun 2009 02:55:22 +0200 Lines: 61 Message-ID: References: <4A2AA48B.20803@free.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4E69E4FE3B573ADD3EAB6334" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 93-138-27-194.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <4A2AA48B.20803@free.de> X-Enigmail-Version: 0.95.7 Sender: news Subject: Re: ZFS v13 performance drops with low memory on FreeBSD-7 STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 00:56:05 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4E69E4FE3B573ADD3EAB6334 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Kai Gallasch wrote: > Hi. >=20 > I upgraded a server with 7-STABLE-amd64 and the MFC'd ZFS v13 about 8 > days ago. Since then the machine is running stable and this without > manually tuning vm.kmem_size, vfs.zfs.arc, etc. in loader.conf - so far= > so good :-) >=20 > In the last few days I noticed some performance issues with zfs, as som= e > customers complained about slow mysql database responses. >=20 > MySQL is running in a database jail on a zfs v13 zpool, websites using > the mysql database are also running on zfs on the same server. >=20 > The server is running about 30 in production jails, has 16GB RAM and 8G= B > swap. Swap usage is about only 1% currently. >=20 > After debugging the mysql settings for a while I found out, that when I= > stopped some processes on the server that were using high amounts of > RAM, the datbase response times for queries were almost back to normal > again.. >=20 > So for me this looks like when running applications and ZFS compete for= > free RAM, ZFS looses. Is that so? Yes, that was the point of recent work in stabilizing ZFS - without it you would probably panic. With it, ZFS's memory is shrunk down. Unless there are other factors (like swapping; are you swapping on ZFS?), this is the probable reason for what you're seeing. It's kind of bad when the file system competes this directly with applications :( --------------enig4E69E4FE3B573ADD3EAB6334 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.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkosYXsACgkQldnAQVacBcg9OACdEi0W0QMOvjtHmZoay/BCcITg YPcAoKs4+xEUNx7gZdTH82yXGHAoUJ/0 =IQah -----END PGP SIGNATURE----- --------------enig4E69E4FE3B573ADD3EAB6334-- From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 01:19:36 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A452106566C; Mon, 8 Jun 2009 01:19:36 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id 2682C8FC13; Mon, 8 Jun 2009 01:19:36 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by an-out-0708.google.com with SMTP id c3so1651005ana.13 for ; Sun, 07 Jun 2009 18:19:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=k6BlsK0B5wAtzXdQQvl0n4H8mReP+mtK8KTOdMvVV/k=; b=BkQNtZ+hDNzNnuoLhWmm9vhyZsTxG8SCLrPtC4vbKAcyy+Vu+0l2c1YTfCPpG4NDGw uurplDqdOKUMixlD+5qpRI7v+j1vLxuYl3vWN11wqHFTzxPmJWpNhzaNyNYjc6QniWgX R1PuGv81IS6TI7OptrMS/24qNbOldrypG4WXA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Z+1NnRL/IjCSL2ow/l+Snr5mxYyO1YgfwFaD6SSKJND/yieD7RhACaegOSEm15HaYq LJlHpg15bZvrd+sw2iK3XOs/dMRVWodaVL5sW1vLrY/znh6UpxIdzOhrQFeLqKT3oL1w EiKRD2N5iayyGHlvAXEJHyuSsULmjpX33LFAY= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.38.5 with SMTP id l5mr5460218anl.183.1244423975565; Sun, 07 Jun 2009 18:19:35 -0700 (PDT) In-Reply-To: References: <4A2AA48B.20803@free.de> Date: Sun, 7 Jun 2009 18:19:35 -0700 X-Google-Sender-Auth: d47ec66a5e33d1ac Message-ID: <3c1674c90906071819k589e93d5u27ff4652c77e09ff@mail.gmail.com> From: Kip Macy To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v13 performance drops with low memory on FreeBSD-7 STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 01:19:36 -0000 d of bad when the file system competes this directly with > applications :( > The backpressure will too aggressively shrink the ARC. I have a bunch of changes in my private branch that I will push back in to HEAD when I've managed to address all the current bottlenecks. -Kip From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 00:41:50 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ECB7106566B for ; Mon, 8 Jun 2009 00:41:50 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: from tutopia.com (mail08mass.ifxnetworks.com [190.60.24.78]) by mx1.freebsd.org (Postfix) with ESMTP id D77E38FC08 for ; Mon, 8 Jun 2009 00:41:49 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: (qmail 5790 invoked from network); 8 Jun 2009 00:15:07 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail08mass.ifxnetworks.com X-Spam-Level: X-Spam-Status: No, score=0.1 required=7.0 tests=MISSING_MID,RDNS_NONE autolearn=disabled version=3.2.5 Received: from unknown (HELO mail14.ifxnetworks.com) ([190.61.128.24]) (envelope-sender ) by mail08mass.ifxnetworks.com (qmail-ldap-1.03) with SMTP for ; 8 Jun 2009 00:15:07 -0000 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: To: freebsd-fs@FreeBSD.org X-Origin: 190.60.24.4 Date: Mon, 08 Jun 2009 00:15:07 +0000 X-Uidl: 1244420107222953898 X-Mailer: AtMail 4.11 Message-Id: <20090608004149.D77E38FC08@mx1.freebsd.org> X-Mailman-Approved-At: Mon, 08 Jun 2009 01:44:17 +0000 Cc: Subject: hpfs success report X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: giffunip@tutopia.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 00:41:50 -0000 Hello;=0D =0D Just FYI I thought I'd mention: I ran an experiment with Virtualbox and I h= ave =0D confirmed that, even though it's not built by default, the hpfs support is = still =0D working on FreeBSD-7.2-Release.=0D =0D It's basically read-only, mounting it rw causes trouble.=0D =0D cheers,=0D =0D Pedro.=0D =0D =0D From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 07:01:35 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E13010656C0 for ; Mon, 8 Jun 2009 07:01:35 +0000 (UTC) (envelope-from gallasch@free.de) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) by mx1.freebsd.org (Postfix) with ESMTP id 71B378FC16 for ; Mon, 8 Jun 2009 07:01:34 +0000 (UTC) (envelope-from gallasch@free.de) Received: (qmail 39442 invoked by uid 98); 8 Jun 2009 09:01:32 +0200 Received: from 91.204.4.103 by smtp.free.de (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.90.1/3618. Clear:RC:1(91.204.4.103):. Processed in 0.048655 secs); 08 Jun 2009 07:01:32 -0000 X-Qmail-Scanner-Mail-From: gallasch@free.de via smtp.free.de X-Qmail-Scanner: 1.25 (Clear:RC:1(91.204.4.103):. Processed in 0.048655 secs) Received: from smtp.free.de (HELO boiler.free.de) (gallasch@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 8 Jun 2009 09:01:32 +0200 Date: Mon, 8 Jun 2009 09:01:23 +0200 From: Kai Gallasch To: freebsd-fs@freebsd.org Message-ID: <20090608090123.13c21d5f@boiler.free.de> In-Reply-To: References: <4A2AA48B.20803@free.de> X-Mailer: Claws Mail 3.6.1 (GTK+ 2.16.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/qIJ7xaFaCLxoO1EqM_e7Cku"; protocol="application/pgp-signature" Subject: Re: ZFS v13 performance drops with low memory on FreeBSD-7 STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 07:01:35 -0000 --Sig_/qIJ7xaFaCLxoO1EqM_e7Cku Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 08 Jun 2009 02:55:22 +0200 wrote Ivan Voras : > Kai Gallasch wrote: > > Hi. > >=20 > > So for me this looks like when running applications and ZFS compete > > for free RAM, ZFS looses. Is that so? >=20 > Yes, that was the point of recent work in stabilizing ZFS - without it > you would probably panic. With it, ZFS's memory is shrunk down. Unless > there are other factors (like swapping; are you swapping on ZFS?), > this is the probable reason for what you're seeing. No. Swapspace is on a standard swap partition outside the zpool. # swapinfo=20 Device 1K-blocks Used Avail Capacity /dev/da0s3b 8388608 11636 8376972 0% There's barely swapping taking place on the server. --Kai. --Sig_/qIJ7xaFaCLxoO1EqM_e7Cku Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkost0MACgkQFvpAnxJUoYa3IgCeKsp1NmUrf4wuWNy/F6/NBLvh p0EAn0X6GL+i3Q7BgjAfYCn5R2tpQBP1 =Y3Fi -----END PGP SIGNATURE----- --Sig_/qIJ7xaFaCLxoO1EqM_e7Cku-- From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 07:46:40 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6F9C106564A for ; Mon, 8 Jun 2009 07:46:40 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id 702878FC16 for ; Mon, 8 Jun 2009 07:46:40 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by an-out-0708.google.com with SMTP id c3so1743936ana.13 for ; Mon, 08 Jun 2009 00:46:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=2HwtSS4BtBuXh6KK+yi8ifntJY78GyalQNwseS8aaaw=; b=PSLdslubxaGWILQ+fW/9CGYbpF1UMdEqscHPAPHdeM+a4EmQ5FQWq9603Ompwzvu3R 1GaHnu0Fk/Gw5R8qAKpUJZugOv3yBxbHNzV8se8uF6tTy02+yUnzt1zvoM1U8bNThYwf OFQHbnMFJC2dH94n5cYiKDwPYH77axB3kFwmc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Wn9EHnFAbxuF+51/yTTGIJA7nslG/iMg+o6h5pqV2QggWaMOIa7qhSU//Rg6lXjg93 hrmAinpXWm05RASnAbmYBbqzBaCDyvrLaWvKmblvfl2YatdxXREReh8Lrr4wBK0fPLjp OEz0kvz/UmcJpXWO24FDjjA5xF29flTN4hGmk= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.38.5 with SMTP id l5mr5672916anl.119.1244447192291; Mon, 08 Jun 2009 00:46:32 -0700 (PDT) In-Reply-To: <20090608090123.13c21d5f@boiler.free.de> References: <4A2AA48B.20803@free.de> <20090608090123.13c21d5f@boiler.free.de> Date: Mon, 8 Jun 2009 00:46:31 -0700 X-Google-Sender-Auth: 24de28c7b6faf439 Message-ID: <3c1674c90906080046q1bdcafci7dc1b30df7a4a169@mail.gmail.com> From: Kip Macy To: Kai Gallasch Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v13 performance drops with low memory on FreeBSD-7 STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 07:46:41 -0000 The inactive queue can cause the ARC to be shrunk down to almost nothing. This is in need of fixing. Cheers, Kip On Mon, Jun 8, 2009 at 12:01 AM, Kai Gallasch wrote: > On Mon, 08 Jun 2009 02:55:22 +0200 > wrote Ivan Voras : > >> Kai Gallasch wrote: >> > Hi. >> > >> > So for me this looks like when running applications and ZFS compete >> > for free RAM, ZFS looses. Is that so? >> >> Yes, that was the point of recent work in stabilizing ZFS - without it >> you would probably panic. With it, ZFS's memory is shrunk down. Unless >> there are other factors (like swapping; are you swapping on ZFS?), >> this is the probable reason for what you're seeing. > > No. Swapspace is on a standard swap partition outside the zpool. > # swapinfo > Device =A0 =A0 =A0 =A0 =A01K-blocks =A0 =A0 Used =A0 =A0Avail Capacity > /dev/da0s3b =A0 =A0 =A0 8388608 =A0 =A011636 =A08376972 =A0 =A0 0% > > There's barely swapping taking place on the server. > > --Kai. > > > --=20 When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 11:06:52 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B16B1065673 for ; Mon, 8 Jun 2009 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 483B58FC08 for ; Mon, 8 Jun 2009 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n58B6qnj020620 for ; Mon, 8 Jun 2009 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n58B6ptK020616 for freebsd-fs@FreeBSD.org; Mon, 8 Jun 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Jun 2009 11:06:51 GMT Message-Id: <200906081106.n58B6ptK020616@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 11:06:52 -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 bin/135314 fs [zfs] assertion failed for zdb(8) usage o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/135039 fs [zfs] mkstemp() fails over NFS when server uses ZFS (7 f kern/134496 fs [zfs] [panic] ZFS pool export occasionally causes a ke o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133980 fs [panic] [ffs] panic: ffs_valloc: dup alloc o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [smbfs] [panic] panic: ffs_truncate: read-only filesys o kern/133373 fs [zfs] umass attachment causes ZFS checksum errors, dat o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/133134 fs [zfs] Missing ZFS zpool labels f kern/133020 fs [zfs] [panic] inappropriate panic caused by zfs. Pani o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132597 fs [tmpfs] [panic] tmpfs-related panic while interrupting o kern/132551 fs [zfs] ZFS locks up on extattr_list_link syscall o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132337 fs [zfs] [panic] kernel panic in zfs_fuid_create_cred 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 f kern/132068 fs [zfs] page fault when using ZFS over NFS on 7.1-RELEAS o kern/131995 fs [nfs] Failure to mount NFSv4 server 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/131086 fs [ext2fs] [patch] mkfs.ext2 creates rotten partition o kern/130979 fs [smbfs] [panic] boot/kernel/smbfs.ko o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv 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/129148 fs [zfs] [panic] panic on concurrent writing & rollback o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad f kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127659 fs [tmpfs] tmpfs memory leak o kern/127492 fs [zfs] System hang on ZFS input-output o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/125644 fs [zfs] [panic] zfs unfixable fs errors caused panic whe f kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs] [panic] changing into .zfs dir from nfs client c f kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o kern/122173 fs [zfs] [panic] Kernel Panic if attempting to replace a o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o kern/122047 fs [ext2fs] [patch] incorrect handling of UF_IMMUTABLE / o kern/122038 fs [tmpfs] [panic] tmpfs: panic: tmpfs_alloc_vp: type 0xc o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o kern/121770 fs [zfs] ZFS on i386, large file or heavy I/O leads to ke o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o bin/120288 fs zfs(8): "zfs share -a" does not send SIGHUP to mountd f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B o kern/118912 fs [2tb] disk sizing/geometry problem with large array o misc/118855 fs [zfs] ZFS-related commands are nonfunctional in fixit o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118320 fs [zfs] [patch] NFS SETATTR sometimes fails to set file o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o kern/116913 fs [ffs] [panic] ffs_blkfree: freeing free block p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/115645 fs [snapshots] [panic] lockmgr: thread 0xc4c00d80, not ex 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 kern/113180 fs [zfs] Setting ZFS nfsshare property does not cause inh o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/105093 fs [ext2fs] [patch] ext2fs on read-only media cannot be m o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist f 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 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [iso9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic 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 f kern/91568 fs [ufs] [panic] writing to UFS/softupdates DVD media in o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/89991 fs [ufs] softupdates with mount -ur causes fs UNREFS o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi 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 kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/77826 fs [ext2fs] ext2fs usb filesystem will not mount RW 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 kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 139 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 19:31:17 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F945106564A for ; Mon, 8 Jun 2009 19:31:17 +0000 (UTC) (envelope-from mlstarling31@hotmail.com) Received: from col0-omc4-s13.col0.hotmail.com (col0-omc4-s13.col0.hotmail.com [65.55.34.215]) by mx1.freebsd.org (Postfix) with ESMTP id 1E80F8FC1C for ; Mon, 8 Jun 2009 19:31:17 +0000 (UTC) (envelope-from mlstarling31@hotmail.com) Received: from COL104-W55 ([65.55.34.199]) by col0-omc4-s13.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Jun 2009 12:18:33 -0700 Message-ID: X-Originating-IP: [69.182.171.61] From: Michael Starling To: Date: Mon, 8 Jun 2009 15:18:33 -0400 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 08 Jun 2009 19:18:33.0122 (UTC) FILETIME=[E9F86820:01C9E86D] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Mounting ext3 under Freebsd X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 19:31:17 -0000 Hello...This problem is driving me crazy as I thought it was fixed with the= release of 7.2. I can mount the ext3 filesystem from a previous linux driv= e but I can't access the data. it was my understanding that a patch has been = incorporated into the 7.2 release ..Any ides as to why I might still be see= ing this issue?.Thanks uname -a=20 FreeBSD BSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 200= 9 OK..So here's what's happening after shutting down the linux box and placin= g the disk inside the BSD box. tune2fs -l /dev/ad6s1 tune2fs 1.41.4 (27-Jan-2009) Filesystem volume name: Last mounted on: Filesystem UUID: fbb12204-b8fc-4f29-aab8-d2d9dd1ccbce Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filet= ype sparse_super large_file Filesystem flags: signed_directory_hash=20 Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 15269888 Block count: 61049000 Reserved block count: 3052450 Free blocks: 36030598 Free inodes: 15269372 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1009 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Fri May 29 10:44:59 2009 Last mount time: Mon Jun 8 09:57:59 2009 Last write time: Mon Jun 8 13:33:00 2009 Mount count: 5 Maximum mount count: 21 Last checked: Fri May 29 10:44:59 2009 Check interval: 15552000 (6 months) Next check after: Wed Nov 25 09:44:59 2009 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group wheel) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 0904fd61-260b-467c-ae33-ba484e5d9f64 Journal backup: inode blocks Now it says the filesystem is clean so I mount it with. mount -t ext2fs /dev/ad6s1 /mnt ls /mnt ls: /mnt: Bad file descriptor OK so we look at tune2fs again and the filesystem is "not clean" now.=20 tune2fs -l /dev/ad6s1 tune2fs 1.41.4 (27-Jan-2009) Filesystem volume name: Last mounted on: Filesystem UUID: fbb12204-b8fc-4f29-aab8-d2d9dd1ccbce Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filet= ype sparse_super large_file Filesystem flags: signed_directory_hash=20 Default mount options: (none) Filesystem state: not clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 15269888 Block count: 61049000 Reserved block count: 3052450 Free blocks: 36030598 Free inodes: 15269372 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1009 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Fri May 29 10:44:59 2009 Last mount time: Mon Jun 8 09:57:59 2009 Last write time: Mon Jun 8 13:37:47 2009 Mount count: 5 Maximum mount count: 21 Last checked: Fri May 29 10:44:59 2009 Check interval: 15552000 (6 months) Next check after: Wed Nov 25 09:44:59 2009 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group wheel) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 0904fd61-260b-467c-ae33-ba484e5d9f64 Journal backup: inode blocks So I umount the filesystem and run e2fsck with. e2fsck /dev/ad6s1 e2fsck 1.41.4 (27-Jan-2009) /dev/ad6s1: clean=2C 516/15269888 files=2C 25018402/61049000 blocks The filesystem now reports as "clean" again....So this is just a vicious cycle which I can't break..aaaaaaaaaaahhhhhhhhhhhhhhhhhhh....Please help...Losing sanity.. _________________________________________________________________ Hotmail=AE has ever-growing storage! Don=92t worry about storage limits.=20 http://windowslive.com/Tutorial/Hotmail/Storage?ocid=3DTXT_TAGLM_WL_HM_Tuto= rial_Storage_062009= From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 20:27:55 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F166106566B for ; Mon, 8 Jun 2009 20:27:55 +0000 (UTC) (envelope-from scjamorim@bsd.com.br) Received: from mail-ew0-f212.google.com (mail-ew0-f212.google.com [209.85.219.212]) by mx1.freebsd.org (Postfix) with ESMTP id 72D8B8FC12 for ; Mon, 8 Jun 2009 20:27:54 +0000 (UTC) (envelope-from scjamorim@bsd.com.br) Received: by ewy8 with SMTP id 8so4401309ewy.43 for ; Mon, 08 Jun 2009 13:27:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.210.86.1 with SMTP id j1mr6937008ebb.29.1244491156414; Mon, 08 Jun 2009 12:59:16 -0700 (PDT) In-Reply-To: References: Date: Mon, 8 Jun 2009 16:59:16 -0300 Message-ID: <5859850b0906081259m2ba43694n9aa952641563c618@mail.gmail.com> From: =?ISO-8859-1?Q?Sylvio_C=E9sar_Teixeira_Amorim?= To: Michael Starling Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ext3 under Freebsd X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 20:27:55 -0000 Linux: # tune2fs -s off /dev/sda1 # e2fsck -y /dev/sda1 FreeBSD: # cd /usr/ports/sysutils/e2fsprogs # make install all # mount -t ext2fs /dev/ad4s1 /media/linux Att Sylvio Cesar 2009/6/8 Michael Starling > > Hello...This problem is driving me crazy as I thought it was fixed with t= he > release of 7.2. I can mount the ext3 filesystem from a previous linux dri= ve > but I can't access the data. it was my understanding that a patch has bee= n > incorporated into the 7.2 release ..Any ides as to why I might still be > seeing this issue?.Thanks > > > > uname -a > FreeBSD BSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC > 2009 > > OK..So here's what's happening after shutting down the linux box and > placing the disk inside the BSD box. > > > > tune2fs -l /dev/ad6s1 > > tune2fs 1.41.4 (27-Jan-2009) > > Filesystem volume name: > > Last mounted on: > > Filesystem UUID: fbb12204-b8fc-4f29-aab8-d2d9dd1ccbce > > Filesystem magic number: 0xEF53 > > Filesystem revision #: 1 (dynamic) > > Filesystem features: has_journal ext_attr resize_inode dir_index > filetype sparse_super large_file > > Filesystem flags: signed_directory_hash > > Default mount options: (none) > > Filesystem state: clean > > Errors behavior: Continue > > Filesystem OS type: Linux > > Inode count: 15269888 > > Block count: 61049000 > > Reserved block count: 3052450 > > Free blocks: 36030598 > > Free inodes: 15269372 > > First block: 0 > > Block size: 4096 > > Fragment size: 4096 > > Reserved GDT blocks: 1009 > > Blocks per group: 32768 > > Fragments per group: 32768 > > Inodes per group: 8192 > > Inode blocks per group: 512 > > Filesystem created: Fri May 29 10:44:59 2009 > > Last mount time: Mon Jun 8 09:57:59 2009 > > Last write time: Mon Jun 8 13:33:00 2009 > > Mount count: 5 > > Maximum mount count: 21 > > Last checked: Fri May 29 10:44:59 2009 > > Check interval: 15552000 (6 months) > > Next check after: Wed Nov 25 09:44:59 2009 > > Reserved blocks uid: 0 (user root) > > Reserved blocks gid: 0 (group wheel) > > First inode: 11 > > Inode size: 256 > > Required extra isize: 28 > > Desired extra isize: 28 > > Journal inode: 8 > > Default directory hash: half_md4 > > Directory Hash Seed: 0904fd61-260b-467c-ae33-ba484e5d9f64 > > Journal backup: inode blocks > > > > > > Now it says the filesystem is clean so I mount it with. > > > > mount -t ext2fs /dev/ad6s1 /mnt > > > > ls /mnt > > > > ls: /mnt: Bad file descriptor > > > > > > OK so we look at tune2fs again and the filesystem is "not clean" now. > > > > tune2fs -l /dev/ad6s1 > > tune2fs 1.41.4 (27-Jan-2009) > > Filesystem volume name: > > Last mounted on: > > Filesystem UUID: fbb12204-b8fc-4f29-aab8-d2d9dd1ccbce > > Filesystem magic number: 0xEF53 > > Filesystem revision #: 1 (dynamic) > > Filesystem features: has_journal ext_attr resize_inode dir_index > filetype sparse_super large_file > > Filesystem flags: signed_directory_hash > > Default mount options: (none) > > Filesystem state: not clean > > Errors behavior: Continue > > Filesystem OS type: Linux > > Inode count: 15269888 > > Block count: 61049000 > > Reserved block count: 3052450 > > Free blocks: 36030598 > > Free inodes: 15269372 > > First block: 0 > > Block size: 4096 > > Fragment size: 4096 > > Reserved GDT blocks: 1009 > > Blocks per group: 32768 > > Fragments per group: 32768 > > Inodes per group: 8192 > > Inode blocks per group: 512 > > Filesystem created: Fri May 29 10:44:59 2009 > > Last mount time: Mon Jun 8 09:57:59 2009 > > Last write time: Mon Jun 8 13:37:47 2009 > > Mount count: 5 > > Maximum mount count: 21 > > Last checked: Fri May 29 10:44:59 2009 > > Check interval: 15552000 (6 months) > > Next check after: Wed Nov 25 09:44:59 2009 > > Reserved blocks uid: 0 (user root) > > Reserved blocks gid: 0 (group wheel) > > First inode: 11 > > Inode size: 256 > > Required extra isize: 28 > > Desired extra isize: 28 > > Journal inode: 8 > > Default directory hash: half_md4 > > Directory Hash Seed: 0904fd61-260b-467c-ae33-ba484e5d9f64 > > Journal backup: inode blocks > > > > So I umount the filesystem and run e2fsck with. > > > > e2fsck /dev/ad6s1 > > e2fsck 1.41.4 (27-Jan-2009) > > /dev/ad6s1: clean, 516/15269888 files, 25018402/61049000 blocks > > > > The filesystem now reports as "clean" again....So this is just a > vicious cycle which I can't > break..aaaaaaaaaaahhhhhhhhhhhhhhhhhhh....Please help...Losing sanity.. > > _________________________________________________________________ > Hotmail=AE has ever-growing storage! Don=92t worry about storage limits. > > http://windowslive.com/Tutorial/Hotmail/Storage?ocid=3DTXT_TAGLM_WL_HM_Tu= torial_Storage_062009_______________________________________________ > freebsd-fs@freebsd.orgmailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 -=3D-=3D-=3D-=3D-=3D-=3D-=3D- Live free or die - UNIX* -=3D-=3D-=3D-=3D-=3D= -=3D-=3D From owner-freebsd-fs@FreeBSD.ORG Tue Jun 9 15:35:08 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF6AE1065670 for ; Tue, 9 Jun 2009 15:35:08 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235]) by mx1.freebsd.org (Postfix) with ESMTP id AEA268FC14 for ; Tue, 9 Jun 2009 15:35:08 +0000 (UTC) (envelope-from sarawgi.aditya@gmail.com) Received: by rv-out-0506.google.com with SMTP id l9so2038125rvb.3 for ; Tue, 09 Jun 2009 08:35:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=ajSA9QiD36FeAt7TB9gdgj0FKTKHKAq3R5dvqe0yv50=; b=IV9aYSsvWg0/6882JA80f/AR6XMdL5DYL3LvIMs5TOZ1KckNZzB0x7fKoky39bcKwW zrNj4KMH0EX1YRAuquTEdhU1dSh7v5NNi5/eKgWdWFegluq3rKBqe931UhyP5uFi65EQ bY3K7G4sowiB8f7W8auiOUinhDDzuVa6VNbdY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=vOJazcpVfBjknR0TSFeBVzndbcSErkl+MwLWKy+rosCFcdB/2AsnxkgbBv41aOJpDp KFLOZQo9hAKnlW9GoAcCVtWUdZ23eD3ao0OC4HcOB1C7rnfJLkzckC7WP68Vhvv1br1X dzEEUDhOm0eNut3l9EStIGTTQhqowudOojt5w= Received: by 10.141.122.1 with SMTP id z1mr203892rvm.210.1244561707413; Tue, 09 Jun 2009 08:35:07 -0700 (PDT) Received: from aditya ([121.241.40.106]) by mx.google.com with ESMTPS id b39sm20031109rvf.3.2009.06.09.08.34.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 09 Jun 2009 08:35:01 -0700 (PDT) Date: Tue, 9 Jun 2009 15:34:48 +0530 From: Aditya Sarawgi To: Michael Starling Message-ID: <20090609100446.GA1095@aditya> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ext3 under Freebsd X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2009 15:35:09 -0000 On Mon, Jun 08, 2009 at 03:18:33PM -0400, Michael Starling wrote: > > Hello...This problem is driving me crazy as I thought it was fixed with the release of 7.2. I can mount the ext3 filesystem from a previous linux drive > but I can't access the data. it was my understanding that a patch has been incorporated into the 7.2 release ..Any ides as to why I might still be seeing this issue?.Thanks > > > > uname -a > FreeBSD BSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 > > OK..So here's what's happening after shutting down the linux box and placing the disk inside the BSD box. > > > > tune2fs -l /dev/ad6s1 > > tune2fs 1.41.4 (27-Jan-2009) > > Filesystem volume name: > > Last mounted on: > > Filesystem UUID: fbb12204-b8fc-4f29-aab8-d2d9dd1ccbce > > Filesystem magic number: 0xEF53 > > Filesystem revision #: 1 (dynamic) > > Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file > > Filesystem flags: signed_directory_hash > > Default mount options: (none) > > Filesystem state: clean > > Errors behavior: Continue > > Filesystem OS type: Linux > > Inode count: 15269888 > > Block count: 61049000 > > Reserved block count: 3052450 > > Free blocks: 36030598 > > Free inodes: 15269372 > > First block: 0 > > Block size: 4096 > > Fragment size: 4096 > > Reserved GDT blocks: 1009 > > Blocks per group: 32768 > > Fragments per group: 32768 > > Inodes per group: 8192 > > Inode blocks per group: 512 > > Filesystem created: Fri May 29 10:44:59 2009 > > Last mount time: Mon Jun 8 09:57:59 2009 > > Last write time: Mon Jun 8 13:33:00 2009 > > Mount count: 5 > > Maximum mount count: 21 > > Last checked: Fri May 29 10:44:59 2009 > > Check interval: 15552000 (6 months) > > Next check after: Wed Nov 25 09:44:59 2009 > > Reserved blocks uid: 0 (user root) > > Reserved blocks gid: 0 (group wheel) > > First inode: 11 > > Inode size: 256 The 7.2 Release doesn't support inode size other than 128 but this problem is fixed in 8.0. If you want support for inode size other than 128 in 7.2 you can use the following patch http://pflog.net/~floyd/ext2fs.diff. Cheers, Aditya Sarawgi From owner-freebsd-fs@FreeBSD.ORG Wed Jun 10 01:22:42 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F5AA106566C for ; Wed, 10 Jun 2009 01:22:42 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.245]) by mx1.freebsd.org (Postfix) with ESMTP id 553698FC1C for ; Wed, 10 Jun 2009 01:22:41 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by an-out-0708.google.com with SMTP id c3so214658ana.13 for ; Tue, 09 Jun 2009 18:22:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=qllLNVpZX4AXQNw3rRxecRPZL3k0jqyNbTaJ4w0kWAs=; b=LKzYW+V9AMQhRT4AAKP8N4QOepovF41tIUs+V5vOe1S3au0mhhPLfm2a+cY64XV8GQ lM9dWt7PVyRGmYXuX0rAb1DXinwaK1vIeXqT9R2iKvpsU3Jkq4Jd1c0Uqot+hb/HR8Uf 76jVg011HdMxXfpk5hGJXD8IPcvFizALvxW/c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=d3R6AmFUwIXlhjXqy+0FE9WBGoJI54VBRa7UlZLbEVwzWzoIQnkSYpppbqhdKGjvDn 6W54StoYjuLF95w7kpym65LkkKrwVKrDQ4nhnF3fcwUaat48w252DqOgwjIQfN8M/04N pTNlHkiZfvSIZb5lYoV+T9WgnfiYxQCmbXzpY= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.153.12 with SMTP id a12mr745356ane.159.1244596960976; Tue, 09 Jun 2009 18:22:40 -0700 (PDT) Date: Tue, 9 Jun 2009 18:22:40 -0700 X-Google-Sender-Auth: 5af4fae6fb9fc513 Message-ID: <3c1674c90906091822x56be5f2bg5b6156618847cc21@mail.gmail.com> From: Kip Macy To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: heads up on prefetch tunable in 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: Wed, 10 Jun 2009 01:22:42 -0000 As far as I can tell systems that have less than 4GB are more often hurt by prefetched than helped. On i386 systems and systems with less than 4GB, as of 193878 prefetch is now disabled by default. I've added a prefetch enable tunable, to enable prefetching for those systems. The prefetch disable tunable will continue to unconditionally disable prefetching. Cheers, Kip From owner-freebsd-fs@FreeBSD.ORG Wed Jun 10 05:16:10 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94C67106564A; Wed, 10 Jun 2009 05:16:10 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 69DB18FC16; Wed, 10 Jun 2009 05:16:10 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5A5GAaV036071; Wed, 10 Jun 2009 05:16:10 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5A5GAJM036067; Wed, 10 Jun 2009 05:16:10 GMT (envelope-from linimon) Date: Wed, 10 Jun 2009 05:16:10 GMT Message-Id: <200906100516.n5A5GAJM036067@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/135412: [zfs] [nfs] zfs(v13)+nfs and open(..., O_WRONLY|O_CREAT|O_EXCL, ...) returns io error 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, 10 Jun 2009 05:16:11 -0000 Old Synopsis: zfs(v13)+nfs and open(..., O_WRONLY|O_CREAT|O_EXCL, ...) returns io error New Synopsis: [zfs] [nfs] zfs(v13)+nfs and open(..., O_WRONLY|O_CREAT|O_EXCL, ...) returns io error Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jun 10 05:15:55 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=135412 From owner-freebsd-fs@FreeBSD.ORG Wed Jun 10 11:48:34 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F37D91065722 for ; Wed, 10 Jun 2009 11:48:33 +0000 (UTC) (envelope-from fbsd@microhost.su) Received: from microhost.su (microhost.su [77.246.106.26]) by mx1.freebsd.org (Postfix) with ESMTP id AAE408FC12 for ; Wed, 10 Jun 2009 11:48:33 +0000 (UTC) (envelope-from fbsd@microhost.su) Received: by microhost.su (Postfix, from userid 125) id 930E62826F; Wed, 10 Jun 2009 15:51:10 +0700 (NOVST) Received: by microhost.su (Postfix, from userid 125) id 2560C2826B; Wed, 10 Jun 2009 15:39:52 +0700 (NOVST) Received: by microhost.su (Postfix, from userid 80) id E597C28267; Wed, 10 Jun 2009 15:34:45 +0700 (NOVST) To: MIME-Version: 1.0 Date: Wed, 10 Jun 2009 15:34:45 +0700 From: Message-ID: X-Sender: fbsd@microhost.su User-Agent: RoundCube Webmail/0.2.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Subject: trouble adding hard disk 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, 10 Jun 2009 11:48:36 -0000 Hello everybody! I have a trouble to add 500G new disk. uname: FreeBSD 7.2-RELEASE #0 harddisk connected via SATA controller ====== atapci0: port 0xb000-0xb00f,0xb400-0xb40f,0xb800-0xb80f,0xbc00-0xbc0f,0xc000-0xc01f,0xc400-0xc4ff irq 18 at device 0.0 on pci1 ====== dmesg | grep ad ===== ad0: 76319MB at ata0-master UDMA100 ad4: 476940MB at ata2-master SATA150 ===== I use sysinstall to setup slice using fdisk and bsdlabel to create partition. When I choose to write changes in bsdlabel i got error mounting: no such file or directory. before use sysinstall i create directory. mkdir /newdisk after sysinstall i got: ======= ls | grep ad4 ad4 ad4s1 ======= But when i doing "newfs -O2 /dev/ad4s1" i got an error: ===== skipped. 976633600 internal error: can't find block in cyl 0 ===== What i'm doing wrong? Tnanks for all answers :) Sorry about my english :) From owner-freebsd-fs@FreeBSD.ORG Wed Jun 10 11:48:36 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04ABF1065724 for ; Wed, 10 Jun 2009 11:48:34 +0000 (UTC) (envelope-from fbsd@microhost.su) Received: from microhost.su (microhost.su [77.246.106.26]) by mx1.freebsd.org (Postfix) with ESMTP id AE83C8FC13 for ; Wed, 10 Jun 2009 11:48:33 +0000 (UTC) (envelope-from fbsd@microhost.su) Received: by microhost.su (Postfix, from userid 125) id 8F3FC2826E; Wed, 10 Jun 2009 15:51:10 +0700 (NOVST) Received: by microhost.su (Postfix, from userid 125) id 2192C2824F; Wed, 10 Jun 2009 15:37:44 +0700 (NOVST) Received: by microhost (Postfix, from userid 80) id 6219D28263; Wed, 10 Jun 2009 15:32:42 +0700 (NOVST) To: MIME-Version: 1.0 Date: Wed, 10 Jun 2009 15:32:42 +0700 From: Message-ID: X-Sender: fbsd@microhost.su User-Agent: RoundCube Webmail/0.2.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Subject: trouble adding hard disk 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, 10 Jun 2009 11:48:37 -0000 Hello everybody! I have a trouble to add 500G new disk. uname: FreeBSD 7.2-RELEASE #0 harddisk connected via SATA controller ====== atapci0: port 0xb000-0xb00f,0xb400-0xb40f,0xb800-0xb80f,0xbc00-0xbc0f,0xc000-0xc01f,0xc400-0xc4ff irq 18 at device 0.0 on pci1 ====== dmesg | grep ad ===== ad0: 76319MB at ata0-master UDMA100 ad4: 476940MB at ata2-master SATA150 ===== I use sysinstall to setup slice using fdisk and bsdlabel to create partition. When I choose to write changes in bsdlabel i got error mounting: no such file or directory. before use sysinstall i create directory. mkdir /newdisk after sysinstall i got: ======= ls | grep ad4 ad4 ad4s1 ======= But when i doing "newfs -O2 /dev/ad4s1" i got an error: ===== skipped. 976633600 internal error: can't find block in cyl 0 ===== What i'm doing wrong? Tnanks for all answers :) Sorry about my english :) From owner-freebsd-fs@FreeBSD.ORG Wed Jun 10 21:37:16 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EBF4106566C for ; Wed, 10 Jun 2009 21:37:16 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id 4FD068FC15 for ; Wed, 10 Jun 2009 21:37:11 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by an-out-0708.google.com with SMTP id c3so575244ana.13 for ; Wed, 10 Jun 2009 14:37:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=B6PZHtS+gjWdGBS2xaQqtBRmy8ufFRM0kldc4uXfGqo=; b=kTBzzfPUhExS8uzzAOGk4OZerSaYR67+BcC6Yl9xyM9ep/Ijj5ewOtdOobwPTy8CEq pbSwwjHlbufBUaaz5d/KyQ1ZhjB35QDvHd3DUb8VvMrOukPjeFOgYjMBE2buLhTU7/vo 1ADDTH7iAm/7oyD7Niw9ETPOQ05XTnGSMw9qM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=ZNyOFpv/+xdYXQVl/g18Dqoytq48+UjOk3R55bNbmBvzAMeXeQ+m3QuTXLCLpvFT/A oePA1oZ/qv6XEvoRdeLUhk7Z5o2xp7d4+5MT2c+aGgQrGD8dZtNJIMlKrj/nm0oY06IT zw9EafMQg/GYXlW63cOlUk1rESO/w5qU5VD5k= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.14.2 with SMTP id 2mr1962531ann.68.1244669830644; Wed, 10 Jun 2009 14:37:10 -0700 (PDT) Date: Wed, 10 Jun 2009 14:37:10 -0700 X-Google-Sender-Auth: cb286e17a03f754e Message-ID: <3c1674c90906101437t5ff9fa72kcad59ff4afe4d1e3@mail.gmail.com> From: Kip Macy To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: prefetch change in 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: Wed, 10 Jun 2009 21:37:16 -0000 Prefetch is still enabled by default on non-i386 systems with more than 4GB. To unconditionally enable or disable, set "vfs.zfs.prefetch_enable" in loader.conf. Cheers, Kip From owner-freebsd-fs@FreeBSD.ORG Wed Jun 10 22:22:26 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 413461065674 for ; Wed, 10 Jun 2009 22:22:26 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: from smtp123.rog.mail.re2.yahoo.com (smtp123.rog.mail.re2.yahoo.com [206.190.53.28]) by mx1.freebsd.org (Postfix) with SMTP id C3C2B8FC13 for ; Wed, 10 Jun 2009 22:22:25 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: (qmail 47185 invoked from network); 10 Jun 2009 21:55:44 -0000 Received: from unknown (HELO wawanesa.iciti.ca) (gtodd@99.246.61.82 with login) by smtp123.rog.mail.re2.yahoo.com with SMTP; 10 Jun 2009 21:55:44 -0000 X-YMail-OSG: QUO_aX8VM1k10VSBCvuVS3R8RUbk7YahpOIG12sAl.jL1it8VxVlO56FbA5aewtz4w-- X-Yahoo-Newman-Property: ymail-3 Received: from wawanesa.iciti.ca (wawanesa.iciti.ca [192.168.2.4]) by wawanesa.iciti.ca (Postfix) with ESMTP id EE7806F; Wed, 10 Jun 2009 17:56:42 -0400 (EDT) Message-ID: <4A302C1A.4030803@bellanet.org> Date: Wed, 10 Jun 2009 17:56:42 -0400 From: Graham Todd User-Agent: Thunderbird 2.0.0.21 (X11/20090511) MIME-Version: 1.0 To: Kip Macy , freebsd-fs@freebsd.org References: <3c1674c90906101437t5ff9fa72kcad59ff4afe4d1e3@mail.gmail.com> In-Reply-To: <3c1674c90906101437t5ff9fa72kcad59ff4afe4d1e3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: prefetch change in 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: Wed, 10 Jun 2009 22:22:26 -0000 Kip Macy wrote: > Prefetch is still enabled by default on non-i386 systems with more > than 4GB. To unconditionally enable or disable, set > "vfs.zfs.prefetch_enable" in loader.conf. So is this a change of OID as well (i.e. to "vfs.zfs.prefetch_enable")? Here prefetch is enabled by default on a 2GB RAM 7.2-RELEASE system (ZFS version 6) by setting *vfs.zfs.prefetch_disable* to 0. ninga# sysctl vfs.zfs | grep fetch vfs.zfs.prefetch_disable: 0 cheers, From owner-freebsd-fs@FreeBSD.ORG Wed Jun 10 22:42:34 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94109106566C for ; Wed, 10 Jun 2009 22:42:34 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from mail-yx0-f200.google.com (mail-yx0-f200.google.com [209.85.210.200]) by mx1.freebsd.org (Postfix) with ESMTP id 511A48FC15 for ; Wed, 10 Jun 2009 22:42:34 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by yxe38 with SMTP id 38so282182yxe.3 for ; Wed, 10 Jun 2009 15:42:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=owcsug+PuIaYls5JD1uwDrOqr6udSjw6cQJEfkhGJ5Y=; b=oRCjJzxbwzx4flTXcAj9Q1ZbfD6Ud5Kv2M9A9aCVEK0+dSuGsTzKw1S/irQgQ6+7KF +gRZBifED+vB3/OgpEjcYnvk5ZPcnNPNontMZ4ovxoVwanwMdzqbsWtg8kqbjRWNZvli ClfO+9gB/2ifKocf6TH6x4Dpm5m31NfGbyW0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=OcavAKcccjwsZ1ysCIh9dZo+eNg8rnlI0cYshVrgAFXZ5v6MJWGhdsjwZF2RAuFjNR o8FiAsRZ2SpySHu2I4r6fcNvjiUTn4iXk1E+0zZEYrrVFzSWSCn8U8BnoZlRQbWtZBHa U6Ld5cfPHS8dWBXtkmcF2S1prxffh0M+3BRXM= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.108.8 with SMTP id g8mr2048988anc.66.1244673753515; Wed, 10 Jun 2009 15:42:33 -0700 (PDT) In-Reply-To: <4A302C1A.4030803@bellanet.org> References: <3c1674c90906101437t5ff9fa72kcad59ff4afe4d1e3@mail.gmail.com> <4A302C1A.4030803@bellanet.org> Date: Wed, 10 Jun 2009 15:42:33 -0700 X-Google-Sender-Auth: 7f61c324c8c4140c Message-ID: <3c1674c90906101542m13c93aedx89c6b03eb188c033@mail.gmail.com> From: Kip Macy To: Graham Todd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: prefetch change in 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: Wed, 10 Jun 2009 22:42:34 -0000 This is on HEAD until MFC. -Kip On Wed, Jun 10, 2009 at 2:56 PM, Graham Todd wrote: > Kip Macy wrote: >> Prefetch is still enabled by default on non-i386 systems with more >> than 4GB. To unconditionally enable or disable, set >> "vfs.zfs.prefetch_enable" in loader.conf. > > So is this a change of OID as well (i.e. to "vfs.zfs.prefetch_enable")? > > Here prefetch is enabled by default on a 2GB RAM 7.2-RELEASE system (ZFS > version 6) by setting *vfs.zfs.prefetch_disable* to 0. > > ninga# sysctl vfs.zfs | grep fetch > vfs.zfs.prefetch_disable: 0 > > cheers, > -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke From owner-freebsd-fs@FreeBSD.ORG Thu Jun 11 20:30:04 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1648A10656C0; Thu, 11 Jun 2009 20:30:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E1C0D8FC2C; Thu, 11 Jun 2009 20:30:03 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5BKU3Bd022363; Thu, 11 Jun 2009 20:30:03 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5BKU3Rj022351; Thu, 11 Jun 2009 20:30:03 GMT (envelope-from linimon) Date: Thu, 11 Jun 2009 20:30:03 GMT Message-Id: <200906112030.n5BKU3Rj022351@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/135480: [zfs] panic: lock &arg.lock already initialized X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2009 20:30:05 -0000 Old Synopsis: (zfs) panic: lock &arg.lock already initialized New Synopsis: [zfs] panic: lock &arg.lock already initialized Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jun 11 20:29:44 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=135480 From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 05:39:29 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E5FB106568F; Fri, 12 Jun 2009 05:39:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 333FF8FC1B; Fri, 12 Jun 2009 05:39:29 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5C5dTL8052784; Fri, 12 Jun 2009 05:39:29 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5C5dTjd052780; Fri, 12 Jun 2009 05:39:29 GMT (envelope-from linimon) Date: Fri, 12 Jun 2009 05:39:29 GMT Message-Id: <200906120539.n5C5dTjd052780@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/135469: [ufs] [panic] kernel crash on md operation in ufs_dirbad X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 05:39:30 -0000 Old Synopsis: kernel crash on md operation in ufs_dirbad New Synopsis: [ufs] [panic] kernel crash on md operation in ufs_dirbad Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jun 12 05:39:12 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=135469 From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 06:09:07 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42E5210656C9 for ; Fri, 12 Jun 2009 06:09:07 +0000 (UTC) (envelope-from ilgiz@reid.ru) Received: from www.reid.ru (reid.ufanet.ru [81.30.200.238]) by mx1.freebsd.org (Postfix) with ESMTP id EA4BD8FC08 for ; Fri, 12 Jun 2009 06:09:06 +0000 (UTC) (envelope-from ilgiz@reid.ru) Received: from localhost (localhost [127.0.0.1]) by www.reid.ru (Postfix) with SMTP id 4AA972CEFDB for ; Fri, 12 Jun 2009 11:55:47 +0600 (YEKST) X-AV-Checked: Fri Jun 12 11:55:47 2009 DRWEB_CHECKED Received: from reid.ru (localhost [127.0.0.1]) by www.reid.ru (Postfix) with ESMTP id 2B61F2CEFD8 for ; Fri, 12 Jun 2009 11:55:47 +0600 (YEKST) Received: from 195.20.197.219 (SquirrelMail authenticated user ilgiz) by reid.ru with HTTP; Fri, 12 Jun 2009 11:55:47 +0600 Message-ID: <262c68149962de9309da268bea23ecaa.squirrel@reid.ru> Date: Fri, 12 Jun 2009 11:55:47 +0600 From: =?utf-8?B?0JjQu9GM0LPQuNC3INCv0L3Rg9C30LDQutC+0LI=?= To: freebsd-fs@freebsd.org User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: ZFS performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 06:09:07 -0000 Hi all. Sorry for my english. I'm test ZFS 6 (7.1) and 13 (upgraded to 7.2) version of zpools (results here - http://www.reid.ru/freebsd/?p=1644 [in russian]) and see what performance is degraded (20-30%). Thread in FreeBSD forums - http://forums.freebsd.org/showthread.php?t=4663 What happen? -- Янузаков Ильгиз, системный администратор ООО "Рейд" г. Уфа, Индустриальное шоссе 44/1 E-mail: ilgiz@reid.ru http://www.reid.ru/ ----------------------------- FreeBSD - The Power to Serve! From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 13:56:50 2009 Return-Path: Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA14C1065689; Fri, 12 Jun 2009 13:56:50 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DFA3F8FC1E; Fri, 12 Jun 2009 13:56:49 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA09983; Fri, 12 Jun 2009 16:56:48 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A325E9F.2080802@icyb.net.ua> Date: Fri, 12 Jun 2009 16:56:47 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: zfs related panic X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 13:56:51 -0000 This is on a recent stable/7 amd64, with zpool and filesystems upgraded to the latest version. I did zfs rollback xxx@yyy And then did ls on a directory in the rolled-back fs. I have the core file if it can be of any help. Sleeping thread (tid 100263, pid 2432) owns a non-sleepable lock sched_switch() at 0xffffffff8031d0ef = sched_switch+0x47d mi_switch() at 0xffffffff80302a59 = mi_switch+0x1bf sleepq_switch() at 0xffffffff8032f645 = sleepq_switch+0xd8 sleepq_catch_signals() at 0xffffffff8032f925 = sleepq_catch_signals+0x2db sleepq_wait_sig() at 0xffffffff80330219 = sleepq_wait_sig+0xc _sleep() at 0xffffffff80302eba = _sleep+0x2b5 kern_sigsuspend() at 0xffffffff802fc567 = kern_sigsuspend+0xeb sigsuspend() at 0xffffffff802fc5e9 = sigsuspend+0x34 syscall() at 0xffffffff80491d2d = syscall+0x347 Xfast_syscall() at 0xffffffff8047d00b = Xfast_syscall+0xab --- syscall (341, FreeBSD ELF64, sigsuspend), rip = 0x80092ce3c, rsp = 0x7fffffffdee8, rbp = 0x8011e5a60 --- panic: sleeping thread cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff80192dd5 = db_trace_self_wrapper+0x2a kdb_backtrace() at 0xffffffff80327ea7 = kdb_backtrace+0x32 panic() at 0xffffffff802fb70c = panic+0x1b0 propagate_priority() at 0xffffffff80332e92 = propagate_priority+0x122 turnstile_wait() at 0xffffffff80333e29 = turnstile_wait+0x358 _mtx_lock_sleep() at 0xffffffff802ed64a = _mtx_lock_sleep+0x117 cache_lookup() at 0xffffffff8036a52a = cache_lookup+0x632 vfs_cache_lookup() at 0xffffffff8036a69f = vfs_cache_lookup+0xab VOP_LOOKUP_APV() at 0xffffffff804c86f3 = VOP_LOOKUP_APV+0x51 lookup() at 0xffffffff80370a71 = lookup+0x5d8 namei() at 0xffffffff8037168f = namei+0x320 kern_lstat() at 0xffffffff8037f6ca = kern_lstat+0x5e lstat() at 0xffffffff8037f8c9 = lstat+0x25 syscall() at 0xffffffff80491d2d = syscall+0x347 Xfast_syscall() at 0xffffffff8047d00b = Xfast_syscall+0xab --- syscall (190, FreeBSD ELF64, lstat), rip = 0x80095afbc, rsp = 0x7fffffffdde8, rbp = 0x800b50270 --- -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 17:49:00 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F2641065673 for ; Fri, 12 Jun 2009 17:49:00 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 0EF148FC1B for ; Fri, 12 Jun 2009 17:48:59 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:43692 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1MFAca-0008LK-5s; Fri, 12 Jun 2009 19:32:59 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 8EB7969A0C; Fri, 12 Jun 2009 19:32:54 +0200 (CEST) Message-Id: <920A69B1-4F06-477E-A13B-63CC22A13120@exscape.org> From: Thomas Backman To: FreeBSD Current Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Fri, 12 Jun 2009 19:32:51 +0200 X-Mailer: Apple Mail (2.935.3) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1MFAca-0008LK-5s. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MFAca-0008LK-5s 1b2082f1ed181962a2cdaf51ba028691 Cc: freebsd-fs@freebsd.org Subject: ZFS: Silent/hidden errors, nothing logged anywhere X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 17:49:00 -0000 OK, so I filed a PR late May (kern/135050): http://www.freebsd.org/cgi/query-pr.cgi?pr=135050 . I don't know if this is a "feature" or a bug, but it really should be considered the latter. The data could be repaired in the background without the user ever knowing - until the disk dies completely. I'd prefer to have warning signs (i.e. checksum errors) so that I can buy a replacement drive *before* that. Not only does this mean that errors can go unnoticed, but also that it's impossible to figure out which disk is broken, if ZFS has *temporarily* repaired the broken data! THAT is REALLY bad! Is this something that we can expect to see changed before 8.0-RELEASE? BTW, note that the md5sums always check out (good!), and that it never mentions "x MB repaired" when repairing silent damage (bad!), but only when scrubbing. Scrubbing may be a hard task with a dying disk - I haven't tried it, but I'd guess so. Regards, Thomas PS. I'm not subscribed to fs@, so please CC me if you read this message over there. [root@clone ~]# uname -a FreeBSD clone.exscape.org 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r194059M: Fri Jun 12 18:25:05 CEST 2009 root@clone.exscape.org:/usr/obj/usr/ src/sys/DTRACE amd64 [root@clone ~]# sysctl kern.geom.debugflags=0x10 ### To allow overwriting of the disk kern.geom.debugflags: 0 -> 16 [root@clone ~]# zpool create test raidz da1 da2 da3 [root@clone ~]# dd if=/dev/random of=/test/testfile bs=1000k dd: /test/testfile: No space left on device 188+0 records in 187+1 records out 192413696 bytes transferred in 105.004322 secs (1832436 bytes/sec) [root@clone ~]# dd if=/dev/random of=/dev/da3 bs=1000k count=10 seek=80 10+0 records in 10+0 records out 10240000 bytes transferred in 0.838391 secs (12213871 bytes/sec) [root@clone ~]# cat /test/testfile > /dev/null [root@clone ~]# zpool status -xv pool: test state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 92 errors: No known data errors [root@clone ~]# reboot --- immediately after reboot --- [root@clone ~]# zpool status -xv pool: test state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 1 errors: No known data errors [root@clone ~]# zpool scrub test (...) [root@clone ~]# zpool status -xv pool: test state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: scrub completed after 0h0m with 0 errors on Fri Jun 12 19:11:36 2009 config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 88 2.72M repaired errors: No known data errors [root@clone ~]# reboot --- immediately after reboot, again --- [root@clone ~]# zpool status -xv all pools are healthy [root@clone ~]# zpool status -v test pool: test state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 errors: No known data errors [root@clone ~]# ----------------- even more testing, no scrub this time ----------------- [root@clone ~]# sysctl kern.geom.debugflags=0x10 kern.geom.debugflags: 0 -> 16 [root@clone ~]# md5 /test/testfile && dd if=/dev/random of=/dev/da2 bs=1000k count=10 seek=40 ; md5 /test/testfile MD5 (/test/testfile) = 510479f16592bf66e7ba63c0a4dda0b6 10+0 records in 10+0 records out 10240000 bytes transferred in 0.901645 secs (11357020 bytes/sec) MD5 (/test/testfile) = 510479f16592bf66e7ba63c0a4dda0b6 [root@clone ~]# zpool status -xv pool: test state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 104 da3 ONLINE 0 0 0 errors: No known data errors [root@clone ~]# reboot --- immediately after reboot, yet again --- [root@clone ~]# md5 /test/testfile MD5 (/test/testfile) = 510479f16592bf66e7ba63c0a4dda0b6 [root@clone ~]# zpool status -xv pool: test state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 3 da3 ONLINE 0 0 0 errors: No known data errors [root@clone ~]# reboot --- immediately after reboot, yet *again* --- [root@clone ~]# md5 /test/testfile MD5 (/test/testfile) = 510479f16592bf66e7ba63c0a4dda0b6 [root@clone ~]# zpool status -xv all pools are healthy [root@clone ~]# zpool status -v test pool: test state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM test ONLINE 0 0 0 raidz1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 errors: No known data errors [root@clone ~]# zpool history -il test History for 'test': 2009-06-12.19:03:43 zpool create test raidz da1 da2 da3 [user root on clone.exscape.org:global] 2009-06-12.19:10:42 [internal pool scrub txg:160] func=1 mintxg=0 maxtxg=160 [user root on clone.exscape.org] 2009-06-12.19:10:44 zpool scrub test [user root on clone.exscape.org:global] 2009-06-12.19:11:36 [internal pool scrub done txg:162] complete=1 [user root on clone.exscape.org] From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 20:54:43 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34F4E106566C; Fri, 12 Jun 2009 20:54:43 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id CF48D8FC0A; Fri, 12 Jun 2009 20:54:42 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by an-out-0708.google.com with SMTP id c3so1349595ana.13 for ; Fri, 12 Jun 2009 13:54:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=DSKWok/uA4O/Z5myXRPNIpaF2PiL7FqahsfxPblvy1U=; b=jnqcDcn7AxvYwi9ynbQXMPcYknHFjsc7utHYI3oXmXHaIxggmYg4VviV9RNMQ67nP2 Y+ME/D6pYNMti8InC2tGKtmzxy7YdfcHnSauskTRKbz2SpPAm6tJTDfDsCtr+TI3F6DA O1ZaaMwhEFKoiDiuV6HN0IC/ZT4YSkqLIDjBo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=uOlOLjwA/A6gwxQwgERYJKdCR44Sr98YKrvNOdwAWo1Z8Wr0eWkAyQeLnImIMil+vw qhm2S+5eLyHyg8qFobmrRoQoT5tFs0ow9wBmyDuAvrYAgQPKlUsnYwikO6gQZWcC8jUH anIlRaPd8u5KRD9kDD+kKZbYDSU+pdp3kd/OI= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.3.13 with SMTP id 13mr5484858anc.75.1244840081163; Fri, 12 Jun 2009 13:54:41 -0700 (PDT) In-Reply-To: <4A325E9F.2080802@icyb.net.ua> References: <4A325E9F.2080802@icyb.net.ua> Date: Fri, 12 Jun 2009 13:54:40 -0700 X-Google-Sender-Auth: 2e44c479cd2b2ba1 Message-ID: <3c1674c90906121354s6d6ae7ben5082708b1586e94f@mail.gmail.com> From: Kip Macy To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zfs related panic X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 20:54:43 -0000 show sleepchain show thread 100263 On Fri, Jun 12, 2009 at 6:56 AM, Andriy Gapon wrote: > > This is on a recent stable/7 amd64, with zpool and filesystems upgraded to the > latest version. > I did zfs rollback xxx@yyy > And then did ls on a directory in the rolled-back fs. > > I have the core file if it can be of any help. > > Sleeping thread (tid 100263, pid 2432) owns a non-sleepable lock > sched_switch() at 0xffffffff8031d0ef = sched_switch+0x47d > mi_switch() at 0xffffffff80302a59 = mi_switch+0x1bf > sleepq_switch() at 0xffffffff8032f645 = sleepq_switch+0xd8 > sleepq_catch_signals() at 0xffffffff8032f925 = sleepq_catch_signals+0x2db > sleepq_wait_sig() at 0xffffffff80330219 = sleepq_wait_sig+0xc > _sleep() at 0xffffffff80302eba = _sleep+0x2b5 > kern_sigsuspend() at 0xffffffff802fc567 = kern_sigsuspend+0xeb > sigsuspend() at 0xffffffff802fc5e9 = sigsuspend+0x34 > syscall() at 0xffffffff80491d2d = syscall+0x347 > Xfast_syscall() at 0xffffffff8047d00b = Xfast_syscall+0xab > --- syscall (341, FreeBSD ELF64, sigsuspend), rip = 0x80092ce3c, rsp = > 0x7fffffffdee8, rbp = 0x8011e5a60 --- > panic: sleeping thread > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at 0xffffffff80192dd5 = db_trace_self_wrapper+0x2a > kdb_backtrace() at 0xffffffff80327ea7 = kdb_backtrace+0x32 > panic() at 0xffffffff802fb70c = panic+0x1b0 > propagate_priority() at 0xffffffff80332e92 = propagate_priority+0x122 > turnstile_wait() at 0xffffffff80333e29 = turnstile_wait+0x358 > _mtx_lock_sleep() at 0xffffffff802ed64a = _mtx_lock_sleep+0x117 > cache_lookup() at 0xffffffff8036a52a = cache_lookup+0x632 > vfs_cache_lookup() at 0xffffffff8036a69f = vfs_cache_lookup+0xab > VOP_LOOKUP_APV() at 0xffffffff804c86f3 = VOP_LOOKUP_APV+0x51 > lookup() at 0xffffffff80370a71 = lookup+0x5d8 > namei() at 0xffffffff8037168f = namei+0x320 > kern_lstat() at 0xffffffff8037f6ca = kern_lstat+0x5e > lstat() at 0xffffffff8037f8c9 = lstat+0x25 > syscall() at 0xffffffff80491d2d = syscall+0x347 > Xfast_syscall() at 0xffffffff8047d00b = Xfast_syscall+0xab > --- syscall (190, FreeBSD ELF64, lstat), rip = 0x80095afbc, rsp = 0x7fffffffdde8, > rbp = 0x800b50270 --- > > -- > Andriy Gapon > _______________________________________________ > 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" > -- When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. Edmund Burke From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 21:01:58 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE49A106566B; Fri, 12 Jun 2009 21:01:58 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 5FABE8FC30; Fri, 12 Jun 2009 21:01:58 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1348319ywe.13 for ; Fri, 12 Jun 2009 14:01:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=I1fITzKtgK+exTBbj3AJA2pBVnVdJDMaUy0G8+6WS0I=; b=uoJHJB0O9WtI7p5RuD5yXivtipHT44aPQCiGHWw6d38QG2rmZ1vyexbhSYvnF9NXeZ y1sv+eY8PPxMeMo7xjcl6S2UWKx4K/QMuqXCl7l4RHE/PIgrzoX2rG5oNbOVu4MUcG9O 9+kNIsm0YXd+YjBlYNf5omOK66e9P3vks65NE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=EEjN0FxAO/eG5EVRt0CoeeCJY9/OAkoyw0cH2IUtkPRNsBSGL9kEygPyyOYnVJBzGQ pilA/YaJvsIt/gC/hyHrjsY5QXskOsmp4nHLUyzAHYBafa3xXmpI3UdymJ0Z5ukA5LXr QbeKA6DqOPk5IwW84McBBhBL6n6eXqOo7Q8y0= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.46.10 with SMTP id t10mr5513887ant.116.1244840517509; Fri, 12 Jun 2009 14:01:57 -0700 (PDT) In-Reply-To: <920A69B1-4F06-477E-A13B-63CC22A13120@exscape.org> References: <920A69B1-4F06-477E-A13B-63CC22A13120@exscape.org> Date: Fri, 12 Jun 2009 14:01:57 -0700 X-Google-Sender-Auth: 25126167c0a296b8 Message-ID: <3c1674c90906121401s19105167vf4535566321b45de@mail.gmail.com> From: Kip Macy To: Thomas Backman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, FreeBSD Current Subject: Re: ZFS: Silent/hidden errors, nothing logged anywhere X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 21:01:59 -0000 On Fri, Jun 12, 2009 at 10:32 AM, Thomas Backman wrot= e: > OK, so I filed a PR late May (kern/135050): > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D135050=A0. > I don't know if this is a "feature" or a bug, but it really should be > considered the latter. The data could be repaired in the background witho= ut > the user ever knowing - until the disk dies completely. I'd prefer to hav= e > warning signs (i.e. checksum errors) so that I can buy a replacement driv= e > *before* that. > > Not only does this mean that errors can go unnoticed, but also that it's > impossible to figure out which disk is broken, if ZFS has *temporarily* > repaired the broken data! THAT is REALLY bad! > Is this something that we can expect to see changed before 8.0-RELEASE? I'm fairly certain that we've discussed this already. Solaris uses FMA - I don't think that I'll get to a "real fix" any time soon. The time that I do have will go to addressing stability problems (memory over-allocation, NFS interaction, control directory mounts) all of which cause panics. Maintaining them persistently in the label doesn't make sense - when do you drop them? Would a simple log message about the number of checksum errors suffice? Cheers, Kip From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 21:05:06 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F6BF10656A7 for ; Fri, 12 Jun 2009 21:05:06 +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 4CC298FC19 for ; Fri, 12 Jun 2009 21:05:05 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1MFDvq-00024n-Ca for freebsd-fs@freebsd.org; Fri, 12 Jun 2009 21:05:02 +0000 Received: from 67.177.235.141 ([67.177.235.141]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Jun 2009 21:05:02 +0000 Received: from mlists by 67.177.235.141 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Jun 2009 21:05:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Peter Jones Date: Fri, 12 Jun 2009 14:53:50 -0600 Lines: 14 Message-ID: <86ljnxyy01.fsf@pmade.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 67.177.235.141 User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/22.3 (darwin) Cancel-Lock: sha1:OmNB8sVqBY2G+QGvct/rZavwbqw= Sender: news Subject: Logical Disk to Physical Drive Mapping X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 21:05:07 -0000 Given the situation where you have several identical physical drives, what is the best way to turn logical labels such as da5 into a physical identifier like "the drive in slot 4"? It looks like I could use dmesg, some assumptions, and glabel to label the logical disks. However, I plan to use ZFS and as far as I can tell glabel doesn't support ZFS. What is the de facto way of doing this? I'll be using FreeBSD-CURRENT for this, btw. -- Peter Jones, http://pmade.com pmade inc. Louisville, CO US From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 21:39:30 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FFB9106564A for ; Fri, 12 Jun 2009 21:39:30 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id BA5C38FC17 for ; Fri, 12 Jun 2009 21:39:29 +0000 (UTC) (envelope-from mat.macy@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1359851ywe.13 for ; Fri, 12 Jun 2009 14:39:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=Oi/DCm0SJeT1PEwhW6CIhKeoOoER4/YK2viLhcQAU60=; b=EOeD/optX2qRUTAMBhq6UtGFyEAX3vVMydNZef/wYydLN+JgiZXiiaPRQOXzLFexlV PVLclqyls+egDfkVGUqkI4aOy4r/og5fTFge4F4794AZ+0YCDouiukQ9haSPpXWSBVuM 5ZPr/2Yans0GaqAELybrW+nsq4HM+fg+y1Ttk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=gcNoPt1sgL+wUg3+lrvf3Xg1HfJtmsSBEzxco+S/5eZ00s+B6//SqAEnOHvW7OhHtw qSU92GcQP54c87D+n4GhK9r9Aq2y2Js5cS/bGQdlykJrU0/ut9xWfhAFJC2RNVDxa1ON k63soct9OXZF6Xrzw16DVoIKc2XqsvQcb+m+A= MIME-Version: 1.0 Sender: mat.macy@gmail.com Received: by 10.100.138.19 with SMTP id l19mr5484910and.160.1244842768148; Fri, 12 Jun 2009 14:39:28 -0700 (PDT) In-Reply-To: <262c68149962de9309da268bea23ecaa.squirrel@reid.ru> References: <262c68149962de9309da268bea23ecaa.squirrel@reid.ru> Date: Fri, 12 Jun 2009 14:39:28 -0700 X-Google-Sender-Auth: b135375336e41146 Message-ID: <3c1674c90906121439id0aaffdk8eb410a1870ad3a5@mail.gmail.com> From: Kip Macy To: =?KOI8-R?B?6czYx8naIPHO1drBy8/X?= Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS performance X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 21:39:30 -0000 On Thu, Jun 11, 2009 at 10:55 PM, =E9=CC=D8=C7=C9=DA =F1=CE=D5=DA=C1=CB=CF= =D7 wrote: > Hi all. Sorry for my english. > I'm test ZFS 6 (7.1) and 13 (upgraded to 7.2) version of zpools (results > here - http://www.reid.ru/freebsd/?p=3D1644 [in russian]) and see what > performance is degraded (20-30%). > Thread in FreeBSD forums - http://forums.freebsd.org/showthread.php?t=3D4= 663 > What happen? I don't know. I have a private branch where I've done a lot of work on read and write performance. When these changes make it back, they should at the very least recover the 30% loss. Cheers, From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 22:15:25 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F9F41065670 for ; Fri, 12 Jun 2009 22:15:25 +0000 (UTC) (envelope-from bp@barryp.org) Received: from itasca.hexavalent.net (itasca.hexavalent.net [67.207.138.180]) by mx1.freebsd.org (Postfix) with ESMTP id EB8E68FC08 for ; Fri, 12 Jun 2009 22:15:24 +0000 (UTC) (envelope-from bp@barryp.org) Received: from eden.barryp.org (host-145-114-107-208.midco.net [208.107.114.145]) by itasca.hexavalent.net (Postfix) with ESMTPS id 62CE723C56D for ; Fri, 12 Jun 2009 16:56:19 -0500 (CDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=barryp.org; s=itasca; t=1244843779; bh=/TnaygMAgWtA4YkhKfNWIWODLUFsEJGdDv5zxXxH6es=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=VuNhoIB7a9oP D9muIpRglUjPVf2HKL/XLMoyY/7x0OsbxZUDfYT/aN/XIOijd8uTGdv5lhkoBu7fjm4 tVfdy75aqmHeGm0SBkQIRXD+sep2divdxfGthoD1kCM87riHpiFbo+ABFmFPnr8JYJQ KdkZ73V0KeQI6J1FDrGq7fiQk= Received: from geo.med.und.nodak.edu ([134.129.166.11]) by eden.barryp.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1MFEjS-000BIE-6W; Fri, 12 Jun 2009 16:56:18 -0500 Message-ID: <4A32CF01.4010004@barryp.org> Date: Fri, 12 Jun 2009 16:56:17 -0500 From: Barry Pederson User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: Peter Jones References: <86ljnxyy01.fsf@pmade.com> In-Reply-To: <86ljnxyy01.fsf@pmade.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Logical Disk to Physical Drive Mapping X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 22:15:25 -0000 Peter Jones wrote: > Given the situation where you have several identical physical drives, > what is the best way to turn logical labels such as da5 into a physical > identifier like "the drive in slot 4"? > > It looks like I could use dmesg, some assumptions, and glabel to label > the logical disks. However, I plan to use ZFS and as far as I can tell > glabel doesn't support ZFS. > > What is the de facto way of doing this? I'll be using FreeBSD-CURRENT > for this, btw. I've glabeled disks and then added them to ZFS pools, seems to work fine. Here's a raidz2 setup of 8 identical glabeled drives on 7.2 -------- # zpool status pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz2 ONLINE 0 0 0 label/15_01 ONLINE 0 0 0 label/15_02 ONLINE 0 0 0 label/15_03 ONLINE 0 0 0 label/15_04 ONLINE 0 0 0 label/15_05 ONLINE 0 0 0 label/15_06 ONLINE 0 0 0 label/15_07a ONLINE 0 0 0 label/15_08 ONLINE 0 0 0 errors: No known data errors ------ Barry From owner-freebsd-fs@FreeBSD.ORG Fri Jun 12 23:40:04 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A47881065670 for ; Fri, 12 Jun 2009 23:40:04 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 440FE8FC14 for ; Fri, 12 Jun 2009 23:40:04 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (adsl-67-124-141.shv.bellsouth.net [98.67.124.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 24ED68BDF515; Fri, 12 Jun 2009 18:40:02 -0500 (CDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n5CNdwni065160; Fri, 12 Jun 2009 18:39:59 -0500 (CDT) (envelope-from morganw@chemikals.org) Date: Fri, 12 Jun 2009 18:39:58 -0500 (CDT) From: Wes Morgan To: Peter Jones In-Reply-To: <86ljnxyy01.fsf@pmade.com> Message-ID: References: <86ljnxyy01.fsf@pmade.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: Logical Disk to Physical Drive Mapping X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 23:40:05 -0000 On Fri, 12 Jun 2009, Peter Jones wrote: > Given the situation where you have several identical physical drives, > what is the best way to turn logical labels such as da5 into a physical > identifier like "the drive in slot 4"? > > It looks like I could use dmesg, some assumptions, and glabel to label > the logical disks. However, I plan to use ZFS and as far as I can tell > glabel doesn't support ZFS. > > What is the de facto way of doing this? I'll be using FreeBSD-CURRENT > for this, btw. Use ATA_STATIC_ID for the ATA subsystem to prevent unit numbers from changing when devices are added or removed. For SCSI devices, you can wire down the naming scheme with something like this in /boot/device.hints: hint.scbus.0.at="mpt0" hint.da.0.at="scbus0" hint.da.0.target="0" hint.da.1.at="scbus0" hint.da.1.target="1" hint.da.2.at="scbus0" hint.da.2.target="2" hint.da.3.at="scbus0" hint.da.3.target="3" From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 07:32:18 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 005E2106564A; Sat, 13 Jun 2009 07:32:17 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 82AC18FC1A; Sat, 13 Jun 2009 07:32:17 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:37804 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1MFNin-0007VP-4e; Sat, 13 Jun 2009 09:32:15 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id E5F4E6A447; Sat, 13 Jun 2009 09:32:10 +0200 (CEST) Message-Id: From: Thomas Backman To: Kip Macy In-Reply-To: <3c1674c90906121401s19105167vf4535566321b45de@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sat, 13 Jun 2009 09:32:09 +0200 References: <920A69B1-4F06-477E-A13B-63CC22A13120@exscape.org> <3c1674c90906121401s19105167vf4535566321b45de@mail.gmail.com> X-Mailer: Apple Mail (2.935.3) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1MFNin-0007VP-4e. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MFNin-0007VP-4e 2ff15941a0ff8a5f42f1e0118a8b5be5 Cc: freebsd-fs@freebsd.org, FreeBSD Current Subject: Re: ZFS: Silent/hidden errors, nothing logged anywhere X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 07:32:18 -0000 On Jun 12, 2009, at 11:01 PM, Kip Macy wrote: > On Fri, Jun 12, 2009 at 10:32 AM, Thomas > Backman wrote: >> OK, so I filed a PR late May (kern/135050): >> http://www.freebsd.org/cgi/query-pr.cgi?pr=135050 . >> I don't know if this is a "feature" or a bug, but it really should be >> considered the latter. The data could be repaired in the background >> without >> the user ever knowing - until the disk dies completely. I'd prefer >> to have >> warning signs (i.e. checksum errors) so that I can buy a >> replacement drive >> *before* that. >> >> Not only does this mean that errors can go unnoticed, but also that >> it's >> impossible to figure out which disk is broken, if ZFS has >> *temporarily* >> repaired the broken data! THAT is REALLY bad! >> Is this something that we can expect to see changed before 8.0- >> RELEASE? > > > I'm fairly certain that we've discussed this already. Solaris uses FMA > - I don't think that I'll get to a "real fix" any time soon. The time > that I do have will go to addressing stability problems (memory > over-allocation, NFS interaction, control directory mounts) all of > which cause panics. Maintaining them persistently in the label doesn't > make sense - when do you drop them? Would a simple log message about > the number of checksum errors suffice? > > Cheers, > Kip Yes, I suppose a log message would be OK, especially if there's a semi- simple way of mailing root automatically (either by the ZFS libs themselves, or by a simple log analyzer daemon that I'm sure there are plenty of already). I do think that storing them in the label does make sense, though, but if Solaris doesn't do it, I suppose we shouldn't, either. IF stored that way, they should IMHO remain until a "zpool clear" is executed on device (a device that causes errors is a device that causes errors - most of the time, this is a great way for the disk to say "hey, I'm dying here!"). In practice, this clearing is already done on reboot (although the relevant functions are of course never called). Regards, Thomas From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 15:06:32 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA65F106564A for ; Sat, 13 Jun 2009 15:06:32 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206192061.chello.pl [87.206.192.61]) by mx1.freebsd.org (Postfix) with ESMTP id 0648C8FC14 for ; Sat, 13 Jun 2009 15:06:31 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 9E22745E9C; Sat, 13 Jun 2009 17:06:29 +0200 (CEST) Received: from localhost (chello087206192061.chello.pl [87.206.192.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 814AD4569A; Sat, 13 Jun 2009 17:06:23 +0200 (CEST) Date: Sat, 13 Jun 2009 17:06:27 +0200 From: Pawel Jakub Dawidek To: Kip Macy Message-ID: <20090613150627.GB1848@garage.freebsd.pl> References: <920A69B1-4F06-477E-A13B-63CC22A13120@exscape.org> <3c1674c90906121401s19105167vf4535566321b45de@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uQr8t48UFsdbeI+V" Content-Disposition: inline In-Reply-To: <3c1674c90906121401s19105167vf4535566321b45de@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org, FreeBSD Current , Thomas Backman Subject: Re: ZFS: Silent/hidden errors, nothing logged anywhere X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 15:06:33 -0000 --uQr8t48UFsdbeI+V Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 12, 2009 at 02:01:57PM -0700, Kip Macy wrote: > On Fri, Jun 12, 2009 at 10:32 AM, Thomas Backman wr= ote: > > OK, so I filed a PR late May (kern/135050): > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D135050=A0. > > I don't know if this is a "feature" or a bug, but it really should be > > considered the latter. The data could be repaired in the background wit= hout > > the user ever knowing - until the disk dies completely. I'd prefer to h= ave > > warning signs (i.e. checksum errors) so that I can buy a replacement dr= ive > > *before* that. > > > > Not only does this mean that errors can go unnoticed, but also that it's > > impossible to figure out which disk is broken, if ZFS has *temporarily* > > repaired the broken data! THAT is REALLY bad! > > Is this something that we can expect to see changed before 8.0-RELEASE? >=20 >=20 > I'm fairly certain that we've discussed this already. Solaris uses FMA > - I don't think that I'll get to a "real fix" any time soon. The time > that I do have will go to addressing stability problems (memory > over-allocation, NFS interaction, control directory mounts) all of > which cause panics. Maintaining them persistently in the label doesn't > make sense - when do you drop them? Would a simple log message about > the number of checksum errors suffice? We do log such errors. Solaris uses FMA and for FreeBSD I use devd. You can find the following entry in /etc/devd.conf: notify 10 { match "system" "ZFS"; match "type" "checksum"; action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=3D$pool = path=3D$vdev_path offset=3D$zio_offset size=3D$zio_size'"; }; If you see nothing in your logs, there must be a bug with reporting the problem somewhere or devd is not running (it should be enabled by default). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --uQr8t48UFsdbeI+V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKM8BzForvXbEpPzQRAm8qAKDtRdWdJdv/KSP3kCqtrqZU+0M8VQCaA14F ii4K+WbYT01ZpKw58i1FItw= =fJRK -----END PGP SIGNATURE----- --uQr8t48UFsdbeI+V-- From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 15:13:13 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EA38106566B; Sat, 13 Jun 2009 15:13:13 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id F0B4D8FC15; Sat, 13 Jun 2009 15:13:12 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:59868 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1MFUul-0003IQ-68; Sat, 13 Jun 2009 17:13:05 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 04E5B6AC12; Sat, 13 Jun 2009 17:13:03 +0200 (CEST) Message-Id: From: Thomas Backman To: Pawel Jakub Dawidek In-Reply-To: <20090613150627.GB1848@garage.freebsd.pl> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sat, 13 Jun 2009 17:13:00 +0200 References: <920A69B1-4F06-477E-A13B-63CC22A13120@exscape.org> <3c1674c90906121401s19105167vf4535566321b45de@mail.gmail.com> <20090613150627.GB1848@garage.freebsd.pl> X-Mailer: Apple Mail (2.935.3) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1MFUul-0003IQ-68. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MFUul-0003IQ-68 e6c89ce1cbc939550c23aa3c0065ffd8 Cc: freebsd-fs@freebsd.org, Kip Macy , FreeBSD Current Subject: Re: ZFS: Silent/hidden errors, nothing logged anywhere X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 15:13:14 -0000 On Jun 13, 2009, at 05:06 PM, Pawel Jakub Dawidek wrote: > On Fri, Jun 12, 2009 at 02:01:57PM -0700, Kip Macy wrote: >> On Fri, Jun 12, 2009 at 10:32 AM, Thomas >> Backman wrote: >>> OK, so I filed a PR late May (kern/135050): >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=135050 . >>> I don't know if this is a "feature" or a bug, but it really should >>> be >>> considered the latter. The data could be repaired in the >>> background without >>> the user ever knowing - until the disk dies completely. I'd prefer >>> to have >>> warning signs (i.e. checksum errors) so that I can buy a >>> replacement drive >>> *before* that. >>> >>> Not only does this mean that errors can go unnoticed, but also >>> that it's >>> impossible to figure out which disk is broken, if ZFS has >>> *temporarily* >>> repaired the broken data! THAT is REALLY bad! >>> Is this something that we can expect to see changed before 8.0- >>> RELEASE? >> >> >> I'm fairly certain that we've discussed this already. Solaris uses >> FMA >> - I don't think that I'll get to a "real fix" any time soon. The time >> that I do have will go to addressing stability problems (memory >> over-allocation, NFS interaction, control directory mounts) all of >> which cause panics. Maintaining them persistently in the label >> doesn't >> make sense - when do you drop them? Would a simple log message >> about >> the number of checksum errors suffice? > > We do log such errors. Solaris uses FMA and for FreeBSD I use devd. > You > can find the following entry in /etc/devd.conf: > ... > If you see nothing in your logs, there must be a bug with reporting > the > problem somewhere or devd is not running (it should be enabled by > default). Awesome! After checking further I did indeed find a bunch of such messages in messages.0.bz2. One thing less to worry about, I guess. :) Regards, Thomas From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 16:33:07 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89CB01065673; Sat, 13 Jun 2009 16:33:07 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5FB908FC17; Sat, 13 Jun 2009 16:33:07 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5DGX7WL014575; Sat, 13 Jun 2009 16:33:07 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5DGX7mk014571; Sat, 13 Jun 2009 16:33:07 GMT (envelope-from linimon) Date: Sat, 13 Jun 2009 16:33:07 GMT Message-Id: <200906131633.n5DGX7mk014571@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/135546: [zfs] zfs.ko module doesn't ignore zpool.cache filename supplied by loader X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 16:33:08 -0000 Old Synopsis: zfs.ko module doesn't ignore zpool.cache filename supplied by loader New Synopsis: [zfs] zfs.ko module doesn't ignore zpool.cache filename supplied by loader Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Jun 13 16:32:52 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=135546 From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 16:55:44 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B35951065673 for ; Sat, 13 Jun 2009 16:55:44 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id 69D2F8FC0A for ; Sat, 13 Jun 2009 16:55:44 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from orion.SpringDaemons.com (unknown [77.232.3.143]) by mx0.deglitch.com (Postfix) with ESMTPA id BC3398FC27; Sat, 13 Jun 2009 20:55:42 +0400 (MSD) Received: from orion (localhost [127.0.0.1]) by orion.SpringDaemons.com (Postfix) with SMTP id 8896539C4E; Sat, 13 Jun 2009 20:56:54 +0400 (MSD) Date: Sat, 13 Jun 2009 20:56:48 +0400 From: Stanislav Sedov To: Peter Jones Message-Id: <20090613205648.9840e240.stas@FreeBSD.org> In-Reply-To: <86ljnxyy01.fsf@pmade.com> References: <86ljnxyy01.fsf@pmade.com> Organization: The FreeBSD Project X-XMPP: ssedov@jabber.ru X-Voice: +7 916 849 20 23 X-Mailer: carrier-pigeon X-PGP-Fingerprint: B83A B15D 929A 364A D8BC B3F9 BF25 A231 092F D9F0 Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Sat__13_Jun_2009_20_56_48_+0400_cs_qmfPex/MXByWR" Cc: freebsd-fs@freebsd.org Subject: Re: Logical Disk to Physical Drive Mapping X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 16:55:44 -0000 --Signature=_Sat__13_Jun_2009_20_56_48_+0400_cs_qmfPex/MXByWR Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 12 Jun 2009 14:53:50 -0600 Peter Jones mentioned: > Given the situation where you have several identical physical drives, > what is the best way to turn logical labels such as da5 into a physical > identifier like "the drive in slot 4"? >=20 > It looks like I could use dmesg, some assumptions, and glabel to label > the logical disks. However, I plan to use ZFS and as far as I can tell > glabel doesn't support ZFS. >=20 If you're using ZFS you probably don't need labels at all. AFAIK, ZFS stores all of its information in the on-disk metadata, and you always access data via ZFS volume labels. --=20 Stanislav Sedov ST4096-RIPE --Signature=_Sat__13_Jun_2009_20_56_48_+0400_cs_qmfPex/MXByWR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJKM9pWAAoJEKN82nOYvCd0vbgQAJ0H54WsXim3VGHtTdXbSsn+ B1ViU4i4XZUcwUkC2nwn6Js2uPhDTggWyIZmodfd/eJ3j/HbenDE2XZI9XuhCsMD vQezM+O7LUV79JPBj1Vn7+rVl408qUWerZwLIfTVgec3EEVW+tq83q4JMESrzfLH S1W1Wh/a0BT+EXzbquVjyhRzPrHN3O17SDw02dnmYpxkWmh0acoTTFw2ZEyqmmVt xLriMRBzz9bYXvo3/e+6dJa7WzuA0P+THZGThNL8G7wcPcxjD1wOusjOR1bmibQs WhyTnWeu8FjueZkXtqEtH52KoH1AuMzyXfiAH4iTEg799VInnAcja95FNqP7+86G dqScWXN+RoGHW6m7fdIb14j2YavgiTyS/x6I+k9y1CgFA4PtHbNS9T2tMn3tghTn KHTiPhYErOtM98Z5EGtVEsJK511kv5iBSqcbcLrWhG94BexM3hsAWSLeMxkG803m EZOCoXg5WRcUKpCsUi/741htJ41B58fEydz+mtHCQ2tVehAazdoQ5Y2EOmGGt7xs 6fUE6U3cKtQtT92UsA+sZB9x/wDpSuyC12gDktZn3ZkQGhPpFcvCCV0ijYYGMpUw 7poajqzi4KGJkrU/trJYS2Pa5x/BADqMPuE4IQZNejgnXnwmpQjJHJzCbu67pk/Q A0qdG/9NfVuB1iMcCO1E =QteQ -----END PGP SIGNATURE----- --Signature=_Sat__13_Jun_2009_20_56_48_+0400_cs_qmfPex/MXByWR-- From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 21:40:03 2009 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59931106566B for ; Sat, 13 Jun 2009 21:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2D5B38FC08 for ; Sat, 13 Jun 2009 21:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5DLe3DQ069798 for ; Sat, 13 Jun 2009 21:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5DLe2KG069797; Sat, 13 Jun 2009 21:40:02 GMT (envelope-from gnats) Date: Sat, 13 Jun 2009 21:40:02 GMT Message-Id: <200906132140.n5DLe2KG069797@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Dan Naumov Cc: Subject: Re: misc/118855: [zfs] ZFS-related commands are nonfunctional in fixit shell. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dan Naumov List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 21:40:03 -0000 The following reply was made to PR misc/118855; it has been noted by GNATS. From: Dan Naumov To: bug-followup@FreeBSD.org, erik.swanson@gmail.com Cc: Subject: Re: misc/118855: [zfs] ZFS-related commands are nonfunctional in fixit shell. Date: Sun, 14 Jun 2009 00:32:54 +0300 I am also having this very same problem on my 7.2-RELEASE/amd64, kinda hard to debug ZFS issues when you cannot interact with ZFS from Fixit... - Dan Naumov From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 21:42:08 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6388E106566C for ; Sat, 13 Jun 2009 21:42:08 +0000 (UTC) (envelope-from james-freebsd-current@jrv.org) Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net [70.243.84.13]) by mx1.freebsd.org (Postfix) with ESMTP id DDB908FC0C for ; Sat, 13 Jun 2009 21:42:07 +0000 (UTC) (envelope-from james-freebsd-current@jrv.org) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.14.3) with ESMTP id n5DKsSFh004688; Sat, 13 Jun 2009 15:54:28 -0500 (CDT) (envelope-from james-freebsd-current@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-current@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=Rm+QLpCCRguURyjTmcVo6LrmhyESylQ8+DSWeuSQaKTRam68FMJgJBnk/Y7h+gPYl AjnIxKPpNIxyPqE4ZUpe/E14Dg3TpwN0rVR3i5TKdCu7BMmhGN0fPWh7dmXWOHVZSWB xvMTdG1hL5q4xkMIIxPRYROqelPSyHAObDG6whk= Message-ID: <4A3411EF.5000307@jrv.org> Date: Sat, 13 Jun 2009 15:54:07 -0500 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <920A69B1-4F06-477E-A13B-63CC22A13120@exscape.org> <3c1674c90906121401s19105167vf4535566321b45de@mail.gmail.com> <20090613150627.GB1848@garage.freebsd.pl> In-Reply-To: <20090613150627.GB1848@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Kip Macy , FreeBSD Current , Thomas Backman Subject: Re: ZFS: Silent/hidden errors, nothing logged anywhere X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 21:42:08 -0000 Pawel Jakub Dawidek wrote: > > We do log such errors. Solaris uses FMA and for FreeBSD I use devd. You > can find the following entry in /etc/devd.conf: > > notify 10 { > match "system" "ZFS"; > match "type" "checksum"; > action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'"; > }; > > If you see nothing in your logs, there must be a bug with reporting the > problem somewhere or devd is not running (it should be enabled by > default). > Looking at vsyslog(3), I don't think logger(1) can ever log with facility KERN. LOG_KERN is 0, so this in vsyslog /* Set default facility if none specified. */ if ((pri & LOG_FACMASK) == 0) pri |= LogFacility; will always change the KERN facility is to LogFacility, which defaults to LOG_USER. So the devd output is really going to user.warn and a syslog.conf line like kern.* /var/log/kernel.log will capture kernel messages, but not the devd logger output, and if you look in kernel.log you won't find the checksum errors. From owner-freebsd-fs@FreeBSD.ORG Sat Jun 13 22:07:25 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B7C0106564A for ; Sat, 13 Jun 2009 22:07:25 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id 067488FC1B for ; Sat, 13 Jun 2009 22:07:24 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: by an-out-0708.google.com with SMTP id c3so1614990ana.13 for ; Sat, 13 Jun 2009 15:07:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=Yj9ejHPI79M/csua3b9+3TXywfLXAfpklxHn0FKOmTY=; b=GHxvLcFKqk7lbJa76g/XWkKWB8M4EyTzGp6G6BG3jH7RIuvvbOfKH/2/30J8Gdwuus Ifc0ErYeLo9bA5l+QqbIQ4Jg+bEm/zM0KEYuVzunJA9ThKViqrMf2JZ38G9eiH8XQjbP aR73x0dxjLxoz7rwxtOFVG1AbzBW0w5iVo5sY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=t1wKYTZi/7bYMqbJGVYY/jRvJLVR/iWVsKDm7JZezPlyFCF9w5c/6p12z5N9xthugp VlJu2p4y/GiTxciepZd3NYV/RiAh6yGV1/YVZXNO0Q2hG2v9ns9YUYyO6NRGZ8k+e/dZ 07PA2ocoJ6Ctnut4I/C9yo3+kCwYVJqciWrpk= MIME-Version: 1.0 Received: by 10.101.66.15 with SMTP id t15mr6679420ank.194.1244929273004; Sat, 13 Jun 2009 14:41:13 -0700 (PDT) Date: Sun, 14 Jun 2009 00:41:12 +0300 Message-ID: From: Dan Naumov To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: misc/118855: [zfs] ZFS-related commands are nonfunctional in fixit shell X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2009 22:07:25 -0000 Hello list. >From http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/118855 : "The zfs and zpool commands are nonfunctional in the fixit shell of the 7.0-BETA4-i386-livefs.iso cd image. When either command is run, the result is "internal error: failed to initialize ZFS library"." This PR was submitted on Dec 19 2007 and the same issue still persists on 7.2-RELEASE, is there anything being done to fix this? I am evaluating a small-time deployment of ZFS, but not being able to debug anything ZFS related from within a Fixit envronment if/when things go south is a huge "NO-GO" sign. Sincerely, - Dan Naumov