From owner-freebsd-fs@FreeBSD.ORG Sun May 13 17:35:52 2012 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 1FDC8106566C for ; Sun, 13 May 2012 17:35:52 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id CED6F8FC16 for ; Sun, 13 May 2012 17:35:51 +0000 (UTC) Received: by ggnm2 with SMTP id m2so3363956ggn.13 for ; Sun, 13 May 2012 10:35:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=CDl+9f1vQ+ulJ8GFW8lT//IBi6QNfSgL/tDZ/RF2LWo=; b=j0twDZjSer89LhDvnm/VAK4E4qKxYRa7QawTfqPNgNWHBEXtNWF+bW7d0yiMddzzKh sOmnNcUheU4V9dTRvCVp1bUo4mmZ2FNJMlzn0D7fTWHf9StEf5zKfR2V04t61sJEAqtq 6Wfo626HqHu3m26vfHtHHUyNAYM3qvNQ2GeAluH/RWcASoFJDa4GOppdM28aeNLBysin JnlXDXQzeCwz0ds9PXYbfi0fkW4RlO06EpUvh99XFMB5UoFB55dvvL+czbTF2RbHhk6y sHDePBpQA7AXxtH/G9IqJqxCKp78N2LcHvvYyKanv1cZIIoNicGMJrseY9DvphcLZ4UH baSQ== MIME-Version: 1.0 Received: by 10.50.15.137 with SMTP id x9mr2719632igc.8.1336930551076; Sun, 13 May 2012 10:35:51 -0700 (PDT) Received: by 10.231.31.196 with HTTP; Sun, 13 May 2012 10:35:51 -0700 (PDT) Date: Mon, 14 May 2012 01:35:51 +0800 Message-ID: From: Marcelo Araujo To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Mirror of Raidz for data reliability X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 May 2012 17:35:52 -0000 Hi All, Me and a co-work are working in a new feature for ZFS, we have 2 Machines and 2 JBOD, every Machine are connected on those JBOD via SAS and we are trying to make a fail-over server. Currently every each Machine has two SAS cables, each one connected in both JBOD. We have worked last week to figure out, how we could make the data be always alive in case one JBOD dies, and let me show you my console output ;): controllerA# zpool status -v araujo pool: araujo state: ONLINE scan: resilvered 57K in 0h0m with 0 errors on Sat May 12 14:32:29 2012 config: NAME STATE READ WRITE CKSUM araujo ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da0 ONLINE 0 0 0 da3 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 da1 ONLINE 0 0 0 da4 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 da2 ONLINE 0 0 0 da5 ONLINE 0 0 0 What I have is: A file system called "araujo" created using raidz with 3 disks, than, I can attache new disks to create a mirror for every disk that is part of the raidz, with this case, if one of my JBOD fail, my raidz will still alive, also I can scale with more JBOD to make sure that my data will be always alive. Currently is possible to do the solution above, just comment few lines of code, but our plan is bring something new like: root# zpool create tank raidzm da0 da1 da2 da3 da4 da5 Where da0 da1 da2 will be raidz and da3 da4 da5 will be mirror of da0 da1 da2. In this case, if da0 da1 or da2 fail, we have the mirror and the raidz will still works. I=92m wondering if there is any other elegant solution for this case, HAST could be an option, but I don=92t want use ETHERNET to sync JBOD, and in th= e case above, it is faster to sync any hard driver more less locally. Best Regards, --=20 Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Sun May 13 17:56:46 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7BBD106566B for ; Sun, 13 May 2012 17:56:46 +0000 (UTC) (envelope-from nowakpl@platinum.linux.pl) Received: from platinum.linux.pl (platinum.edu.pl [81.161.192.4]) by mx1.freebsd.org (Postfix) with ESMTP id 87BAD8FC0A for ; Sun, 13 May 2012 17:56:45 +0000 (UTC) Received: by platinum.linux.pl (Postfix, from userid 87) id D165F47E1A; Sun, 13 May 2012 19:46:56 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on platinum.linux.pl X-Spam-Level: X-Spam-Status: No, score=-1.3 required=3.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.3.2 Received: from [172.19.191.4] (c38-073.client.duna.pl [83.151.38.73]) by platinum.linux.pl (Postfix) with ESMTPA id D9CD647E15 for ; Sun, 13 May 2012 19:46:54 +0200 (CEST) Message-ID: <4FAFF38C.3060002@platinum.linux.pl> Date: Sun, 13 May 2012 19:46:52 +0200 From: Adam Nowacki User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Mirror of Raidz for data reliability 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, 13 May 2012 17:56:46 -0000 Wouldn't this accomplish the same? zpool create tank raidz da0 da1 da2 raidz da3 da4 da5 zfs set copies=2 tank On 2012-05-13 19:35, Marcelo Araujo wrote: > Hi All, > > Me and a co-work are working in a new feature for ZFS, we have 2 Machines > and 2 JBOD, every Machine are connected on those JBOD via SAS and we are > trying to make a fail-over server. Currently every each Machine has two SAS > cables, each one connected in both JBOD. > > We have worked last week to figure out, how we could make the data be > always alive in case one JBOD dies, and let me show you my console output > ;): > > controllerA# zpool status -v araujo > pool: araujo > state: ONLINE > scan: resilvered 57K in 0h0m with 0 errors on Sat May 12 14:32:29 2012 > config: > > NAME STATE READ WRITE CKSUM > araujo ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > da0 ONLINE 0 0 0 > da3 ONLINE 0 0 0 > mirror-1 ONLINE 0 0 0 > da1 ONLINE 0 0 0 > da4 ONLINE 0 0 0 > mirror-2 ONLINE 0 0 0 > da2 ONLINE 0 0 0 > da5 ONLINE 0 0 0 > > > What I have is: A file system called "araujo" created using raidz with 3 > disks, than, I can attache new disks to create a mirror for every disk that > is part of the raidz, with this case, if one of my JBOD fail, my raidz will > still alive, also I can scale with more JBOD to make sure that my data will > be always alive. > > Currently is possible to do the solution above, just comment few lines of > code, but our plan is bring something new like: > root# zpool create tank raidzm da0 da1 da2 da3 da4 da5 > > Where da0 da1 da2 will be raidz and da3 da4 da5 will be mirror of da0 da1 > da2. In this case, if da0 da1 or da2 fail, we have the mirror and the raidz > will still works. > > Im wondering if there is any other elegant solution for this case, HAST > could be an option, but I dont want use ETHERNET to sync JBOD, and in the > case above, it is faster to sync any hard driver more less locally. > > > Best Regards, From owner-freebsd-fs@FreeBSD.ORG Mon May 14 02:14:09 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D7DD106567F for ; Mon, 14 May 2012 02:14:09 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id C7DF58FC22 for ; Mon, 14 May 2012 02:14:08 +0000 (UTC) Received: by ggnm2 with SMTP id m2so3506581ggn.13 for ; Sun, 13 May 2012 19:14:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=yLsUUB7nyzu7or4IWrD/6lciW5Ee/IIM8oCeHkYqg80=; b=oDU9Biw+tz8RGe+PWlXNaph6d8EA+0fBmjqWRsPSNYpOiUmjtYfWW7HkDt/j6UEMrG vYR7xNMkhhmAT7TD5FuN5up6Z1HNg6CuYa1WAAiyg05JVUUIznFsHmL2DDNwyNiBleLL +oZUdTfKaAZOqU0dXUaoOCbE6TY0lqiZiRV5GxyxnDkFQC8GB4FWoQ2YfGbinZ05Ghyc vJR454YIoxO3Nizk1gyXKqqyNC28372vSJiOv/r+WmhGzsBzA0rcif+3LBqhbqj22UAO l+C1uNM1Gf/2IaeDfZDBcTaI67NgO4KCj25i6qlFlEoGvcW3Po9o3naMfWgRNpqQOcxW wjLg== MIME-Version: 1.0 Received: by 10.50.100.169 with SMTP id ez9mr835899igb.44.1336961647776; Sun, 13 May 2012 19:14:07 -0700 (PDT) Received: by 10.231.31.196 with HTTP; Sun, 13 May 2012 19:14:07 -0700 (PDT) In-Reply-To: <4FAFF38C.3060002@platinum.linux.pl> References: <4FAFF38C.3060002@platinum.linux.pl> Date: Mon, 14 May 2012 10:14:07 +0800 Message-ID: From: Marcelo Araujo To: Adam Nowacki 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: Mirror of Raidz for data reliability X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2012 02:14:09 -0000 Hello Adam, Well, in my understand it would be not the same. Because it will works as a stripe, and OK we have 2 copies of each striped data between both raidz, however I don't have a mirror for every each disk in the pool, so no data protection. Also I could scale with more JBOD or Machines till 3 times, because zfs set copies support till 3 copies. In case, I use something like: zpool create tank raidz da0 da1 raidz da2 da3 raidz da4 da5 raidz da6 da7 I don't have set copies=3D4, but in the previous email that I sent, you hav= e no limit to set more mirrors. What do you think? Best Regards, - Araujo 2012/5/14 Adam Nowacki > Wouldn't this accomplish the same? > zpool create tank raidz da0 da1 da2 raidz da3 da4 da5 > zfs set copies=3D2 tank > > > On 2012-05-13 19:35, Marcelo Araujo wrote: > >> Hi All, >> >> Me and a co-work are working in a new feature for ZFS, we have 2 Machine= s >> and 2 JBOD, every Machine are connected on those JBOD via SAS and we are >> trying to make a fail-over server. Currently every each Machine has two >> SAS >> cables, each one connected in both JBOD. >> >> We have worked last week to figure out, how we could make the data be >> always alive in case one JBOD dies, and let me show you my console outpu= t >> ;): >> >> controllerA# zpool status -v araujo >> pool: araujo >> state: ONLINE >> scan: resilvered 57K in 0h0m with 0 errors on Sat May 12 14:32:29 2012 >> config: >> >> NAME STATE READ WRITE CKSUM >> araujo ONLINE 0 0 0 >> raidz1-0 ONLINE 0 0 0 >> mirror-0 ONLINE 0 0 0 >> da0 ONLINE 0 0 0 >> da3 ONLINE 0 0 0 >> mirror-1 ONLINE 0 0 0 >> da1 ONLINE 0 0 0 >> da4 ONLINE 0 0 0 >> mirror-2 ONLINE 0 0 0 >> da2 ONLINE 0 0 0 >> da5 ONLINE 0 0 0 >> >> >> What I have is: A file system called "araujo" created using raidz with 3 >> disks, than, I can attache new disks to create a mirror for every disk >> that >> is part of the raidz, with this case, if one of my JBOD fail, my raidz >> will >> still alive, also I can scale with more JBOD to make sure that my data >> will >> be always alive. >> >> Currently is possible to do the solution above, just comment few lines o= f >> code, but our plan is bring something new like: >> root# zpool create tank raidzm da0 da1 da2 da3 da4 da5 >> >> Where da0 da1 da2 will be raidz and da3 da4 da5 will be mirror of da0 da= 1 >> da2. In this case, if da0 da1 or da2 fail, we have the mirror and the >> raidz >> will still works. >> >> I=92m wondering if there is any other elegant solution for this case, HA= ST >> could be an option, but I don=92t want use ETHERNET to sync JBOD, and in= the >> case above, it is faster to sync any hard driver more less locally. >> >> >> Best Regards, >> > > ______________________________**_________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@**freebsd.org > " > --=20 Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Mon May 14 11:07:11 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 372561065794 for ; Mon, 14 May 2012 11:07:11 +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 028AD8FC15 for ; Mon, 14 May 2012 11:07:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4EB7AFg053244 for ; Mon, 14 May 2012 11:07:10 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4EB7AkX053242 for freebsd-fs@FreeBSD.org; Mon, 14 May 2012 11:07:10 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 May 2012 11:07:10 GMT Message-Id: <201205141107.q4EB7AkX053242@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, 14 May 2012 11:07:11 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/167688 fs [fusefs] Incorrect signal handling with direct_io o kern/167685 fs [zfs] ZFS on USB drive prevents shutdown / reboot o kern/167612 fs [portalfs] The portal file system gets stuck inside po o kern/167272 fs [zfs] ZFS Disks reordering causes ZFS to pick the wron o kern/167266 fs [zfs] [nfs] ZFS + new NFS export (sharenfs) leads to N o kern/167260 fs [msdosfs] msdosfs disk was mounted the second time whe o kern/167109 fs [zfs] [panic] zfs diff kernel panic Fatal trap 9: gene o kern/167105 fs [nfs] mount_nfs can not handle source exports wiht mor o kern/167067 fs [zfs] [panic] ZFS panics the server o kern/167066 fs [zfs] ZVOLs not appearing in /dev/zvol o kern/167065 fs [zfs] boot fails when a spare is the boot disk o kern/167048 fs [nfs] [patch] RELEASE-9 crash when using ZFS+NULLFS+NF o kern/166912 fs [ufs] [panic] Panic after converting Softupdates to jo o kern/166851 fs [zfs] [hang] Copying directory from the mounted UFS di o kern/166566 fs [zfs] zfs split renders 2 disk (MBR based) mirror unbo o kern/166477 fs [nfs] NFS data corruption. o kern/165950 fs [ffs] SU+J and fsck problem o kern/165923 fs [nfs] Writing to NFS-backed mmapped files fails if flu o kern/165521 fs [zfs] [hang] livelock on 1 Gig of RAM with zfs when 31 o kern/165392 fs Multiple mkdir/rmdir fails with errno 31 o kern/165087 fs [unionfs] lock violation in unionfs o kern/164472 fs [ufs] fsck -B panics on particular data inconsistency o kern/164370 fs [zfs] zfs destroy for snapshot fails on i386 and sparc o kern/164261 fs [nullfs] [patch] fix panic with NFS served from NULLFS o kern/164256 fs [zfs] device entry for volume is not created after zfs o kern/164184 fs [ufs] [panic] Kernel panic with ufs_makeinode o kern/163801 fs [md] [request] allow mfsBSD legacy installed in 'swap' o kern/163770 fs [zfs] [hang] LOR between zfs&syncer + vnlru leading to o kern/163501 fs [nfs] NFS exporting a dir and a subdir in that dir to o kern/162944 fs [coda] Coda file system module looks broken in 9.0 o kern/162860 fs [zfs] Cannot share ZFS filesystem to hosts with a hyph o kern/162751 fs [zfs] [panic] kernel panics during file operations o kern/162591 fs [nullfs] cross-filesystem nullfs does not work as expe o kern/162519 fs [zfs] "zpool import" relies on buggy realpath() behavi o kern/162362 fs [snapshots] [panic] ufs with snapshot(s) panics when g o kern/161968 fs [zfs] [hang] renaming snapshot with -r including a zvo o kern/161897 fs [zfs] [patch] zfs partition probing causing long delay o kern/161864 fs [ufs] removing journaling from UFS partition fails on o bin/161807 fs [patch] add option for explicitly specifying metadata o kern/161579 fs [smbfs] FreeBSD sometimes panics when an smb share is o kern/161533 fs [zfs] [panic] zfs receive panic: system ioctl returnin o kern/161511 fs [unionfs] Filesystem deadlocks when using multiple uni o kern/161438 fs [zfs] [panic] recursed on non-recursive spa_namespace_ o kern/161424 fs [nullfs] __getcwd() calls fail when used on nullfs mou o kern/161280 fs [zfs] Stack overflow in gptzfsboot o kern/161205 fs [nfs] [pfsync] [regression] [build] Bug report freebsd o kern/161169 fs [zfs] [panic] ZFS causes kernel panic in dbuf_dirty o kern/161112 fs [ufs] [lor] filesystem LOR in FreeBSD 9.0-BETA3 o kern/160893 fs [zfs] [panic] 9.0-BETA2 kernel panic o kern/160860 fs [ufs] Random UFS root filesystem corruption with SU+J o kern/160801 fs [zfs] zfsboot on 8.2-RELEASE fails to boot from root-o o kern/160790 fs [fusefs] [panic] VPUTX: negative ref count with FUSE o kern/160777 fs [zfs] [hang] RAID-Z3 causes fatal hang upon scrub/impo o kern/160706 fs [zfs] zfs bootloader fails when a non-root vdev exists o kern/160591 fs [zfs] Fail to boot on zfs root with degraded raidz2 [r o kern/160410 fs [smbfs] [hang] smbfs hangs when transferring large fil o kern/160283 fs [zfs] [patch] 'zfs list' does abort in make_dataset_ha o kern/159930 fs [ufs] [panic] kernel core o kern/159402 fs [zfs][loader] symlinks cause I/O errors o kern/159357 fs [zfs] ZFS MAXNAMELEN macro has confusing name (off-by- o kern/159356 fs [zfs] [patch] ZFS NAME_ERR_DISKLIKE check is Solaris-s o kern/159351 fs [nfs] [patch] - divide by zero in mountnfs() o kern/159251 fs [zfs] [request]: add FLETCHER4 as DEDUP hash option o kern/159077 fs [zfs] Can't cd .. with latest zfs version o kern/159048 fs [smbfs] smb mount corrupts large files o kern/159045 fs [zfs] [hang] ZFS scrub freezes system o kern/158839 fs [zfs] ZFS Bootloader Fails if there is a Dead Disk o kern/158802 fs amd(8) ICMP storm and unkillable process. o kern/158231 fs [nullfs] panic on unmounting nullfs mounted over ufs o f kern/157929 fs [nfs] NFS slow read o kern/157399 fs [zfs] trouble with: mdconfig force delete && zfs strip o kern/157179 fs [zfs] zfs/dbuf.c: panic: solaris assert: arc_buf_remov o kern/156797 fs [zfs] [panic] Double panic with FreeBSD 9-CURRENT and o kern/156781 fs [zfs] zfs is losing the snapshot directory, p kern/156545 fs [ufs] mv could break UFS on SMP systems o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs p kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 p kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an f bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o kern/118318 fs [nfs] NFS server hangs under special circumstances o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118126 fs [nfs] [patch] Poor NFS server write performance o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 275 problems total. From owner-freebsd-fs@FreeBSD.ORG Tue May 15 10:22:14 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA6CA1065672 for ; Tue, 15 May 2012 10:22:14 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0278FC16 for ; Tue, 15 May 2012 10:22:14 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.iaf.psconsult.nl [80.89.238.138]) by mx1.psconsult.nl (8.14.4/8.14.4) with ESMTP id q4FAM7CU022829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 May 2012 12:22:12 +0200 (CEST) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.4/8.14.4/Submit) id q4FAM6jT022828 for freebsd-fs@freebsd.org; Tue, 15 May 2012 12:22:07 +0200 (CEST) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Tue, 15 May 2012 12:22:06 +0200 From: Paul Schenkeveld To: freebsd-fs@freebsd.org Message-ID: <20120515102206.GA53750@psconsult.nl> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: Mirror of Raidz for data reliability 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, 15 May 2012 10:22:14 -0000 On Mon, May 14, 2012 at 01:35:51AM +0800, Marcelo Araujo wrote: > Hi All, > > Me and a co-work are working in a new feature for ZFS, we have 2 Machines > and 2 JBOD, every Machine are connected on those JBOD via SAS and we are > trying to make a fail-over server. Currently every each Machine has two SAS > cables, each one connected in both JBOD. > > We have worked last week to figure out, how we could make the data be > always alive in case one JBOD dies, and let me show you my console output > ;): > > controllerA# zpool status -v araujo > pool: araujo > state: ONLINE > scan: resilvered 57K in 0h0m with 0 errors on Sat May 12 14:32:29 2012 > config: > > NAME STATE READ WRITE CKSUM > araujo ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > da0 ONLINE 0 0 0 > da3 ONLINE 0 0 0 > mirror-1 ONLINE 0 0 0 > da1 ONLINE 0 0 0 > da4 ONLINE 0 0 0 > mirror-2 ONLINE 0 0 0 > da2 ONLINE 0 0 0 > da5 ONLINE 0 0 0 > Maybe a dumb question, how you you create the above setup? I seem unable to create a raidz consisting of mirrors neither can I attach a second physical drive to an existing one in a raidz of three single drives: # zpool create tank raidz1 mirror /dev/da0 /dev/da3 mirror /dev/da1 /dev/da4 mirror /dev/da2 /dev/da5 invalid vdev specification: raidz1 requires at least 2 devices # zpool create tank raidz1 /dev/da0 /dev/da1 /dev/da2 # zpool attach tank /dev/da0 /dev/da3 cannot attach /dev/da3 to /dev/da0: can only attach to mirrors and top-level disks # zpool upgrade This system is currently running ZFS pool version 28. All pools are formatted using this version. Kind regards, Paul Schenkeveld From owner-freebsd-fs@FreeBSD.ORG Tue May 15 11:55:42 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C725106566B for ; Tue, 15 May 2012 11:55:42 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id B88178FC0C for ; Tue, 15 May 2012 11:55:41 +0000 (UTC) Received: by yenl8 with SMTP id l8so6719262yen.13 for ; Tue, 15 May 2012 04:55:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Bv7/ifoi+hmEXqJraPD6fLPkMZoeQn/+pD27PHnPyEI=; b=ycFVHKky6Et4wnhdHnZ8oQsq4WF8dgsrp5RW7ClFblmKts1Ww5hBH/T248ebPNfC4r X38uSf1cooBAyZtfft4ln+dM92nw4F2+L2W2zrLCUERwhh3f6YL1mTMhJozRSc365EEv QIiV74mK0w0ZoNKLqnj9xoMrBw8QtY7CLz/tBW3rwW9j/Ru64TLxyZqMgpXp7/ylAfaO WhXYwafc2Wqu/g512bF4alWkcNCpkl698xjG89FAVvjIZeKhO+cmgXLEmFHN1iOBnQRz HIUfVVnYE1ngYQeLcXInHdXefCIyGg/Al9wEDc72LOhnteqId/BewXNWAmVn32ZxS3to 6M9w== MIME-Version: 1.0 Received: by 10.42.122.76 with SMTP id m12mr863852icr.38.1337082940830; Tue, 15 May 2012 04:55:40 -0700 (PDT) Received: by 10.231.31.196 with HTTP; Tue, 15 May 2012 04:55:40 -0700 (PDT) In-Reply-To: <20120515102206.GA53750@psconsult.nl> References: <20120515102206.GA53750@psconsult.nl> Date: Tue, 15 May 2012 19:55:40 +0800 Message-ID: From: Marcelo Araujo To: Paul Schenkeveld Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Mirror of Raidz for data reliability X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2012 11:55:42 -0000 2012/5/15 Paul Schenkeveld > On Mon, May 14, 2012 at 01:35:51AM +0800, Marcelo Araujo wrote: > > Hi All, > > > > Me and a co-work are working in a new feature for ZFS, we have 2 Machines > > and 2 JBOD, every Machine are connected on those JBOD via SAS and we are > > trying to make a fail-over server. Currently every each Machine has two > SAS > > cables, each one connected in both JBOD. > > > > We have worked last week to figure out, how we could make the data be > > always alive in case one JBOD dies, and let me show you my console output > > ;): > > > > controllerA# zpool status -v araujo > > pool: araujo > > state: ONLINE > > scan: resilvered 57K in 0h0m with 0 errors on Sat May 12 14:32:29 2012 > > config: > > > > NAME STATE READ WRITE CKSUM > > araujo ONLINE 0 0 0 > > raidz1-0 ONLINE 0 0 0 > > mirror-0 ONLINE 0 0 0 > > da0 ONLINE 0 0 0 > > da3 ONLINE 0 0 0 > > mirror-1 ONLINE 0 0 0 > > da1 ONLINE 0 0 0 > > da4 ONLINE 0 0 0 > > mirror-2 ONLINE 0 0 0 > > da2 ONLINE 0 0 0 > > da5 ONLINE 0 0 0 > > > > Maybe a dumb question, how you you create the above setup? I seem unable > to create a raidz consisting of mirrors neither can I attach a second > physical drive to an existing one in a raidz of three single drives: > > # zpool create tank raidz1 mirror /dev/da0 /dev/da3 mirror /dev/da1 > /dev/da4 mirror /dev/da2 /dev/da5 > invalid vdev specification: raidz1 requires at least 2 devices > > # zpool create tank raidz1 /dev/da0 /dev/da1 /dev/da2 > # zpool attach tank /dev/da0 /dev/da3 > cannot attach /dev/da3 to /dev/da0: can only attach to mirrors and > top-level disks > > # zpool upgrade > This system is currently running ZFS pool version 28. > > All pools are formatted using this version. > > Kind regards, > > Paul Schenkeveld > Hey Paul, Yes, I'm using the latest version with code modification, it might be a new feature. The currently ZFS doesn't support this kind of set, that was I ask, if there is another way that I supposed to don't know and could do the same thing. If it make sense, maybe, I'll put more effort to bring this kind of stuff as a new feature. However, it is not so simple that I could made in few days as well as have this feature only on FreeBSD, it will make the code inconsistent between our ZFS port and Illumos-gate. But is interesting. Best Regards, -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Tue May 15 17:20:07 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA04F106564A for ; Tue, 15 May 2012 17:20:07 +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 9FBAE8FC0A for ; Tue, 15 May 2012 17:20:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4FHK7Mg088978 for ; Tue, 15 May 2012 17:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4FHK7pE088977; Tue, 15 May 2012 17:20:07 GMT (envelope-from gnats) Date: Tue, 15 May 2012 17:20:07 GMT Message-Id: <201205151720.q4FHK7pE088977@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: bin/155104: commit references a PR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2012 17:20:07 -0000 The following reply was made to PR bin/155104; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/155104: commit references a PR Date: Tue, 15 May 2012 17:11:15 +0000 (UTC) Author: avg Date: Tue May 15 17:11:00 2012 New Revision: 235479 URL: http://svn.freebsd.org/changeset/base/235479 Log: zpool_find_import_impl: another /dev/dsk -> /dev fix This seems to fix zdb -e behavior. PR: bin/155104 Submitted by: swell.k@gmail.com MFC after: 2 weeks Modified: head/cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c Modified: head/cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c ============================================================================== --- head/cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c Tue May 15 17:07:29 2012 (r235478) +++ head/cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c Tue May 15 17:11:00 2012 (r235479) @@ -1145,7 +1145,7 @@ zpool_find_import_impl(libzfs_handle_t * char *end, **dir = iarg->path; size_t pathleft; nvlist_t *ret = NULL; - static char *default_dir = "/dev/dsk"; + static char *default_dir = "/dev"; pool_list_t pools = { 0 }; pool_entry_t *pe, *penext; vdev_entry_t *ve, *venext; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue May 15 22:03:33 2012 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 0E2591065670 for ; Tue, 15 May 2012 22:03:33 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id BD7EC8FC14 for ; Tue, 15 May 2012 22:03:32 +0000 (UTC) Received: from conversation.bsdunix.ch (localhost [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id 488FDBFEB for ; Tue, 15 May 2012 21:54:35 +0000 (UTC) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by conversation.bsdunix.ch (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QAQdBcEj0DD0 for ; Tue, 15 May 2012 21:54:34 +0000 (UTC) Received: from Toms-Saftbook.local (dmhd.bsdunix.ch [82.220.17.25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTPSA id 3554BBFE6 for ; Tue, 15 May 2012 21:54:34 +0000 (UTC) Message-ID: <4FB2D099.8040103@bsdunix.ch> Date: Tue, 15 May 2012 23:54:33 +0200 From: Tom User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Subject: zfs userquota support for rquotad (nfs)? 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, 15 May 2012 22:03:33 -0000 Hello Has someone tried or is working on an implementation to add ZFS userquota support to rquotad? https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/4f68f041ddcd Regards, Tom From owner-freebsd-fs@FreeBSD.ORG Wed May 16 02:22:28 2012 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 7620E106566B for ; Wed, 16 May 2012 02:22:28 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 26C828FC17 for ; Wed, 16 May 2012 02:22:27 +0000 (UTC) Received: by yenl8 with SMTP id l8so302641yen.13 for ; Tue, 15 May 2012 19:22:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=il6Ygms11ULl5p0iXra8JeWrDyPHZhIae17DPYmwEVQ=; b=yPFHZ17Z89EPgmPXnIK9eTm8GvG8U4rtW1tn2wBXSfYQF0hHcizPPZ02/wILSJ6Cv+ 5ee5RwBayOfrN6a3019dgfWAvgB4YJFmTapkue6Duquphi5VmeHBraLCFlMpoRqPeM0T OJIhVBCQm3iNhYJq11xquO+NE2+qNIVnT48JbVazYKM7Fn9T041lxkzP6Y0OZpcF+TDs noCSQcWhdPmMc4vrbpi1+Jeyr1z589OkNtuM3/4wGmDKBXLcdxh9waj/G+AdKEHGJKkx Pu6epLxtvy0Cp5eGJ7cEUDcspGd6G2Rg+6uM9xQQJSY1jEebDirJMLks3Pjwr2Z/YZs+ 9wTg== MIME-Version: 1.0 Received: by 10.50.140.70 with SMTP id re6mr738132igb.23.1337134947154; Tue, 15 May 2012 19:22:27 -0700 (PDT) Received: by 10.231.31.196 with HTTP; Tue, 15 May 2012 19:22:27 -0700 (PDT) In-Reply-To: <4FB2D099.8040103@bsdunix.ch> References: <4FB2D099.8040103@bsdunix.ch> Date: Wed, 16 May 2012 10:22:27 +0800 Message-ID: From: Marcelo Araujo To: Tom Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: zfs userquota support for rquotad (nfs)? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2012 02:22:28 -0000 Hello Tom and All, If there is no one working on it, I'm gonna take a look on it this weekend. Best Regards, - Marcelo Araujo 2012/5/16 Tom > Hello > > Has someone tried or is working on an implementation to add ZFS > userquota support to rquotad? > > https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/4f68f041ddcd > > Regards, > Tom > _______________________________________________ > 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" > -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Wed May 16 02:33:55 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0975F1065673; Wed, 16 May 2012 02:33:55 +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 D0E748FC14; Wed, 16 May 2012 02:33:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4G2XsvE016002; Wed, 16 May 2012 02:33:54 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4G2Xsmk015998; Wed, 16 May 2012 02:33:54 GMT (envelope-from linimon) Date: Wed, 16 May 2012 02:33:54 GMT Message-Id: <201205160233.q4G2Xsmk015998@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167905: [zfs] zfs set canmount=on UNMOUNTS dataset 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, 16 May 2012 02:33:55 -0000 Old Synopsis: zfs set canmount=on UNMOUNTS dataset New Synopsis: [zfs] zfs set canmount=on UNMOUNTS dataset Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed May 16 02:33:39 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167905 From owner-freebsd-fs@FreeBSD.ORG Wed May 16 08:35:15 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CE06106572A; Wed, 16 May 2012 08:35:15 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id 415758FC17; Wed, 16 May 2012 08:35:13 +0000 (UTC) Received: from conversation.bsdunix.ch (localhost [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id CB3B7B7B4; Wed, 16 May 2012 08:35:11 +0000 (UTC) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by conversation.bsdunix.ch (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id x885cXf4ageg; Wed, 16 May 2012 08:35:10 +0000 (UTC) Received: from ernie.mlan.solnet.ch (ernie.mlan.solnet.ch [212.101.1.20]) by conversation.bsdunix.ch (Postfix) with ESMTPA id C587EB7B1; Wed, 16 May 2012 08:35:10 +0000 (UTC) Message-ID: <4FB366BE.50203@bsdunix.ch> Date: Wed, 16 May 2012 10:35:10 +0200 From: Thomas User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: araujo@FreeBSD.org References: <4FB2D099.8040103@bsdunix.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Araujo , freebsd-fs@freebsd.org Subject: Re: zfs userquota support for rquotad (nfs)? 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, 16 May 2012 08:35:15 -0000 Hi Marcelo Am 5/16/12 4:22 AM, schrieb Marcelo Araujo: > Hello Tom and All, > > If there is no one working on it, I'm gonna take a look on it this weekend. Great. I can test patches. Regards, Tom > > 2012/5/16 Tom > > > Hello > > Has someone tried or is working on an implementation to add ZFS > userquota support to rquotad? > > https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/4f68f041ddcd > > Regards, > Tom > _______________________________________________ > 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 > " > > > > > -- > Marcelo Araujo > araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Wed May 16 20:22:43 2012 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 08491106566C; Wed, 16 May 2012 20:22:43 +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 CF6358FC16; Wed, 16 May 2012 20:22:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4GKMgQa045298; Wed, 16 May 2012 20:22:42 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4GKMgqw045294; Wed, 16 May 2012 20:22:42 GMT (envelope-from linimon) Date: Wed, 16 May 2012 20:22:42 GMT Message-Id: <201205162022.q4GKMgqw045294@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167977: [smbfs] mount_smbfs results are differ when utf-8 or UTF-8 local encoding's name is used 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, 16 May 2012 20:22:43 -0000 Old Synopsis: mount_smbfs results are differ when utf-8 or UTF-8 local encoding's name is used New Synopsis: [smbfs] mount_smbfs results are differ when utf-8 or UTF-8 local encoding's name is used Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed May 16 20:22:26 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167977 From owner-freebsd-fs@FreeBSD.ORG Wed May 16 21:10:04 2012 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 2FE49106566B for ; Wed, 16 May 2012 21:10:04 +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 EEE5B8FC1B for ; Wed, 16 May 2012 21:10:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4GLA3O8083500 for ; Wed, 16 May 2012 21:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4GLA3RF083499; Wed, 16 May 2012 21:10:03 GMT (envelope-from gnats) Date: Wed, 16 May 2012 21:10:03 GMT Message-Id: <201205162110.q4GLA3RF083499@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Buganini Cc: Subject: Re: kern/167977: [smbfs] mount_smbfs results are differ when utf-8 or UTF-8 local encoding's name is used X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Buganini List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2012 21:10:04 -0000 The following reply was made to PR kern/167977; it has been noted by GNATS. From: Buganini To: bug-followup@FreeBSD.org, alexey_kovalenko@inbox.ru Cc: Subject: Re: kern/167977: [smbfs] mount_smbfs results are differ when utf-8 or UTF-8 local encoding's name is used Date: Thu, 17 May 2012 05:08:14 +0800 How about change line 105 and 107 in /usr/src/sys/libkern/iconv_ucs.c from strcmp to strcasecmp ? Regards, Buganini From owner-freebsd-fs@FreeBSD.ORG Wed May 16 21:49:30 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02AE41065676 for ; Wed, 16 May 2012 21:49:30 +0000 (UTC) (envelope-from lists@hurricane-ridge.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C671E8FC17 for ; Wed, 16 May 2012 21:49:29 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so1860805pbb.13 for ; Wed, 16 May 2012 14:49:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=GTV9N7/MLEPXxYo5BWaUngKmoJb/W4PBX/S/EjFTOqc=; b=i0b2zoYqwit4EvVV7Ug3l8lu/sb5Pv7QCE7Cv8PTzBsj4zVrjSoWK6ii5EjRg+z59e Y2zsPgQZJxkqQ6XM9peOJ7PDuyiSb7BvsnUnNGwXKQP83DUTLNVuIA5JQABw5IzBBQiB vS2afRFnBG2sLCozEYnHkoHJQ3e8sr3KiLgMI67CE7XTeImZ4xH69Ywn7Wc0gNtHbeTp 19n4JiLRB9JOz4DbXFZBdVvIFvtSJ7scwr/+Dz47poX7cP2/5im2QytQwT/M1S2R7jeQ YfNp2+jZcgenXjebUPWYPuA7kccopir8adPfjEwQ2XqfkGjvaN2DqiecvCmdTAdGZoiU KOfA== MIME-Version: 1.0 Received: by 10.68.231.195 with SMTP id ti3mr20439746pbc.96.1337204969288; Wed, 16 May 2012 14:49:29 -0700 (PDT) Received: by 10.68.195.166 with HTTP; Wed, 16 May 2012 14:49:29 -0700 (PDT) X-Originating-IP: [98.247.224.125] In-Reply-To: <1831201709.296992.1336789851115.JavaMail.root@erie.cs.uoguelph.ca> References: <1831201709.296992.1336789851115.JavaMail.root@erie.cs.uoguelph.ca> Date: Wed, 16 May 2012 14:49:29 -0700 Message-ID: From: Andrew Leonard To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlKsA99ePKtf4W4U0w/kpHdPKfLsRrdOvHHbH76V7K/floDusP7Q0ABKr8T1gP0TcrYyeT7 Cc: freebsd-fs@freebsd.org Subject: Re: Unable to set ACLs on ZFS file system over NFSv4? 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, 16 May 2012 21:49:30 -0000 On Fri, May 11, 2012 at 7:30 PM, Rick Macklem wrote: > Andrew Leonard wrote: >> On Thu, May 10, 2012 at 2:23 PM, Rick Macklem >> wrote: >> >> > I wrote: >> >> >> If you capture a packet trace from before you do the NFSv4 mount, I >> >> can >> >> take a look and see what the server is saying. (Basically, at mount >> >> time >> >> a reply to a Getattr should including the supported attributes and >> >> that >> >> should include the ACL bit. Then the setfacl becomes a Setattr of >> >> the >> >> ACL >> >> attribute.) >> >> # tcpdump -s 0 -w acl.pcap host >> >> - run on the client should do it >> >> >> >> If you want to look at it, use wireshark. If you want me to look, >> >> just >> >> email acl.pcap as an attachment. >> >> >> >> rick >> >> ps: Although I suspect it is the server that isn't behaving, please >> >> use >> >> the FreeBSD client for the above. >> >> pss: I've cc'd trasz@ in case he can spot some reason why it >> >> wouldn't >> >> work. >> >> >> > Oh, and make sure "user1" isn't in more than 16 groups, because that >> > is the >> > limit for AUTH_SYS. (I'm not sure what the effect of user1 being in >> > more >> > than 16 groups would be, but might as well eliminate it as a cause.) >> >> Thanks, Rick - I'll send the pcap over private email, as I'm sure >> $DAYJOB would consider it somewhat sensitive. >> >> Looking in wireshark, if I'm reading it correctly, I don't see >> anything for FATTR4_ACL in any replies. On the final connection, I do >> see NFS4ERR_IO set as the status for the reply to the setattr - but >> from Googling, my understanding is that response is supposed to >> indicate a hard error, such as a hardware problem. >> > Yep, it appears that ZFS returned an error that isn't in the list of > replies for getattr, so it got mapped to EIO (the catch all for error > codes not known to NFS). > > I took a quick look at the ZFS code and the problem looks pretty > obvious. ZFS replies EOPNOTSUPP to the VOP_ACLCHECK() and that's > as far as it gets. > > Please try the attached patch in the server (untested, but all it does is go ahead > and try the VOP_SETACL() for the case where VOP_ACLCHECK() replies > EOPNOTSUPP) and let me know if it helps. It took me a little while to get a test environment set up, but with the patch applied, ACLs can be set on the ZFS file system over NFSv4. Thanks, Andy > Thanks for reporting this and sending the packet trace, rick > >> Also, I have verified that "user1" is not a member of more than 16 >> groups, so we can rule that out - that user is in only three groups. >> >> -Andy From owner-freebsd-fs@FreeBSD.ORG Wed May 16 22:17:57 2012 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 BA75E106564A for ; Wed, 16 May 2012 22:17:57 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (firebox.emsphone.com [199.67.51.15]) by mx1.freebsd.org (Postfix) with ESMTP id 71AFB8FC14 for ; Wed, 16 May 2012 22:17:57 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [172.17.17.101]) by email2.allantgroup.com (8.14.4/8.14.4) with ESMTP id q4GMH9VA063749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 17:17:10 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.5/8.14.5) with ESMTP id q4GMH9Qv031465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 17:17:09 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.5/8.14.5/Submit) id q4GMH9vf031463; Wed, 16 May 2012 17:17:09 -0500 (CDT) (envelope-from dan) Date: Wed, 16 May 2012 17:17:09 -0500 From: Dan Nelson To: Tom Message-ID: <20120516221709.GA1933@dan.emsphone.com> References: <4FB2D099.8040103@bsdunix.ch> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <4FB2D099.8040103@bsdunix.ch> X-OS: FreeBSD 8.3-PRERELEASE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.2 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (email2.allantgroup.com [172.17.19.78]); Wed, 16 May 2012 17:17:10 -0500 (CDT) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on email2.allantgroup.com X-Scanned-By: MIMEDefang 2.68 on 172.17.19.78 Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs userquota support for rquotad (nfs)? 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, 16 May 2012 22:17:57 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In the last episode (May 15), Tom said: > Hello > > Has someone tried or is working on an implementation to add ZFS > userquota support to rquotad? > > https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/4f68f041ddcd Here's a simple implementation I coded up a year ago. Instead of trying to link in libzfs on the fly, it simply popens a "zfs get" command to fetch the user's quota info. -- Dan Nelson dnelson@allantgroup.com --FCuugMFkClbJLl1L Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="userquota.diff" Index: rquotad.c =================================================================== --- rquotad.c (revision 234445) +++ rquotad.c (working copy) @@ -36,7 +36,8 @@ void printerr_reply(SVCXPRT *transp); void initfs(void); int getfsquota(long id, char *path, struct dqblk *dqblk); -int hasquota(struct fstab *fs, char **qfnamep); +int hasquota(struct fstab *fs, const char **qfnamep); +static int getzfsquota(uid_t user, char *dataset, struct dqblk *zq); /* * structure containing informations about ufs filesystems @@ -45,6 +46,8 @@ struct fs_stat { struct fs_stat *fs_next; /* next element */ char *fs_file; /* mount point of the filesystem */ + char *fs_spec; /* device name of the filesystem */ + char *fs_type; /* type of the filesystem */ char *qfpathname; /* pathname of the quota file */ dev_t st_dev; /* device of the filesystem */ } fs_stat; @@ -209,17 +212,22 @@ { struct fs_stat *fs_current = NULL; struct fs_stat *fs_next = NULL; - char *qfpathname; + const char *qfpathname; struct fstab *fs; struct stat st; setfsent(); while ((fs = getfsent())) { - if (strcmp(fs->fs_vfstype, "ufs")) + /* Only process UFS or ZFS filesystems */ + if (strcmp(fs->fs_vfstype, "ufs") && strcmp(fs->fs_vfstype, "zfs")) continue; - if (!hasquota(fs, &qfpathname)) + /* Skip UFS filesystems with quotas disabled */ + if ((strcmp(fs->fs_vfstype, "ufs") == 0) && !hasquota(fs, &qfpathname)) continue; + if (strcmp(fs->fs_vfstype, "zfs") == 0) + qfpathname = ""; + fs_current = (struct fs_stat *) malloc(sizeof(struct fs_stat)); fs_current->fs_next = fs_next; /* next element */ @@ -227,6 +235,14 @@ malloc(sizeof(char) * (strlen(fs->fs_file) + 1)); strcpy(fs_current->fs_file, fs->fs_file); + fs_current->fs_spec = + malloc(sizeof(char) * (strlen(fs->fs_spec) + 1)); + strcpy(fs_current->fs_spec, fs->fs_spec); + + fs_current->fs_type = + malloc(sizeof(char) * (strlen(fs->fs_vfstype) + 1)); + strcpy(fs_current->fs_type, fs->fs_vfstype); + fs_current->qfpathname = malloc(sizeof(char) * (strlen(qfpathname) + 1)); strcpy(fs_current->qfpathname, qfpathname); @@ -257,10 +273,13 @@ qcmd = QCMD(Q_GETQUOTA, USRQUOTA); for (fs = fs_begin; fs != NULL; fs = fs->fs_next) { - /* where the devise is the same as path */ + /* where the device is the same as path */ if (fs->st_dev != st_path.st_dev) continue; + if (strcmp(fs->fs_type, "zfs") == 0) + return (getzfsquota(id, fs->fs_spec, dqblk)); + /* find the specified filesystem. get and return quota */ if (quotactl(fs->fs_file, qcmd, id, dqblk) == 0) return (1); @@ -300,7 +319,7 @@ * Comes from quota.c, NetBSD 0.9 */ int -hasquota(struct fstab *fs, char **qfnamep) +hasquota(struct fstab *fs, const char **qfnamep) { static char initname, usrname[100]; static char buf[BUFSIZ]; @@ -329,3 +348,43 @@ *qfnamep = buf; return (1); } + +static int +getzfsquota(uid_t user, char *dataset, struct dqblk *zq) +{ + uint64_t userquota, userused; + FILE *zfp; + char buf[64]; + char *cmd; + int failed = 0; + + asprintf(&cmd, "zfs get -Hp -o value userquota@%d,userused@%d %s", user, user, dataset); + if (cmd == NULL) + return (0); + + zfp = popen(cmd, "r"); + free(cmd); + if (zfp == NULL) + return (0); + + if (fgets(buf, sizeof(buf), zfp) == NULL) + failed = 1; + if (!failed && (sscanf(buf, "%lld", &userquota) != 1)) + failed = 1; + if (!failed && (fgets(buf, sizeof(buf), zfp) == NULL)) + failed = 1; + if (!failed && (sscanf(buf, "%lld", &userused) != 1)) + failed = 1; + failed += pclose(zfp); + + if (failed) + return(0); + + bzero(zq, sizeof(struct dqblk)); + + zq->dqb_bhardlimit = userquota / DEV_BSIZE; + zq->dqb_bsoftlimit = userquota / DEV_BSIZE; + zq->dqb_curblocks = userused / DEV_BSIZE; + + return (1); +} --FCuugMFkClbJLl1L-- From owner-freebsd-fs@FreeBSD.ORG Wed May 16 23:43:25 2012 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 C5DBE106564A for ; Wed, 16 May 2012 23:43:25 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 72A988FC08 for ; Wed, 16 May 2012 23:43:25 +0000 (UTC) Received: by vbmv11 with SMTP id v11so1638808vbm.13 for ; Wed, 16 May 2012 16:43:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=D6tkf7UjNkS/APEiZ5bDy5S9YNqfTOegrVp/+S0UhbA=; b=WrrZz+GY9x3/LNPvD34JXv6pqwEPjACsmK5WZg2WtLl2wa5rEuJfrnvV9sCh2fwv3x hqby4hiWsXVvq09rrQfFuXFDlWVYHiLAFJ2EZ3i6/JbhZ8/wxfRpZ8RzpyeV2u6e+SR6 9tbj2VW/O+qRGx2l4EMQaJJ0GFWWbVTJkRjR+G0lk1ABuyNxgEM91aSNeiF//VrivrNZ muX/+7ZuzPpxpnw7MpDoMvkx4Hr4Pgh+U9awkVeX40xRM0Gq0HFxZcaJ1WWmbPIit2B7 9SUyruAZKkp+zzcbPVTdlT5BSI4lNNwcv21P+26MuqhBVSr3LopsgXnWksMtJp6/94Mq tGfg== MIME-Version: 1.0 Received: by 10.221.1.80 with SMTP id np16mr3712340vcb.33.1337211801707; Wed, 16 May 2012 16:43:21 -0700 (PDT) Received: by 10.220.8.202 with HTTP; Wed, 16 May 2012 16:43:21 -0700 (PDT) In-Reply-To: References: <20120515102206.GA53750@psconsult.nl> Date: Thu, 17 May 2012 02:43:21 +0300 Message-ID: From: George Kontostanos To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Mirror of Raidz for data reliability 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, 16 May 2012 23:43:25 -0000 On Tue, May 15, 2012 at 2:55 PM, Marcelo Araujo w= rote: > 2012/5/15 Paul Schenkeveld > >> On Mon, May 14, 2012 at 01:35:51AM +0800, Marcelo Araujo wrote: >> > Hi All, >> > >> > Me and a co-work are working in a new feature for ZFS, we have 2 Machi= nes >> > and 2 JBOD, every Machine are connected on those JBOD via SAS and we a= re >> > trying to make a fail-over server. Currently every each Machine has tw= o >> SAS >> > cables, each one connected in both JBOD. >> > >> > We have worked last week to figure out, how we could make the data be >> > always alive in case one JBOD dies, and let me show you my console out= put >> > ;): >> > >> > controllerA# zpool status -v araujo >> > =A0 pool: araujo >> > =A0state: ONLINE >> > =A0scan: resilvered 57K in 0h0m with 0 errors on Sat May 12 14:32:29 2= 012 >> > config: >> > >> > =A0 =A0 =A0 =A0 NAME =A0 =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM >> > =A0 =A0 =A0 =A0 araujo =A0 =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 >> > =A0 =A0 =A0 =A0 =A0 raidz1-0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 mirror-0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 da0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0= =A0 =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 da3 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0= =A0 =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 mirror-1 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 da1 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0= =A0 =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 da4 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0= =A0 =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 mirror-2 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 da2 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0= =A0 =A0 0 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 da5 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0= =A0 =A0 0 >> > >> >> Maybe a dumb question, how you you create the above setup? =A0I seem una= ble >> to create a raidz consisting of mirrors neither can I attach a second >> physical drive to an existing one in a raidz of three single drives: >> >> =A0# zpool create tank raidz1 mirror /dev/da0 /dev/da3 mirror /dev/da1 >> /dev/da4 mirror /dev/da2 /dev/da5 >> =A0invalid vdev specification: raidz1 requires at least 2 devices >> >> =A0# zpool create tank raidz1 /dev/da0 /dev/da1 /dev/da2 >> =A0# zpool attach tank /dev/da0 /dev/da3 >> =A0cannot attach /dev/da3 to /dev/da0: can only attach to mirrors and >> top-level disks >> >> =A0# zpool upgrade >> =A0This system is currently running ZFS pool version 28. >> >> =A0All pools are formatted using this version. >> >> Kind regards, >> >> Paul Schenkeveld >> > > Hey Paul, > > Yes, I'm using the latest version with code modification, it might be a n= ew > feature. > The currently ZFS doesn't support this kind of set, that was I ask, if > there is another way that I supposed to don't know and could do the same > thing. > > If it make sense, maybe, I'll put more effort to bring this kind of stuff > as a new feature. However, it is not so simple that I could made in few > days as well as have this feature only on FreeBSD, it will make the code > inconsistent between our ZFS port and Illumos-gate. > > But is interesting. > > Best Regards, > -- > Marcelo Araujo > araujo@FreeBSD.org > _______________________________________________ > 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" If you have 2 machines then your best bet would be HAST. If you are worried about data replication you can always use lagg with 2 or more interfaces. --=20 George Kontostanos Aicom telecoms ltd http://www.aisecure.net From owner-freebsd-fs@FreeBSD.ORG Wed May 16 23:52:24 2012 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 027EE106564A for ; Wed, 16 May 2012 23:52:24 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id AE5388FC16 for ; Wed, 16 May 2012 23:52:23 +0000 (UTC) Received: from conversation.bsdunix.ch (localhost [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id BEA1BBF78; Wed, 16 May 2012 23:52:16 +0000 (UTC) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by conversation.bsdunix.ch (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GOaPEpA28yaL; Wed, 16 May 2012 23:52:16 +0000 (UTC) Received: from Toms-Saftbook.local (dmhd.bsdunix.ch [82.220.17.25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTPSA id F1C88BF75; Wed, 16 May 2012 23:52:15 +0000 (UTC) Message-ID: <4FB43DAF.3020207@bsdunix.ch> Date: Thu, 17 May 2012 01:52:15 +0200 From: Tom User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Dan Nelson References: <4FB2D099.8040103@bsdunix.ch> <20120516221709.GA1933@dan.emsphone.com> In-Reply-To: <20120516221709.GA1933@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs userquota support for rquotad (nfs)? 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, 16 May 2012 23:52:24 -0000 Hi Dan Am 17.05.12 00:17, schrieb Dan Nelson: > In the last episode (May 15), Tom said: >> Hello >> >> Has someone tried or is working on an implementation to add ZFS >> userquota support to rquotad? >> >> https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/4f68f041ddcd > > Here's a simple implementation I coded up a year ago. Instead of trying to > link in libzfs on the fly, it simply popens a "zfs get" command to fetch the > user's quota info. Interessting. Did you also modify the quota.c file? Regards, Thomas From owner-freebsd-fs@FreeBSD.ORG Thu May 17 00:29:16 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D81D71065670 for ; Thu, 17 May 2012 00:29:16 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8DE998FC08 for ; Thu, 17 May 2012 00:29:16 +0000 (UTC) Received: by yenl8 with SMTP id l8so1661794yen.13 for ; Wed, 16 May 2012 17:29:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=aqnXGa4Ph6PUZwiiGhpU3wCm2+TefYCSfsL3SrThoPc=; b=iIxByRBHBzkTAp2q2dJFh6TKsi28ypldzW8GxBaybgcf+Pv7tvSm75Qfvs1o0SOFC6 vnFbRBiMQBkXds/ilEWhG3Cko5rRUJsfLUBHlxM/l4+we4KiwFecYjLXHwWP4fXgFvvV phqxFlbRG5UKtRm2MvleW/7euHXiKURGSokCtyqfVDboaW7lEE2GNmB21IJqZ3Z61GB5 3UUtv1fYyThFebEg+Q5yvcr34fEnB/wAagRWkPlzQhVlfMAf5JeaeqN2qqQTflNE+thm nOJC+NQHuFFMbCxlx0hjrtpuyB1UpflpRIuqXc6Yzh0T0aeHr9r+wJY7UUALmRzbII7g bk5w== MIME-Version: 1.0 Received: by 10.50.15.137 with SMTP id x9mr11558218igc.8.1337214555753; Wed, 16 May 2012 17:29:15 -0700 (PDT) Received: by 10.231.31.196 with HTTP; Wed, 16 May 2012 17:29:15 -0700 (PDT) In-Reply-To: References: <20120515102206.GA53750@psconsult.nl> Date: Thu, 17 May 2012 08:29:15 +0800 Message-ID: From: Marcelo Araujo To: George Kontostanos Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Mirror of Raidz for data reliability X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2012 00:29:16 -0000 George, > If you have 2 machines then your best bet would be HAST. > So, why use ETHERNET if my Machine can see both JBOD? > If you are worried about data replication you can always use lagg with > 2 or more interfaces. It is different than data replication. It is data protection. Best Regards, -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Thu May 17 02:56:55 2012 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52D21106566B for ; Thu, 17 May 2012 02:56:55 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (firebox.emsphone.com [199.67.51.15]) by mx1.freebsd.org (Postfix) with ESMTP id 1157D8FC0A for ; Thu, 17 May 2012 02:56:54 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [172.17.17.101]) by email2.allantgroup.com (8.14.4/8.14.4) with ESMTP id q4H2undl088804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 21:56:49 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.5/8.14.5) with ESMTP id q4H2unjv087297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 21:56:49 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.5/8.14.5/Submit) id q4H2unkM087296; Wed, 16 May 2012 21:56:49 -0500 (CDT) (envelope-from dan) Date: Wed, 16 May 2012 21:56:49 -0500 From: Dan Nelson To: Tom Message-ID: <20120517025649.GF45363@dan.emsphone.com> References: <4FB2D099.8040103@bsdunix.ch> <20120516221709.GA1933@dan.emsphone.com> <4FB43DAF.3020207@bsdunix.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FB43DAF.3020207@bsdunix.ch> X-OS: FreeBSD 8.3-PRERELEASE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.2 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (email2.allantgroup.com [172.17.19.78]); Wed, 16 May 2012 21:56:49 -0500 (CDT) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on email2.allantgroup.com X-Scanned-By: MIMEDefang 2.68 on 172.17.19.78 Cc: freebsd-fs@FreeBSD.org Subject: Re: zfs userquota support for rquotad (nfs)? 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, 17 May 2012 02:56:55 -0000 In the last episode (May 17), Tom said: > Am 17.05.12 00:17, schrieb Dan Nelson: > > In the last episode (May 15), Tom said: > >> Hello > >> > >> Has someone tried or is working on an implementation to add ZFS > >> userquota support to rquotad? > >> > >> https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/4f68f041ddcd > > > > Here's a simple implementation I coded up a year ago. Instead of trying > > to link in libzfs on the fly, it simply popens a "zfs get" command to > > fetch the user's quota info. > > Interessting. Did you also modify the quota.c file? Hmm... no I didn't. I forgot about that :) My usecase was for an NFS homedir server, and I never thought about the fact that /usr/bin/quota looks up local filesystems on its own. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-fs@FreeBSD.ORG Thu May 17 07:12:47 2012 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EA8E106564A; Thu, 17 May 2012 07:12:47 +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 324F28FC0C; Thu, 17 May 2012 07:12:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4H7ClT5067426; Thu, 17 May 2012 07:12:47 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4H7Cl3M067422; Thu, 17 May 2012 07:12:47 GMT (envelope-from linimon) Date: Thu, 17 May 2012 07:12:47 GMT Message-Id: <201205170712.q4H7Cl3M067422@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/167979: [ufs] DIOCGDINFO ioctl does not work on 8.2 file systems 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, 17 May 2012 07:12:47 -0000 Old Synopsis: DIOCGDINFO ioctl does not work on 8.2 file systems New Synopsis: [ufs] DIOCGDINFO ioctl does not work on 8.2 file systems Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 17 07:12:38 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=167979 From owner-freebsd-fs@FreeBSD.ORG Thu May 17 10:12:04 2012 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 40A01106568D; Thu, 17 May 2012 10:12:04 +0000 (UTC) (envelope-from gjb@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id CC5E28FC0A; Thu, 17 May 2012 10:12:00 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 360EDC4B2C; Thu, 17 May 2012 12:11:50 +0200 (CEST) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id wk-bRt3RI39U; Thu, 17 May 2012 12:11:49 +0200 (CEST) Received: from [10.0.0.93] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id 8C034C4B2A; Thu, 17 May 2012 12:11:49 +0200 (CEST) Message-ID: <4FB4EABA.702@semihalf.com> Date: Thu, 17 May 2012 14:10:34 +0200 From: Grzegorz Bernacki User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.24) Gecko/20120127 Thunderbird/3.1.16 MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-embedded@FreeBSD.org, freebsd-arm@freebsd.org Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: NAND Framework in HEAD. 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, 17 May 2012 10:12:04 -0000 Hello, I would like to annouce merging of the project/nand branch into HEAD. The purpose of this project was to create a complete environment supportng NAND Flash devices in FreeBSD. The NAND Flash environment consists of a driver framework for NAND controllers and memory chips, a NAND device simulator and a fault tolerant, log-structured file system (NANDFS), tailored to meet the unique challenges of NAND flash storage. The package includes all the tools, utilities and documentation needed to deploy this technology in custom applications. The NAND Flash environment consists of several distinct components: - NAND framework (drivers harness for NAND controllers and NAND chips) - NAND simulator (NANDsim) - NAND file system (NAND FS) - Companion tools and utilities - Documentation (manual pages) NAND FS adopts log-structured approach and some parts of its internal design are derived from the new implementation of the log-structured file system (NILFS), with some concepts rooting in the original (now legacy) BSD log-structured file system (LFS). The NAND FS has the following major features: - Hard links - Symbolic links - Case-sensitive, case-preserving - Snapshots No limit on the number of snapshots (only volume-limited) Mountable as read-only file systems Simultaneously mountable (there can be a writable mount concurrently mixed with a number of read-only snapshots) - Redundant super block - Metadata POSIX file permissions Creation timestamps Last content modification timestamps Last metadata change timestamps Checksum / ECC Additional documentation related to project can be found at: http://wiki.semihalf.com/moin.cgi/FreeBSD/NAND The NAND Flash Framework was developed by Semihalf. Juniper Networks and the FreeBSD Foundation kindly sponsored releasing the code to the FreeBSD community. regards, grzesiek From owner-freebsd-fs@FreeBSD.ORG Thu May 17 10:52:39 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA49B1065673 for ; Thu, 17 May 2012 10:52:39 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8E2F08FC14 for ; Thu, 17 May 2012 10:52:39 +0000 (UTC) Received: by vbmv11 with SMTP id v11so2077203vbm.13 for ; Thu, 17 May 2012 03:52:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0Y1L+MYLp8reKcNG4X3a273utAapH/Yg6feFXeKsPxk=; b=Ujoe5pjayK4ObKVP4wCEnxkhPi3PmpbHI+uK+un+VKKsDl0sx4uyvow+NIU5xk/YPF QIhkqUE9dtkPazQ5/nvVqxKVfDRjtEPos55zs3fdATfFPMGIEXnyF6xF+DG0CYgtlfYN QkIeYQ+RIk/ehIyfBj3eB2IVKTjiLKhrtO/t7EJjE7wMBqqTSf9cZ09/U8ATB/wh91uf b46imJfl92419GuQIQC213v+OY1qvoKGRUDVSf4dacoypZvlWRPGeO3oY64JLSue56xu zVJoxst2EVKCvH3hwo/vKQ2Qe4bXpdOYhvgSyVgCcxRNe092habnuhCSHO8JXrILiIWp /3Zg== MIME-Version: 1.0 Received: by 10.220.150.205 with SMTP id z13mr4797750vcv.19.1337251958875; Thu, 17 May 2012 03:52:38 -0700 (PDT) Received: by 10.220.8.202 with HTTP; Thu, 17 May 2012 03:52:38 -0700 (PDT) In-Reply-To: References: <20120515102206.GA53750@psconsult.nl> Date: Thu, 17 May 2012 13:52:38 +0300 Message-ID: From: George Kontostanos To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Mirror of Raidz for data reliability 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, 17 May 2012 10:52:39 -0000 On Thu, May 17, 2012 at 3:29 AM, Marcelo Araujo wrote: > George, > >> >> If you have 2 machines then your best bet would be HAST. > > > So, why use ETHERNET if my Machine can see both JBOD? I was under the impression that you are talking about 2 different physical machines. >> If you are worried about data replication you can always use lagg with >> 2 or more interfaces. > > > It is different than data replication. It is data protection. Storing the same data in 2 different locations is data protection. Regards -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net From owner-freebsd-fs@FreeBSD.ORG Thu May 17 10:56:33 2012 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 D20481065673; Thu, 17 May 2012 10:56:33 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 894ED8FC15; Thu, 17 May 2012 10:56:33 +0000 (UTC) Received: from terran.dlink.ua (unknown [192.168.10.90]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPSA id 47569C495B; Thu, 17 May 2012 13:56:27 +0300 (EEST) Date: Thu, 17 May 2012 13:56:30 +0300 From: Aleksandr Rybalko To: Grzegorz Bernacki Message-Id: <20120517135630.6ec31920.ray@dlink.ua> In-Reply-To: <4FB4EABA.702@semihalf.com> References: <4FB4EABA.702@semihalf.com> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.20.1; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-embedded@FreeBSD.org Subject: Re: NAND Framework in HEAD. 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, 17 May 2012 10:56:33 -0000 On Thu, 17 May 2012 14:10:34 +0200 Grzegorz Bernacki wrote: >> Hello, >> >> I would like to annouce merging of the project/nand branch into >> HEAD. The purpose of this project was to create a complete >> environment supportng NAND Flash devices in FreeBSD. >> >> The NAND Flash environment consists of a driver framework for NAND >> controllers and memory chips, a NAND device simulator and a fault >> tolerant, log-structured file system (NANDFS), tailored to meet the >> unique challenges of NAND flash storage. The package includes all >> the tools, utilities and documentation needed to deploy this >> technology in custom applications. >> >> The NAND Flash environment consists of several distinct components: >> - NAND framework (drivers harness for NAND controllers and NAND >> chips) >> - NAND simulator (NANDsim) >> - NAND file system (NAND FS) >> - Companion tools and utilities >> - Documentation (manual pages) >> >> NAND FS adopts log-structured approach and some parts of its >> internal design are derived from the new implementation of the >> log-structured file system (NILFS), with some concepts rooting in >> the original (now legacy) BSD log-structured file system (LFS). >> >> The NAND FS has the following major features: >> - Hard links >> - Symbolic links >> - Case-sensitive, case-preserving >> - Snapshots >> – No limit on the number of snapshots (only volume-limited) >> – Mountable as read-only file systems >> – Simultaneously mountable (there can be a writable mount >> concurrently mixed with a number of read-only snapshots) >> - Redundant super block >> - Metadata >> – POSIX file permissions >> – Creation timestamps >> – Last content modification timestamps >> – Last metadata change timestamps >> – Checksum / ECC >> >> Additional documentation related to project can be found at: >> http://wiki.semihalf.com/moin.cgi/FreeBSD/NAND >> >> The NAND Flash Framework was developed by Semihalf. Juniper Networks >> and the FreeBSD Foundation kindly sponsored releasing the code to >> the FreeBSD community. >> >> regards, >> grzesiek >> _______________________________________________ >> freebsd-embedded@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >> To unsubscribe, send any mail to >> "freebsd-embedded-unsubscribe@freebsd.org" Cool! Many thanks for that! to you Grzegorz and to whole Semihalf!!! WBW -- Alexandr Rybalko aka Alex RAY From owner-freebsd-fs@FreeBSD.ORG Thu May 17 11:17:13 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D300C1065670 for ; Thu, 17 May 2012 11:17:13 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 80A818FC14 for ; Thu, 17 May 2012 11:17:13 +0000 (UTC) Received: by vbmv11 with SMTP id v11so2098488vbm.13 for ; Thu, 17 May 2012 04:17:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=L5N6bw9W3MEcNWDlcieLL0tkocmd5s8cq38q74oZpEE=; b=Nc+woxOomBw4dkESOvLCrIe02iJtJcFbkaZ/U7IvlRHuEAfTwFt38N5rTmwGiYyx/0 ge1DWDVGrIZ2QpziwYN9XbBHQEiDJK/Mvf5KqrtLIQ9GwQHziF4yTuQhzJmbn9fDXQTb ayOXCCT035GdDIR3rCuVLZfH3T4+LOqwc0b9UpUbkIeascdCUz4Nm6R2IQ6wQBGEk4op QSicn5/btsD4ZQnTynfROchz+KOgBaQDhihNp3qikAxOlKJkNdkcOQ/BMXDEgjfS8Ft7 /vqUZYohhzxRJ7ljyuudXkzClESmozhjCnRefYiLdQ2ZJgPN5Gaz9TopxWmPXjCToZ6z XxzA== MIME-Version: 1.0 Received: by 10.52.26.240 with SMTP id o16mr3965584vdg.20.1337253432596; Thu, 17 May 2012 04:17:12 -0700 (PDT) Received: by 10.220.8.202 with HTTP; Thu, 17 May 2012 04:17:12 -0700 (PDT) In-Reply-To: References: <20120515102206.GA53750@psconsult.nl> Date: Thu, 17 May 2012 14:17:12 +0300 Message-ID: From: George Kontostanos To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Mirror of Raidz for data reliability 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, 17 May 2012 11:17:13 -0000 On Thu, May 17, 2012 at 1:52 PM, George Kontostanos wrote: > On Thu, May 17, 2012 at 3:29 AM, Marcelo Araujo wrote: >> George, >> >>> >>> If you have 2 machines then your best bet would be HAST. >> >> >> So, why use ETHERNET if my Machine can see both JBOD? > > I was under the impression that you are talking about 2 different > physical machines. > >>> If you are worried about data replication you can always use lagg with >>> 2 or more interfaces. >> >> >> It is different than data replication. It is data protection. > > Storing the same data in 2 different locations is data protection. > > Regards > Ok, after reading more carefully your first post I realized what you are trying to do. 2 Machines, 2 different controllers. Yet interconnected. So, in a way both machines would be able to see both controllers. This is very interesting but there are some implications. 1) Suppose you manage to create a mirror consisted by drives on those different controllers. If you reboot machine #1 machine#2 might panic. It is not like loosing a drive, here we are loosing a controller. 2) Both machines have to be online and the pool has to be mounted readonly on the standby! You don't want both of them to accidentally write at the same pool. 3) HAST requires tcp to work therefore it is a no go. HAST also works in the vdev level. Therefore the resources should not be online on the standby server. Good luck, this is certainly very interesting. -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net From owner-freebsd-fs@FreeBSD.ORG Thu May 17 11:32:45 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D0E3106566C for ; Thu, 17 May 2012 11:32:45 +0000 (UTC) (envelope-from nowakpl@platinum.linux.pl) Received: from platinum.linux.pl (platinum.edu.pl [81.161.192.4]) by mx1.freebsd.org (Postfix) with ESMTP id 19F378FC08 for ; Thu, 17 May 2012 11:32:44 +0000 (UTC) Received: by platinum.linux.pl (Postfix, from userid 87) id 8023547E16; Thu, 17 May 2012 13:32:38 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on platinum.linux.pl X-Spam-Level: X-Spam-Status: No, score=-1.5 required=3.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.3.2 Received: from [172.19.191.4] (unknown [83.151.38.73]) by platinum.linux.pl (Postfix) with ESMTPA id ED6F447E11 for ; Thu, 17 May 2012 13:32:36 +0200 (CEST) Message-ID: <4FB4E1CC.8030501@platinum.linux.pl> Date: Thu, 17 May 2012 13:32:28 +0200 From: Adam Nowacki User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20120515102206.GA53750@psconsult.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Mirror of Raidz for data reliability 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, 17 May 2012 11:32:45 -0000 My understanding of this setup is: - there are 2 chasis housing disks, each with a 2 port SAS expander, - there are 2 servers, each with a 2 port SAS HBA (1st port connected to 1st SAS expander, 2nd port connected to 2nd SAS expander). On 2012-05-17 13:17, George Kontostanos wrote: > On Thu, May 17, 2012 at 1:52 PM, George Kontostanos > wrote: >> On Thu, May 17, 2012 at 3:29 AM, Marcelo Araujo wrote: >>> George, >>> >>>> >>>> If you have 2 machines then your best bet would be HAST. >>> >>> >>> So, why use ETHERNET if my Machine can see both JBOD? >> >> I was under the impression that you are talking about 2 different >> physical machines. >> >>>> If you are worried about data replication you can always use lagg with >>>> 2 or more interfaces. >>> >>> >>> It is different than data replication. It is data protection. >> >> Storing the same data in 2 different locations is data protection. >> >> Regards >> > > Ok, after reading more carefully your first post I realized what you > are trying to do. > > 2 Machines, 2 different controllers. Yet interconnected. So, in a way > both machines would be able to see both controllers. > > This is very interesting but there are some implications. > > 1) Suppose you manage to create a mirror consisted by drives on those > different controllers. If you reboot machine #1 machine#2 might panic. > It is not like loosing a drive, here we are loosing a controller. > > 2) Both machines have to be online and the pool has to be mounted > readonly on the standby! You don't want both of them to accidentally > write at the same pool. > > 3) HAST requires tcp to work therefore it is a no go. HAST also works > in the vdev level. Therefore the resources should not be online on the > standby server. > > Good luck, this is certainly very interesting. > From owner-freebsd-fs@FreeBSD.ORG Thu May 17 12:15:49 2012 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 5C6081065674; Thu, 17 May 2012 12:15:49 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id C8C088FC18; Thu, 17 May 2012 12:15:48 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id F31FFC4B2C; Thu, 17 May 2012 14:15:37 +0200 (CEST) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id TvEkhdLj2Twi; Thu, 17 May 2012 14:15:37 +0200 (CEST) Received: from [10.0.0.22] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id EBF19C4B2A; Thu, 17 May 2012 14:15:36 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=utf-8 From: Rafal Jaworowski In-Reply-To: <20120517135630.6ec31920.ray@dlink.ua> Date: Thu, 17 May 2012 14:15:46 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4FB4EABA.702@semihalf.com> <20120517135630.6ec31920.ray@dlink.ua> To: Aleksandr Rybalko X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org, Grzegorz Bernacki , freebsd-arm@freebsd.org, freebsd-embedded@FreeBSD.org Subject: Re: NAND Framework in HEAD. 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, 17 May 2012 12:15:49 -0000 On 2012-05-17, at 12:56, Aleksandr Rybalko wrote: > On Thu, 17 May 2012 14:10:34 +0200 > Grzegorz Bernacki wrote: >=20 >>> Hello, >>>=20 >>> I would like to annouce merging of the project/nand branch into >>> HEAD. The purpose of this project was to create a complete >>> environment supportng NAND Flash devices in FreeBSD. >>>=20 >>> The NAND Flash environment consists of a driver framework for NAND=20= >>> controllers and memory chips, a NAND device simulator and a fault=20 >>> tolerant, log-structured file system (NANDFS), tailored to meet the=20= >>> unique challenges of NAND flash storage. The package includes all >>> the tools, utilities and documentation needed to deploy this >>> technology in custom applications. >>>=20 >>> The NAND Flash environment consists of several distinct components: >>> - NAND framework (drivers harness for NAND controllers and NAND >>> chips) >>> - NAND simulator (NANDsim) >>> - NAND file system (NAND FS) >>> - Companion tools and utilities >>> - Documentation (manual pages) >>>=20 >>> NAND FS adopts log-structured approach and some parts of its >>> internal design are derived from the new implementation of the >>> log-structured file system (NILFS), with some concepts rooting in >>> the original (now legacy) BSD log-structured file system (LFS). >>>=20 >>> The NAND FS has the following major features: >>> - Hard links >>> - Symbolic links >>> - Case-sensitive, case-preserving >>> - Snapshots >>> =E2=80=93 No limit on the number of snapshots (only = volume-limited) >>> =E2=80=93 Mountable as read-only file systems >>> =E2=80=93 Simultaneously mountable (there can be a writable = mount >>> concurrently mixed with a number of read-only snapshots) >>> - Redundant super block >>> - Metadata >>> =E2=80=93 POSIX file permissions >>> =E2=80=93 Creation timestamps >>> =E2=80=93 Last content modification timestamps >>> =E2=80=93 Last metadata change timestamps >>> =E2=80=93 Checksum / ECC >>>=20 >>> Additional documentation related to project can be found at: >>> http://wiki.semihalf.com/moin.cgi/FreeBSD/NAND >>>=20 >>> The NAND Flash Framework was developed by Semihalf. Juniper Networks >>> and the FreeBSD Foundation kindly sponsored releasing the code to >>> the FreeBSD community. >>>=20 >>> regards, >>> grzesiek >>> _______________________________________________ >>> freebsd-embedded@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >>> To unsubscribe, send any mail to >>> "freebsd-embedded-unsubscribe@freebsd.org" >=20 > Cool! Many thanks for that! to you Grzegorz and to whole Semihalf!!! This project was developed by Grzegorz Bernacki, Mateusz Guzik, =C5=81ukas= z P=C5=82achno, Jan Si=C4=99ka, =C5=81ukasz W=C3=B3jcik, with some help = from Jakub Klama and yours truly. We would like to thank Marcel = Moolenaar, Larkland Morley and Craig Rodrigues for testing, problem = reports and integration at Juniper side. Rafal From owner-freebsd-fs@FreeBSD.ORG Thu May 17 12:25:26 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 68913106564A; Thu, 17 May 2012 12:25:26 +0000 (UTC) (envelope-from rafael@lk6.com.br) Received: from mx2.lk6.com.br (mailx.lk6.com.br [189.30.46.209]) by mx1.freebsd.org (Postfix) with ESMTP id B78A18FC16; Thu, 17 May 2012 12:25:25 +0000 (UTC) Received: from mx.lk6.com.br (unknown [189.114.74.27]) by mx2.lk6.com.br (Postfix) with ESMTP id D74721CD31; Thu, 17 May 2012 09:19:13 -0300 (BRT) Received: from helix.lk6.com.br (unknown [192.168.2.11]) by mx.lk6.com.br (Postfix) with ESMTP id AA92DE4D019; Thu, 17 May 2012 09:19:11 -0300 (BRT) Received: from helix.lk6.com.br (localhost.helix.lk6.com.br [192.168.2.11]) by helix.lk6.com.br (Postfix) with ESMTP id 25A82544BC56; Thu, 17 May 2012 09:19:11 -0300 (BRT) Date: Thu, 17 May 2012 09:19:11 -0300 (BRT) From: Rafael Aquino To: Rafal Jaworowski Message-ID: <6ca0ac8e-937e-4525-ad65-f134a49b8615@helix.lk6.com.br> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Originating-IP: [192.168.2.9] X-Mailer: Zimbra 7.1.1_GA_3205 (ZimbraWebClient - FF3.0 (Win)/7.1.1_GA_3205) Cc: freebsd-fs@freebsd.org, Aleksandr Rybalko , freebsd-arm@freebsd.org, freebsd-embedded@FreeBSD.org Subject: Re: NAND Framework in HEAD. 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, 17 May 2012 12:25:26 -0000 ----- Mensagem original ----- > De: "Rafal Jaworowski" > Para: "Aleksandr Rybalko" > Cc: freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-embedded@Fre= eBSD.org > Enviadas: Quinta-feira, 17 de Maio de 2012 9:15:46 > Assunto: Re: NAND Framework in HEAD. > > > On 2012-05-17, at 12:56, Aleksandr Rybalko wrote: > > > On Thu, 17 May 2012 14:10:34 +0200 > > Grzegorz Bernacki wrote: > > > >>> Hello, > >>> > >>> I would like to annouce merging of the project/nand branch into > >>> HEAD. The purpose of this project was to create a complete > >>> environment supportng NAND Flash devices in FreeBSD. > >>> > >>> The NAND Flash environment consists of a driver framework for > >>> NAND > >>> controllers and memory chips, a NAND device simulator and a fault > >>> tolerant, log-structured file system (NANDFS), tailored to meet > >>> the > >>> unique challenges of NAND flash storage. The package includes all > >>> the tools, utilities and documentation needed to deploy this > >>> technology in custom applications. > >>> > >>> The NAND Flash environment consists of several distinct > >>> components: > >>> - NAND framework (drivers harness for NAND controllers and NAND > >>> chips) > >>> - NAND simulator (NANDsim) > >>> - NAND file system (NAND FS) > >>> - Companion tools and utilities > >>> - Documentation (manual pages) > >>> > >>> NAND FS adopts log-structured approach and some parts of its > >>> internal design are derived from the new implementation of the > >>> log-structured file system (NILFS), with some concepts rooting in > >>> the original (now legacy) BSD log-structured file system (LFS). > >>> > >>> The NAND FS has the following major features: > >>> - Hard links > >>> - Symbolic links > >>> - Case-sensitive, case-preserving > >>> - Snapshots > >>> =E2=80=93 No limit on the number of snapshots (only volume-limite= d) > >>> =E2=80=93 Mountable as read-only file systems > >>> =E2=80=93 Simultaneously mountable (there can be a writable mount= > >>> concurrently mixed with a number of read-only snapshots) > >>> - Redundant super block > >>> - Metadata > >>> =E2=80=93 POSIX file permissions > >>> =E2=80=93 Creation timestamps > >>> =E2=80=93 Last content modification timestamps > >>> =E2=80=93 Last metadata change timestamps > >>> =E2=80=93 Checksum / ECC > >>> > >>> Additional documentation related to project can be found at: > >>> http://wiki.semihalf.com/moin.cgi/FreeBSD/NAND > >>> > >>> The NAND Flash Framework was developed by Semihalf. Juniper > >>> Networks > >>> and the FreeBSD Foundation kindly sponsored releasing the code to > >>> the FreeBSD community. > >>> > >>> regards, > >>> grzesiek > >>> _______________________________________________ > >>> freebsd-embedded@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > >>> To unsubscribe, send any mail to > >>> "freebsd-embedded-unsubscribe@freebsd.org" > > > > Cool! Many thanks for that! to you Grzegorz and to whole > > Semihalf!!! > > This project was developed by Grzegorz Bernacki, Mateusz Guzik, > =C5=81ukasz P=C5=82achno, Jan Si=C4=99ka, =C5=81ukasz W=C3=B3jcik, with s= ome help from Jakub > Klama and yours truly. We would like to thank Marcel Moolenaar, > Larkland Morley and Craig Rodrigues for testing, problem reports and > integration at Juniper side. > > Rafal > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to > "freebsd-arm-unsubscribe@freebsd.org" > Hey, everybody! I bought a Sheevaplug 2 years ago and still not using it, waiting for NAND = support. Congratulations for the great work. I'm a big fan!!! Best regards! Rafael Mentz Aquino LK6 Solu=C3=A7=C3=B5es em TI Rua Domingos de Almeida, 135 sala 1102 Centro - Novo Hamburgo - RS - BRAZIL (51) 3035-6997 - 9999-7030 www.lk6.com.br From owner-freebsd-fs@FreeBSD.ORG Thu May 17 12:26:22 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B66E51065675; Thu, 17 May 2012 12:26:22 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 28B1E8FC18; Thu, 17 May 2012 12:26:21 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 9BFF6C4B3C; Thu, 17 May 2012 14:26:05 +0200 (CEST) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id ps4WStHYEzuE; Thu, 17 May 2012 14:26:04 +0200 (CEST) Received: from [10.0.0.22] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id A5454C4B2C; Thu, 17 May 2012 14:26:04 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=utf-8 From: Rafal Jaworowski In-Reply-To: <6ca0ac8e-937e-4525-ad65-f134a49b8615@helix.lk6.com.br> Date: Thu, 17 May 2012 14:26:13 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8450E177-A668-4336-AC16-3260C0683226@semihalf.com> References: <6ca0ac8e-937e-4525-ad65-f134a49b8615@helix.lk6.com.br> To: Rafael Aquino X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org, Aleksandr Rybalko , freebsd-arm@freebsd.org, freebsd-embedded@FreeBSD.org Subject: Re: NAND Framework in HEAD. 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, 17 May 2012 12:26:22 -0000 On 2012-05-17, at 14:19, Rafael Aquino wrote: >=20 > ----- Mensagem original ----- >> De: "Rafal Jaworowski" >> Para: "Aleksandr Rybalko" >> Cc: freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, = freebsd-embedded@FreeBSD.org >> Enviadas: Quinta-feira, 17 de Maio de 2012 9:15:46 >> Assunto: Re: NAND Framework in HEAD. >>=20 >>=20 >> On 2012-05-17, at 12:56, Aleksandr Rybalko wrote: >>=20 >>> On Thu, 17 May 2012 14:10:34 +0200 >>> Grzegorz Bernacki wrote: >>>=20 >>>>> Hello, >>>>>=20 >>>>> I would like to annouce merging of the project/nand branch into >>>>> HEAD. The purpose of this project was to create a complete >>>>> environment supportng NAND Flash devices in FreeBSD. >>>>>=20 >>>>> The NAND Flash environment consists of a driver framework for >>>>> NAND >>>>> controllers and memory chips, a NAND device simulator and a fault >>>>> tolerant, log-structured file system (NANDFS), tailored to meet >>>>> the >>>>> unique challenges of NAND flash storage. The package includes all >>>>> the tools, utilities and documentation needed to deploy this >>>>> technology in custom applications. >>>>>=20 >>>>> The NAND Flash environment consists of several distinct >>>>> components: >>>>> - NAND framework (drivers harness for NAND controllers and NAND >>>>> chips) >>>>> - NAND simulator (NANDsim) >>>>> - NAND file system (NAND FS) >>>>> - Companion tools and utilities >>>>> - Documentation (manual pages) >>>>>=20 >>>>> NAND FS adopts log-structured approach and some parts of its >>>>> internal design are derived from the new implementation of the >>>>> log-structured file system (NILFS), with some concepts rooting in >>>>> the original (now legacy) BSD log-structured file system (LFS). >>>>>=20 >>>>> The NAND FS has the following major features: >>>>> - Hard links >>>>> - Symbolic links >>>>> - Case-sensitive, case-preserving >>>>> - Snapshots >>>>> =E2=80=93 No limit on the number of snapshots (only = volume-limited) >>>>> =E2=80=93 Mountable as read-only file systems >>>>> =E2=80=93 Simultaneously mountable (there can be a writable = mount >>>>> concurrently mixed with a number of read-only snapshots) >>>>> - Redundant super block >>>>> - Metadata >>>>> =E2=80=93 POSIX file permissions >>>>> =E2=80=93 Creation timestamps >>>>> =E2=80=93 Last content modification timestamps >>>>> =E2=80=93 Last metadata change timestamps >>>>> =E2=80=93 Checksum / ECC >>>>>=20 >>>>> Additional documentation related to project can be found at: >>>>> http://wiki.semihalf.com/moin.cgi/FreeBSD/NAND >>>>>=20 >>>>> The NAND Flash Framework was developed by Semihalf. Juniper >>>>> Networks >>>>> and the FreeBSD Foundation kindly sponsored releasing the code to >>>>> the FreeBSD community. >>>>>=20 >>>>> regards, >>>>> grzesiek >>>>> _______________________________________________ >>>>> freebsd-embedded@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >>>>> To unsubscribe, send any mail to >>>>> "freebsd-embedded-unsubscribe@freebsd.org" >>>=20 >>> Cool! Many thanks for that! to you Grzegorz and to whole >>> Semihalf!!! >>=20 >> This project was developed by Grzegorz Bernacki, Mateusz Guzik, >> =C5=81ukasz P=C5=82achno, Jan Si=C4=99ka, =C5=81ukasz W=C3=B3jcik, = with some help from Jakub >> Klama and yours truly. We would like to thank Marcel Moolenaar, >> Larkland Morley and Craig Rodrigues for testing, problem reports and >> integration at Juniper side. >>=20 >> Rafal >>=20 >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to >> "freebsd-arm-unsubscribe@freebsd.org" >>=20 >=20 > Hey, everybody! >=20 > I bought a Sheevaplug 2 years ago and still not using it, waiting for = NAND support. > Congratulations for the great work. I'm a big fan!!! Sheevaplug (and the 88F6281 chip in general) is actually the reference, = demo implementation of the NAND controller driver in this framework. Rafal From owner-freebsd-fs@FreeBSD.ORG Thu May 17 13:05:16 2012 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 9C380106566C for ; Thu, 17 May 2012 13:05:16 +0000 (UTC) (envelope-from norman@khine.net) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 598C78FC0C for ; Thu, 17 May 2012 13:05:16 +0000 (UTC) Received: by ggnm2 with SMTP id m2so2214478ggn.13 for ; Thu, 17 May 2012 06:05:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=xDSBcEskUo/Xf5klc7YK60etp+MKR8aqobEPNcKHAx8=; b=BRc3WXfOQP1/C0Kzap+WOu4PoYG4qnDUAbqt0LP5CyCfv4jYikb31rouqAmk6ozt/T rCMchY/hvWklYjpuxbpx+pn8pHt25kaByUr5E/o+5YMx0R7PinfZRbi5aT5mD/hFx3Rx F0YOSgI98SFdNxTRImdtOujFwCu8Lyadudop521r+RgsxBFVdj4JvubiAEHmZXS9GJeJ 0WDPIEvNx45zzCalVw+QR8FHwGHP4tfO7+C0XwaZW+OUuKwb1g+9m6jk/RDd6oeQHMAE mNYAm5EXWbTuMRZmcIqAmVECo3a0rw3wCZpCT/mbduVCsokVGAIl/ADINrfS0iHe6NWz BGEA== MIME-Version: 1.0 Received: by 10.42.150.8 with SMTP id y8mr4389627icv.10.1337259915195; Thu, 17 May 2012 06:05:15 -0700 (PDT) Received: by 10.50.131.226 with HTTP; Thu, 17 May 2012 06:05:15 -0700 (PDT) Date: Thu, 17 May 2012 14:05:15 +0100 Message-ID: From: Norman Khine To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlMGnOhg6CHxHbXKVfz//4r3Zq7xiasCh4uk+ZU9ifb6snlqXryXIKxNHrc3iQzL+VTyKov Subject: Setting up ZFS on FreeBSD on 4 drives 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, 17 May 2012 13:05:16 -0000 Hello, I have a server with a total of 4 drives: # dmesg | grep ad | grep device ada0: ATA-8 SATA 2.x device ada1: ATA-8 SATA 2.x device ada2: ATA-8 SATA 3.x device ada3: ATA-8 SATA 3.x device ada0 and ada1 are 40Gb each with ada2 and ada3 being 2Tb each here are the full details: http://pastie.org/3904764 i have followed several tutorials of setting up ZFS but have a question: is it a good idea to have /var reside on the 2Tb drive and /usr on the 40Gb? here is how i set it up http://pastie.org/3925356, and on line 63 zfs create -o compression=gzip -o exec=off -o setuid=off pool0/ROOT/usr/src zfs create -o compression=gzip -o setuid=off pool0/ROOT/usr/ports zfs create -o compression=off -o exec=off -o setuid=off pool0/ROOT/usr/ports/distfiles zfs create -o compression=off -o exec=off -o setuid=off pool0/ROOT/usr/ports/packages zfs create -o compression=lzjb pool0/ROOT/usr/obj zfs create -o compression=on -o exec=on -o setuid=off pool1/ROOT/tmp zfs create -o compression=lzjb -o exec=off -o setuid=off pool1/ROOT/var/crash zfs create -o compression=off -o exec=off -o setuid=off pool1/ROOT/var/empty zfs create -o compression=lzjb -o exec=on -o setuid=off pool1/ROOT/var/tmp any advise of making this better much appreciated. -- %>>> "".join( [ {'*':'@','^':'.'}.get(c,None) or chr(97+(ord(c)-83)%26) for c in ",adym,*)&uzq^zqf" ] ) From owner-freebsd-fs@FreeBSD.ORG Thu May 17 14:08:47 2012 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 943BC1065674; Thu, 17 May 2012 14:08:47 +0000 (UTC) (envelope-from gber@freebsd.org) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 217258FC0C; Thu, 17 May 2012 14:08:47 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 05C74C4E1F; Thu, 17 May 2012 16:08:36 +0200 (CEST) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id Fugf3jlTcvWo; Thu, 17 May 2012 16:08:35 +0200 (CEST) Received: from [10.0.0.93] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPSA id 05D52C5183; Thu, 17 May 2012 16:08:35 +0200 (CEST) Message-ID: <4FB52238.6080000@freebsd.org> Date: Thu, 17 May 2012 18:07:20 +0200 From: Grzegorz Bernacki User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.24) Gecko/20120127 Thunderbird/3.1.16 MIME-Version: 1.0 To: Rafal Jaworowski References: <6ca0ac8e-937e-4525-ad65-f134a49b8615@helix.lk6.com.br> <8450E177-A668-4336-AC16-3260C0683226@semihalf.com> In-Reply-To: <8450E177-A668-4336-AC16-3260C0683226@semihalf.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Rafael Aquino , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-embedded@FreeBSD.org Subject: Re: NAND Framework in HEAD. 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, 17 May 2012 14:08:47 -0000 On 05/17/12 14:26, Rafal Jaworowski wrote: > > On 2012-05-17, at 14:19, Rafael Aquino wrote: > >> >> ----- Mensagem original ----- >>> De: "Rafal Jaworowski" >>> Para: "Aleksandr Rybalko" >>> Cc: freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-embedded@FreeBSD.org >>> Enviadas: Quinta-feira, 17 de Maio de 2012 9:15:46 >>> Assunto: Re: NAND Framework in HEAD. >>> >>> >>> On 2012-05-17, at 12:56, Aleksandr Rybalko wrote: >>> >>>> On Thu, 17 May 2012 14:10:34 +0200 >>>> Grzegorz Bernacki wrote: >>>> >>>>>> Hello, >>>>>> >>>>>> I would like to annouce merging of the project/nand branch into >>>>>> HEAD. The purpose of this project was to create a complete >>>>>> environment supportng NAND Flash devices in FreeBSD. >>>>>> >>>>>> The NAND Flash environment consists of a driver framework for >>>>>> NAND >>>>>> controllers and memory chips, a NAND device simulator and a fault >>>>>> tolerant, log-structured file system (NANDFS), tailored to meet >>>>>> the >>>>>> unique challenges of NAND flash storage. The package includes all >>>>>> the tools, utilities and documentation needed to deploy this >>>>>> technology in custom applications. >>>>>> >>>>>> The NAND Flash environment consists of several distinct >>>>>> components: >>>>>> - NAND framework (drivers harness for NAND controllers and NAND >>>>>> chips) >>>>>> - NAND simulator (NANDsim) >>>>>> - NAND file system (NAND FS) >>>>>> - Companion tools and utilities >>>>>> - Documentation (manual pages) >>>>>> >>>>>> NAND FS adopts log-structured approach and some parts of its >>>>>> internal design are derived from the new implementation of the >>>>>> log-structured file system (NILFS), with some concepts rooting in >>>>>> the original (now legacy) BSD log-structured file system (LFS). >>>>>> >>>>>> The NAND FS has the following major features: >>>>>> - Hard links >>>>>> - Symbolic links >>>>>> - Case-sensitive, case-preserving >>>>>> - Snapshots >>>>>> – No limit on the number of snapshots (only volume-limited) >>>>>> – Mountable as read-only file systems >>>>>> – Simultaneously mountable (there can be a writable mount >>>>>> concurrently mixed with a number of read-only snapshots) >>>>>> - Redundant super block >>>>>> - Metadata >>>>>> – POSIX file permissions >>>>>> – Creation timestamps >>>>>> – Last content modification timestamps >>>>>> – Last metadata change timestamps >>>>>> – Checksum / ECC >>>>>> >>>>>> Additional documentation related to project can be found at: >>>>>> http://wiki.semihalf.com/moin.cgi/FreeBSD/NAND >>>>>> >>>>>> The NAND Flash Framework was developed by Semihalf. Juniper >>>>>> Networks >>>>>> and the FreeBSD Foundation kindly sponsored releasing the code to >>>>>> the FreeBSD community. >>>>>> >>>>>> regards, >>>>>> grzesiek >>>>>> _______________________________________________ >>>>>> freebsd-embedded@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >>>>>> To unsubscribe, send any mail to >>>>>> "freebsd-embedded-unsubscribe@freebsd.org" >>>> >>>> Cool! Many thanks for that! to you Grzegorz and to whole >>>> Semihalf!!! >>> >>> This project was developed by Grzegorz Bernacki, Mateusz Guzik, >>> Łukasz Płachno, Jan Sięka, Łukasz Wójcik, with some help from Jakub >>> Klama and yours truly. We would like to thank Marcel Moolenaar, >>> Larkland Morley and Craig Rodrigues for testing, problem reports and >>> integration at Juniper side. >>> >>> Rafal >>> >>> _______________________________________________ >>> freebsd-arm@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >>> To unsubscribe, send any mail to >>> "freebsd-arm-unsubscribe@freebsd.org" >>> >> >> Hey, everybody! >> >> I bought a Sheevaplug 2 years ago and still not using it, waiting for NAND support. >> Congratulations for the great work. I'm a big fan!!! > > Sheevaplug (and the 88F6281 chip in general) is actually the reference, demo implementation of the NAND controller driver in this framework. > Hi, In the first step only platform independent code has been integrated. Platform code related to 88F6281 (like dts files, kernel configuration, localbus driver, etc) will be committed soon. Thanks for showing your interest, regards, grzesiek From owner-freebsd-fs@FreeBSD.ORG Thu May 17 20:50:13 2012 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 70C1E10657FC for ; Thu, 17 May 2012 20:50:13 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242]) by mx1.freebsd.org (Postfix) with ESMTP id 5239B8FC1C for ; Thu, 17 May 2012 20:50:13 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id q4HKo6hK000183; Thu, 17 May 2012 13:50:09 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201205172050.q4HKo6hK000183@gw.catspoiler.org> Date: Thu, 17 May 2012 13:50:06 -0700 (PDT) From: Don Lewis To: gjb@semihalf.com In-Reply-To: <4FB4EABA.702@semihalf.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Cc: freebsd-fs@FreeBSD.org Subject: Re: NAND Framework in HEAD. 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, 17 May 2012 20:50:13 -0000 On 17 May, Grzegorz Bernacki wrote: > NAND FS adopts log-structured approach and some parts of its internal > design are derived from the new implementation of the log-structured > file system (NILFS), with some concepts rooting in the original (now > legacy) BSD log-structured file system (LFS). > > The NAND FS has the following major features: > - Hard links > - Symbolic links > - Case-sensitive, case-preserving > - Snapshots > ? No limit on the number of snapshots (only volume-limited) > ? Mountable as read-only file systems > ? Simultaneously mountable (there can be a writable mount concurrently > mixed with a number of read-only snapshots) > - Redundant super block > - Metadata > ? POSIX file permissions > ? Creation timestamps > ? Last content modification timestamps > ? Last metadata change timestamps > ? Checksum / ECC Any thoughts on how well NAND FS might work on SSDs as compared to something like UFS, which isn't aware of the properties of the underlying storage? I would think that avoiding random block overwrites would help performance and device lifetime. [Cc: trimmed] From owner-freebsd-fs@FreeBSD.ORG Thu May 17 21:59:46 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79857106564A; Thu, 17 May 2012 21:59:46 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 17B7D8FC14; Thu, 17 May 2012 21:59:45 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EAItztU+DaFvO/2dsb2JhbABEhTSvHYIOBwEBBAEjVgUWDgoCAg0ZAlkGE4VJB4I5Bakxkm2BJoleFIQigRUDlVqQGoMFgTsI X-IronPort-AV: E=Sophos;i="4.75,612,1330923600"; d="scan'208";a="172355194" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 17 May 2012 17:59:38 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 05FEAB3F85; Thu, 17 May 2012 17:59:38 -0400 (EDT) Date: Thu, 17 May 2012 17:59:37 -0400 (EDT) From: Rick Macklem To: Andrew Leonard Message-ID: <1959918893.562069.1337291977972.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: Unable to set ACLs on ZFS file system over NFSv4? 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, 17 May 2012 21:59:46 -0000 Andrew Leonard wrote: > On Fri, May 11, 2012 at 7:30 PM, Rick Macklem > wrote: > > Andrew Leonard wrote: > >> On Thu, May 10, 2012 at 2:23 PM, Rick Macklem > >> > >> wrote: > >> > >> > I wrote: > >> > >> >> If you capture a packet trace from before you do the NFSv4 > >> >> mount, I > >> >> can > >> >> take a look and see what the server is saying. (Basically, at > >> >> mount > >> >> time > >> >> a reply to a Getattr should including the supported attributes > >> >> and > >> >> that > >> >> should include the ACL bit. Then the setfacl becomes a Setattr > >> >> of > >> >> the > >> >> ACL > >> >> attribute.) > >> >> # tcpdump -s 0 -w acl.pcap host > >> >> - run on the client should do it > >> >> > >> >> If you want to look at it, use wireshark. If you want me to > >> >> look, > >> >> just > >> >> email acl.pcap as an attachment. > >> >> > >> >> rick > >> >> ps: Although I suspect it is the server that isn't behaving, > >> >> please > >> >> use > >> >> the FreeBSD client for the above. > >> >> pss: I've cc'd trasz@ in case he can spot some reason why it > >> >> wouldn't > >> >> work. > >> >> > >> > Oh, and make sure "user1" isn't in more than 16 groups, because > >> > that > >> > is the > >> > limit for AUTH_SYS. (I'm not sure what the effect of user1 being > >> > in > >> > more > >> > than 16 groups would be, but might as well eliminate it as a > >> > cause.) > >> > >> Thanks, Rick - I'll send the pcap over private email, as I'm sure > >> $DAYJOB would consider it somewhat sensitive. > >> > >> Looking in wireshark, if I'm reading it correctly, I don't see > >> anything for FATTR4_ACL in any replies. On the final connection, I > >> do > >> see NFS4ERR_IO set as the status for the reply to the setattr - but > >> from Googling, my understanding is that response is supposed to > >> indicate a hard error, such as a hardware problem. > >> > > Yep, it appears that ZFS returned an error that isn't in the list of > > replies for getattr, so it got mapped to EIO (the catch all for > > error > > codes not known to NFS). > > > > I took a quick look at the ZFS code and the problem looks pretty > > obvious. ZFS replies EOPNOTSUPP to the VOP_ACLCHECK() and that's > > as far as it gets. > > > > Please try the attached patch in the server (untested, but all it > > does is go ahead > > and try the VOP_SETACL() for the case where VOP_ACLCHECK() replies > > EOPNOTSUPP) and let me know if it helps. > > It took me a little while to get a test environment set up, but with > the patch applied, ACLs can be set on the ZFS file system over NFSv4. > Just fyi, a patch has just been committed to head and will be MFC'd in a week. It is slightly different, in that it just deletes the VOP_ACLCHECK() call, but should fix the problem. (The patch applies to the NFSv4 server, not client.) Thanks for testing this, rick > Thanks, > Andy > > > Thanks for reporting this and sending the packet trace, rick > > > >> Also, I have verified that "user1" is not a member of more than 16 > >> groups, so we can rule that out - that user is in only three > >> groups. > >> > >> -Andy From owner-freebsd-fs@FreeBSD.ORG Fri May 18 01:14:32 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88A7C1065677; Fri, 18 May 2012 01:14:32 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 460428FC08; Fri, 18 May 2012 01:14:32 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q4I1A2o7004946; Thu, 17 May 2012 20:10:02 -0500 (CDT) Date: Thu, 17 May 2012 20:10:02 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Don Lewis In-Reply-To: <201205172050.q4HKo6hK000183@gw.catspoiler.org> Message-ID: References: <201205172050.q4HKo6hK000183@gw.catspoiler.org> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Thu, 17 May 2012 20:10:02 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: NAND Framework in HEAD. 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, 18 May 2012 01:14:32 -0000 On Thu, 17 May 2012, Don Lewis wrote: > > Any thoughts on how well NAND FS might work on SSDs as compared to > something like UFS, which isn't aware of the properties of the > underlying storage? I would think that avoiding random block overwrites > would help performance and device lifetime. Filesystems designed to work with raw NAND Flash take care of issues like bad block management and garbage collecting freed blocks. These are functionalities already embedded in SSDs. Even zfs avoids random block overwrites. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Fri May 18 01:20:10 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78D881065670; Fri, 18 May 2012 01:20:10 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 3B54F8FC1B; Fri, 18 May 2012 01:20:10 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q4I1K9Tw004962; Thu, 17 May 2012 20:20:09 -0500 (CDT) Date: Thu, 17 May 2012 20:20:09 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Don Lewis In-Reply-To: Message-ID: References: <201205172050.q4HKo6hK000183@gw.catspoiler.org> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Thu, 17 May 2012 20:20:09 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: NAND Framework in HEAD. 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, 18 May 2012 01:20:10 -0000 A further issue that flash filesystems take care of is that the nand flash erasure block size may not be the same size as the logical filesystem sector size (it may be much larger). In order to update an existing block, it may be necessary to read and re-write all of the other logical filesystem blocks which share the same erasure block. Again, this is something that SSDs already handle internally (since they use nand flash). Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Fri May 18 01:34:21 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E41B1065679 for ; Fri, 18 May 2012 01:34:21 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 01D318FC0C for ; Fri, 18 May 2012 01:34:20 +0000 (UTC) Received: by yenl8 with SMTP id l8so3059504yen.13 for ; Thu, 17 May 2012 18:34:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=b2q/w5rdOy9+tHTo2DzXk7DPBYdWmQy0RPgNZjqYY1A=; b=Tcryfr6HV6oH1tLAWExRjw21R+23QeicZmTAOPhvSpX2CH4TJYobkWJTl6o/waprmt YTBx84knneciLUoaJfKyUsLWDxCiVZ84UUW4c88sY+fr2IlmF2BgZWFeEt88Wa4YTsiH KVe+05aTPqcnUYAoX8QUeRRBPNI1t96NFgX5NtH6oRmhB6EF8cW9FtnntADBGWGpgYfT YhQO4PzohEL7C3QOzl7ujQIf9ROBpvRAPtmmiAveT/Sa3WF/TUP26gN9RmdtnNQe0lhr aGwIq4XbHaC1gBQmGLfLADAJkMAaAvy03ftWjnd5NUPctciZHYlCMx1G6UvNjXWuSX4q T/3g== MIME-Version: 1.0 Received: by 10.50.42.129 with SMTP id o1mr7299353igl.72.1337304859838; Thu, 17 May 2012 18:34:19 -0700 (PDT) Received: by 10.231.31.196 with HTTP; Thu, 17 May 2012 18:34:19 -0700 (PDT) In-Reply-To: References: <20120515102206.GA53750@psconsult.nl> Date: Fri, 18 May 2012 09:34:19 +0800 Message-ID: From: Marcelo Araujo To: George Kontostanos Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Mirror of Raidz for data reliability X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2012 01:34:21 -0000 2012/5/17 George Kontostanos > On Thu, May 17, 2012 at 1:52 PM, George Kontostanos > wrote: > > > Ok, after reading more carefully your first post I realized what you > are trying to do. > > 2 Machines, 2 different controllers. Yet interconnected. So, in a way > both machines would be able to see both controllers. > > This is very interesting but there are some implications. > > 1) Suppose you manage to create a mirror consisted by drives on those > different controllers. If you reboot machine #1 machine#2 might panic. > It is not like loosing a drive, here we are loosing a controller. > I don't know, why the machine#2 might panic. However, one controller will be passive and not active. > > 2) Both machines have to be online and the pool has to be mounted > readonly on the standby! You don't want both of them to accidentally > write at the same pool. > > Not no.You can use Devd to start some scripts to mount the FS in another machine or something like that. But I can't be focused only in this scenario, I believe there are much more application for it. > 3) HAST requires tcp to work therefore it is a no go. HAST also works > in the vdev level. Therefore the resources should not be online on the > standby server. > > Good luck, this is certainly very interesting. > Thanks dear George, any input and ideas is always welcome. Best Regards, -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Fri May 18 01:34:45 2012 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 3DADC1065670 for ; Fri, 18 May 2012 01:34:45 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id E3E1F8FC0C for ; Fri, 18 May 2012 01:34:44 +0000 (UTC) Received: by mail-yx0-f182.google.com with SMTP id l8so3059504yen.13 for ; Thu, 17 May 2012 18:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=OZ2Curkg0/NMuPxmd7W+EcH72WNA0y7bBeY+4/EgOEA=; b=w1f/h9RVujq9kE7mtNmey88PK7EBUkWOBkGtQZx3nWLx11pHWNriQOqjzFR8KGnwnh LNrMiJHj22/Dd4sEoCQ6CkG0DmCEBcaXeXipttgjZddSy8WSj0Q89a2iaNoS9eCx2uOL kHFJyF1djh5hh2I6wHp6HS6+rNw3fHizsHqyBckxPs6DV9IIR0Ohiu13EVxgIqkBJIFo V2SMuj4M94S6b3OXNuRILxbR7HpR3iWbxmSWhMFpE+OSBNBOhrzjUBoNI0IENL7w+Cfg Pk6bb3JnOyLLCkWlB5Qc+tI00pktFUD4Z28qUHksXgcLzTJ3RTGors9XQK3oHI5ec9Uh hp7w== MIME-Version: 1.0 Received: by 10.50.159.202 with SMTP id xe10mr7147228igb.66.1337304884102; Thu, 17 May 2012 18:34:44 -0700 (PDT) Received: by 10.231.31.196 with HTTP; Thu, 17 May 2012 18:34:44 -0700 (PDT) In-Reply-To: <4FB4E1CC.8030501@platinum.linux.pl> References: <20120515102206.GA53750@psconsult.nl> <4FB4E1CC.8030501@platinum.linux.pl> Date: Fri, 18 May 2012 09:34:44 +0800 Message-ID: From: Marcelo Araujo To: Adam Nowacki Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: Mirror of Raidz for data reliability X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: araujo@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2012 01:34:45 -0000 Dear Adam, Yes, you are right! 2012/5/17 Adam Nowacki > My understanding of this setup is: > - there are 2 chasis housing disks, each with a 2 port SAS expander, > - there are 2 servers, each with a 2 port SAS HBA (1st port connected to > 1st SAS expander, 2nd port connected to 2nd SAS expander). > > > On 2012-05-17 13:17, George Kontostanos wrote: > >> On Thu, May 17, 2012 at 1:52 PM, George Kontostanos >> wrote: >> >>> On Thu, May 17, 2012 at 3:29 AM, Marcelo Araujo>> *> wrote: >>> >>>> George, >>>> >>>> >>>>> If you have 2 machines then your best bet would be HAST. >>>>> >>>> >>>> >>>> So, why use ETHERNET if my Machine can see both JBOD? >>>> >>> >>> I was under the impression that you are talking about 2 different >>> physical machines. >>> >>> If you are worried about data replication you can always use lagg with >>>>> 2 or more interfaces. >>>>> >>>> >>>> >>>> It is different than data replication. It is data protection. >>>> >>> >>> Storing the same data in 2 different locations is data protection. >>> >>> Regards >>> >>> >> Ok, after reading more carefully your first post I realized what you >> are trying to do. >> >> 2 Machines, 2 different controllers. Yet interconnected. So, in a way >> both machines would be able to see both controllers. >> >> This is very interesting but there are some implications. >> >> 1) Suppose you manage to create a mirror consisted by drives on those >> different controllers. If you reboot machine #1 machine#2 might panic. >> It is not like loosing a drive, here we are loosing a controller. >> >> 2) Both machines have to be online and the pool has to be mounted >> readonly on the standby! You don't want both of them to accidentally >> write at the same pool. >> >> 3) HAST requires tcp to work therefore it is a no go. HAST also works >> in the vdev level. Therefore the resources should not be online on the >> standby server. >> >> Good luck, this is certainly very interesting. >> >> > ______________________________**_________________ > 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 > " > -- Marcelo Araujo araujo@FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Fri May 18 06:39:44 2012 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 CEAC5106566B for ; Fri, 18 May 2012 06:39:44 +0000 (UTC) (envelope-from toredhiddenuser@tormail.org) Received: from server2.allsitecontrol.com (server2.allsitecontrol.com [63.143.36.210]) by mx1.freebsd.org (Postfix) with ESMTP id A00B98FC0C for ; Fri, 18 May 2012 06:39:44 +0000 (UTC) Received: from spftor3.privacyfoundation.ch ([62.220.135.129]:56976 helo=internal.tormail.org) by server2.allsitecontrol.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1SVGqc-0032nO-Vw for freebsd-fs@freebsd.org; Fri, 18 May 2012 02:39:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tormail.org; s=tm; h=Message-Id:X-TorMail-User:Content-Transfer-Encoding:Content-Type:MIME-Version:To:From:Subject:Date; bh=P2vfQlr6k0qGuLwD/iZx4jT5WoBVSRYa0duDwo8uOyA=; b=QDEruzDmVBAilgSi20LIv1AhHGw1//YKGkwo6YnUPGvB2IV+ggTWuHPohSqHqW4kquACyTPs7YbODWfZV1BrrMNBRjewD/os2a2mBrDdZMOhTMwy8praE4BdBnPIGcmxBQCyNAjQbaOXLVlDU6Up63aMT41h9bRhHHDIFlsshDo=; Received: from toredhiddenuser by internal.tormail.org with local (Exim 4.63) (envelope-from ) id 1SVGpE-0001jE-Es for freebsd-fs@freebsd.org; Fri, 18 May 2012 06:38:08 +0000 Date: Fri, 18 May 2012 06:38:08 -0000 From: toredhiddenuser@tormail.org To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Importance: Normal X-TorMail-User: toredhiddenuser Message-Id: <1SVGpE-0001jE-Es@internal.tormail.org> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server2.allsitecontrol.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tormail.org X-Source: X-Source-Args: X-Source-Dir: X-Mailman-Approved-At: Fri, 18 May 2012 11:28:49 +0000 Subject: File systems 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, 18 May 2012 06:39:44 -0000 Recently saw a news about ext2 being implemented in BSD license. Does that include support the ext3 and ext4 filesystems or will they be implemented? ref: http://www.freebsd.org/doc/handbook/filesystems-linux.html Is there any way to shrink the ever-growing ZFS or UFS2 systems? Or will it be implemented in UFS3? Any ideas without re-dumping the entire file system using ufsdump? Thank You From owner-freebsd-fs@FreeBSD.ORG Fri May 18 12:10:13 2012 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 210301065676 for ; Fri, 18 May 2012 12:10:13 +0000 (UTC) (envelope-from maurizio.vairani@cloverinformatica.it) Received: from smtplq04.aruba.it (smtplq-out12.aruba.it [62.149.158.32]) by mx1.freebsd.org (Postfix) with SMTP id 4EB878FC14 for ; Fri, 18 May 2012 12:10:11 +0000 (UTC) Received: (qmail 6107 invoked by uid 89); 18 May 2012 12:10:10 -0000 Received: from unknown (HELO smtp6.aruba.it) (62.149.158.226) by smtplq04.aruba.it with SMTP; 18 May 2012 12:10:10 -0000 Received: (qmail 7667 invoked by uid 89); 18 May 2012 12:10:10 -0000 Received: from unknown (HELO clover.dyndns.biz) (info@cloverinformatica.it@151.55.85.84) by smtp6.ad.aruba.it with SMTP; 18 May 2012 12:10:10 -0000 Received: from [192.168.0.185] ([192.168.0.185]) by clover.dyndns.biz ; Fri, 18 May 2012 14:09:47 +0200 Message-ID: <4FB63C22.8010902@cloverinformatica.it> Date: Fri, 18 May 2012 14:10:10 +0200 From: Maurizio Vairani User-Agent: Mozilla/5.0 (Windows NT 4.0; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Bob Friesenhahn References: <201205172050.q4HKo6hK000183@gw.catspoiler.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: smtp6.ad.aruba.it 1.6.2 0/1000/N X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N Cc: freebsd-fs@freebsd.org Subject: Re: NAND Framework in HEAD. 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, 18 May 2012 12:10:13 -0000 On 18/05/2012 3.10, Bob Friesenhahn wrote: > On Thu, 17 May 2012, Don Lewis wrote: >> >> Any thoughts on how well NAND FS might work on SSDs as compared to >> something like UFS, which isn't aware of the properties of the >> underlying storage? I would think that avoiding random block overwrites >> would help performance and device lifetime. > > Filesystems designed to work with raw NAND Flash take care of issues > like bad block management and garbage collecting freed blocks. These > are functionalities already embedded in SSDs. > > Even zfs avoids random block overwrites. > > Bob Hi have a Root on ZFS FreeBSD 8.2 server on 3 USB Flash Disks in RAID 1 configuration. Is there any advantage using NAND FS instead of ZFS ? Thanks Maurizio From owner-freebsd-fs@FreeBSD.ORG Fri May 18 16:56:39 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9154F106566C; Fri, 18 May 2012 16:56:39 +0000 (UTC) (envelope-from trent@snakebite.org) Received: from exchange.liveoffice.com (exchla3.liveoffice.com [64.70.67.188]) by mx1.freebsd.org (Postfix) with ESMTP id 6358B8FC12; Fri, 18 May 2012 16:56:39 +0000 (UTC) Received: from EXHUB03.exchhosting.com (192.168.11.104) by exhub05.exchhosting.com (192.168.11.101) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 18 May 2012 09:55:29 -0700 Received: from EXMBX10.exchhosting.com ([fe80::9c37:32f6:a508:a44f]) by EXHUB03.exchhosting.com ([fe80::ac41:fbe5:3959:ad64%12]) with mapi; Fri, 18 May 2012 09:55:26 -0700 From: Trent Nelson To: "araujo@FreeBSD.org" Date: Fri, 18 May 2012 09:55:24 -0700 Thread-Topic: Mirror of Raidz for data reliability Thread-Index: Ac01FwX48EsTh0EbQWykJg8N2G75Hg== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.1.120420 acceptlanguage: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-fs@freebsd.org" Subject: Re: Mirror of Raidz for data reliability 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, 18 May 2012 16:56:39 -0000 Hi Marcelo,=20 On 5/17/12 9:34 PM, "Marcelo Araujo" wrote: >2012/5/17 George Kontostanos > >> On Thu, May 17, 2012 at 1:52 PM, George Kontostanos >> wrote: >> >> >> Ok, after reading more carefully your first post I realized what you >> are trying to do. >> >> 2 Machines, 2 different controllers. Yet interconnected. So, in a way >> both machines would be able to see both controllers. >> >> 2) Both machines have to be online and the pool has to be mounted >> readonly on the standby! You don't want both of them to accidentally >> write at the same pool. >> >> >Not no.You can use Devd to start some scripts to mount the FS in another >machine or something like that. >But I can't be focused only in this scenario, I believe there are much >more >application for it. I'm in a similar situation with Snakebite. I have two boxes that can see a common set of disks (via FC SAN). I'm interested in failover, but like you, I don't want to use HAST -- why duplicate data when both machines can access the disks? I came across these articles yesterday, which are pretty neat: CARP and devd on FreeBSD: http://blather.michaelwlucas.com/archives/224 Automated CARP/HAST Failover: http://blather.michaelwlucas.com/archives/241 (Both of those posts reference lots of other articles; all of which I also found to be very good reads.) The author uses CARP/devd/HAST to automate failover and rebuild. Our situation is a little different because we don't want/need to use HAST. So, my thinking is=8A because both machines can see all disks, the master could import the zpool as normal, and the slave could import it read-only. (Or not import it at all...) Then, when CARP detects that the master has failed, some script will kick in on the slave (via devd?) and re-mount the zpools read-write. (Or import them for the first time.) That approach seems like a feasible starting point to me. It'll take a bit of fiddling of course, as FreeBSD isn't really set up to utilize ZFS like that. I'm planning on having my own /etc/rc.* type scripts that manually import/load zpools, rather than using /etc/rc.conf's zfs_enable=3D"YES" (which will definitely break things). Now the only thing that confuses me about your original e-mail is with regards to adding raidz vdevs. Can I enquire what you'll actually be doing with the zpools once they're loaded? I.e. You mentioned failover; what services will you be providing (NFS? Apache?) that you want to fail over? In my case, I'd *like* to be able to offer NFS, iSCSI and FC-target-mode in such a way that if the master dies, failover to the slave is automatic and transparent. At least, that's the ideal scenario :-) It'll sure take a bit of fiddling/hacking to get that working. Regards, Trent. From owner-freebsd-fs@FreeBSD.ORG Fri May 18 17:52:28 2012 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 3025B106564A; Fri, 18 May 2012 17:52:28 +0000 (UTC) (envelope-from freebsd@knarf.de) Received: from mail.server-king.de (mail.server-king.de [IPv6:2a01:4f8:100:41a2::25]) by mx1.freebsd.org (Postfix) with ESMTP id 643F38FC08; Fri, 18 May 2012 17:52:27 +0000 (UTC) Received: from cheese.server-king.de (localhost [127.0.0.1]) by mail.server-king.de (8.14.5/8.14.5) with ESMTP id q4IHqPqL044291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 18 May 2012 19:52:25 +0200 (CEST) (envelope-from freebsd@knarf.de) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=knarf.de; s=mail.server-king.de; t=1337363546; bh=wiMJZlK6iR5T/+34ScABAPnNR4H/ko9xxr+ZXQpJjB4=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ax4giC8Revj0gp6LiJuToqVD94IhEihhi5fLtlsVjo41U5CJrlQAp+TtbuZ5ergrD rihh9wY/epi4wrrTcSsi5kqbGomIgEVWeGVI1X2e99FBdhOfAeBgZ9BNYTyB8FOHbe D1jbAFu8ZMAaAQe7rDku1l7poH3eCeDGheneSF5Q= Received: (from knarf@localhost) by cheese.server-king.de (8.14.5/8.14.5/Submit) id q4IHqPSO044290; Fri, 18 May 2012 19:52:25 +0200 (CEST) (envelope-from freebsd@knarf.de) X-Authentication-Warning: cheese.server-king.de: knarf set sender to freebsd@knarf.de using -f Date: Fri, 18 May 2012 19:52:25 +0200 From: Frank Bartels To: freebsd-fs@freebsd.org Message-ID: <20120518175225.GA4735@server-king.de> References: <4F1858FE.7020509@FreeBSD.org> <39C592E81AEC0B418EAD826FC1BBB09B25253F@mailgate> <4F1878AC.6060704@FreeBSD.org> <39C592E81AEC0B418EAD826FC1BBB09B25284B@mailgate> <4F1AC995.7050506@FreeBSD.org> <39C592E81AEC0B418EAD826FC1BBB09B255E15@mailgate> <4F1D75CD.6050000@FreeBSD.org> <39C592E81AEC0B418EAD826FC1BBB09B25607F@mailgate> <4F1DC398.3050502@FreeBSD.org> <39C592E81AEC0B418EAD826FC1BBB09B25CF08@mailgate> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <39C592E81AEC0B418EAD826FC1BBB09B25CF08@mailgate> User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mail.server-king.de [127.0.0.1]); Fri, 18 May 2012 19:52:26 +0200 (CEST) Cc: 'Andriy Gapon' Subject: Re: zpool import reboots computer 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, 18 May 2012 17:52:28 -0000 Hi freebsd-fs, I have a similar problem like Martin. It started a while ago with a broken zfs, I was no longer able to delete some files on /home/ncvs: Checking setuid files and devices: find: /home/ncvs/del/efax/Attic/pkg-comment,v: Bad file descriptor find: /home/ncvs/del/libsyncml/files: No such file or directory Two days ago the machine started rebooting every two hours, directly after syncing my local cvsup-server. So I renamed the zfs /home/ncvs to /home/ncvs.del and tried to destroy it including its snapshots. The machine crashed again and now I'm unable to import the pool. First I've seen this backtrace: https://www.server-king.de/download/DSC02742.medium.JPG Then I've added the three blocks above to vdev_mirror.c. It still crashes, but the backtrace has changed: https://www.server-king.de/download/DSC02744.medium.JPG ... calltrap zio_checksum_verify zio_execute arc_read_nolock arc_read ... This is FreeBSD 8.3-RELEASE-p1 amd64 on a Xeon X5650 with 24 GByte RAM and 12 hard disks and 2 SSDs. This is what I see with zpool import -d /dev/gpt pool: zdata id: 18141461787395278116 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: zdata ONLINE raidz2-0 ONLINE gpt/zdata1.eli ONLINE gpt/zdata0.eli ONLINE gpt/zdata2.eli ONLINE gpt/zdata3.eli ONLINE gpt/zdata5.eli ONLINE gpt/zdata4.eli ONLINE gpt/zdata6.eli ONLINE gpt/zdata8.eli ONLINE gpt/zdata9.eli ONLINE cache gpt/zcache0.eli gpt/zcache1.eli spares gpt/zdata7.eli logs mirror-1 ONLINE gpt/zlog0.eli ONLINE gpt/zlog1.eli ONLINE I have no idea why I don't see zcaches and zdata7 as ONLINE. If I use zpool import (without -d) I see dsk/gpt instead of gpt/ on these three disks: cache dsk/gpt/zcache0.eli dsk/gpt/zcache1.eli spares dsk/gpt/zdata7.eli Do you have any idea what I can do? I've tried 9.0-RELEASE (LiveCD) without success. Do you think using 8.3-STABLE or 9.0-STABLE could cure my problem? Thanks, Knarf On Wed, Jan 25, 2012 at 16:10:19 +0000, Martin Ranne wrote: > Thank you everyone who have helped me with hacking zfs. We have now been able to do an import of the pool and transfered all the data to another computer. Next step is to see if we can quickly repair the pool or just delete it and make it new again. > > We hacked the functions vdev_mirror_child_select() and vdev_mirror_io_start(). In vdev_mirror_io_start() we added the code below just after the mc pointer was set in both loops. > > if (mc->mc_vd == NULL) { > (void) printf("mc->mc_vd is NULL. Child %i\n", c); > continue; > } > > In vdev_mirror_child_select(), we added the code below just after the mc pointer was set. > > if (mc->mc_vd == NULL) { > (void) printf("mc->mc_vd is NULL. Child %i\n", c); > mc->mc_tried = 1; > mc->mc_skipped = 1; > continue; > } > > > Best regards, > > Martin Ranne > > >On 2012-01-23 21:31, Andriy Gapon wrote: > >>on 23/01/2012 20:33 Martin Ranne said the following: > >>Have done some checking and found mc->mc_vd == NULL in the function vdev_mirror_io_start() where the while-loop is. > >> > >>while (children--) { > >> mc = &mm->mm_child[c]; > >> zio_nowait(zio_vdev_child_io(zio, zio->io_bp, > >> mc->mc_vd, mc->mc_offset, zio->io_data, zio->io_size, > >> zio->io_type, zio->io_priority, 0, > >> vdev_mirror_child_done, mc)); > >> c++; > >>} > >> > >>if i set a break before it runs zio_nowait() it will still crash the kernel. > >>What can i check next for it to be able to continue? Is it possible to have it ignore the child where mc_vd is NULL? I am also looking into what more I can do to debug it (adding code to print to console as i can not use kernel dumps). > >> > >Not sure. If by "set a break" you mean inserting a break statement, try > >continue instead. > > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Fri May 18 18:36:46 2012 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 DE0A0106566B for ; Fri, 18 May 2012 18:36:46 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 953C38FC18 for ; Fri, 18 May 2012 18:36:46 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q4IIacnR009085; Fri, 18 May 2012 13:36:39 -0500 (CDT) Date: Fri, 18 May 2012 13:36:38 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Maurizio Vairani In-Reply-To: <4FB63C22.8010902@cloverinformatica.it> Message-ID: References: <201205172050.q4HKo6hK000183@gw.catspoiler.org> <4FB63C22.8010902@cloverinformatica.it> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Fri, 18 May 2012 13:36:39 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: NAND Framework in HEAD. 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, 18 May 2012 18:36:47 -0000 On Fri, 18 May 2012, Maurizio Vairani wrote: >> Bob > Hi have a Root on ZFS FreeBSD 8.2 server on 3 USB Flash Disks in RAID 1 > configuration. Is there any advantage using NAND FS instead of ZFS ? If this NAND filesystem is similar to others I am aware of (e.g. JFFS2, UBIFS), it is intended to be used directly with NAND FLASH devices (i.e. a chip). This is common for embedded type applications. USB Flash Disks are a type of SSD and are arranged as logical disk blocks. They are not suitable for use with a NAND filesystem. Regardless, the availability of a NAND filesystem will make FreeBSD much more competitive for use in embedded applications (where Linux currently dominates). Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Sat May 19 10:13:41 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09FC71065674 for ; Sat, 19 May 2012 10:13:41 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 816D58FC0C for ; Sat, 19 May 2012 10:13:40 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.5/8.14.5) with ESMTP id q4JADSlI062051 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 19 May 2012 13:13:29 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4FB77248.50709@digsys.bg> Date: Sat, 19 May 2012 13:13:28 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.4) Gecko/20120501 Thunderbird/10.0.4 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: Mirror of Raidz for data reliability 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, 19 May 2012 10:13:41 -0000 On 18.05.12 19:55, Trent Nelson wrote: > So, my thinking is=8A because both machines can see all disks, the=20 > master could import the zpool as normal, and the slave could import it = > read-only. (Or not import it at all...) The proper way of doing it is "not import it at all". ZFS is not an=20 shared filesystem. If you have the second host mount the zpool even if read-only, you only=20 guarantee that data on the pool will not be corrupted, but you cannot=20 avoid the second "read-only" host panic or otherwise crash if it tries=20 to access data which is no longer where it thinks it is, because the=20 second host doesn't have access to the primary host's in-memory metadata = about ZFS. Since ZFS is copy on write filesystem, chances are you will=20 be accessing data that is no longer valid. Refreshing the internal ZFS=20 state between two or more hosts is non-trivial (if it was, Sun would=20 have done this, as it suits their usage) and in any case performance=20 will suffer at least as much as an true networked filesystem does,=20 compared to "native" ZFS. Daniel From owner-freebsd-fs@FreeBSD.ORG Sat May 19 14:01:34 2012 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 8ECB21065676 for ; Sat, 19 May 2012 14:01:34 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5174D8FC08 for ; Sat, 19 May 2012 14:01:34 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:889:fc08:3271:d956]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 230934AC2D for ; Sat, 19 May 2012 18:01:33 +0400 (MSK) Date: Sat, 19 May 2012 18:01:26 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <10910347966.20120519180126@serebryakov.spb.ru> To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Does -CURRENT support *Plug "computers? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2012 14:01:34 -0000 Hello, Freebsd-fs. Does -CURRENT support SheevaPlug/GuruPlug/DreamPlug computers, based on Marvell ARM CPUs? -- // Black Lion AKA Lev Serebryakov From owner-freebsd-fs@FreeBSD.ORG Sat May 19 14:23:57 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F7841065674; Sat, 19 May 2012 14:23:57 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 06B9D8FC0C; Sat, 19 May 2012 14:23:56 +0000 (UTC) Received: by wibhj8 with SMTP id hj8so830093wib.13 for ; Sat, 19 May 2012 07:23:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; bh=VBxfWEYWrrb7UFlYZPJJNMkhtfvNr4T2HX3mVRTETKk=; b=ewrvUier4OviY5LnY/5sQsSUA6XJ5/boaBGYp+9LYjZoH3CmozxCla684FJwlgMgtT Y1cvlNPkMe4j1Mhzse6GpPunfbsx16tfU15geOAqMz2ev8dDpVzZ/xrxrtZ4OlZtN/pN mugtaWQv6J4BQdUignuFNv+Pvt4YIDPhzd0lKodjiRHTv6Uej5WgZc5MY47VSCTz8rdM 0R/r7JXJe1kFfeDNtWMuBp/VXmTrBCkGRdoUngpYo+m+VK+iFuYUOSOveziQJ4zjKCA3 ipm78IPvbf8Aq1JSc1hFtoPdKSLv1N1F5kUclJ05LTvql4BsQHH9a5qyrv9vYL6i4+lM YugA== Received: by 10.180.92.130 with SMTP id cm2mr10526544wib.4.1337437436059; Sat, 19 May 2012 07:23:56 -0700 (PDT) Received: from ernst.jennejohn.org (p578E0D2F.dip.t-dialin.net. [87.142.13.47]) by mx.google.com with ESMTPS id fm1sm9798072wib.10.2012.05.19.07.23.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 May 2012 07:23:55 -0700 (PDT) Date: Sat, 19 May 2012 16:23:53 +0200 From: Gary Jennejohn To: lev@FreeBSD.org Message-ID: <20120519162353.465585b1@ernst.jennejohn.org> In-Reply-To: <10910347966.20120519180126@serebryakov.spb.ru> References: <10910347966.20120519180126@serebryakov.spb.ru> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Does -CURRENT support *Plug "computers? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2012 14:23:57 -0000 On Sat, 19 May 2012 18:01:26 +0400 Lev Serebryakov wrote: > Hello, Freebsd-fs. > > Does -CURRENT support SheevaPlug/GuruPlug/DreamPlug computers, based > on Marvell ARM CPUs? > It would make more sense to ask this question on freebsd-arm. -- Gary Jennejohn From owner-freebsd-fs@FreeBSD.ORG Sat May 19 15:48:55 2012 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 558C2106566B for ; Sat, 19 May 2012 15:48:55 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 107818FC15 for ; Sat, 19 May 2012 15:48:54 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:889:fc08:3271:d956]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id D04184AC2D; Sat, 19 May 2012 19:48:53 +0400 (MSK) Date: Sat, 19 May 2012 19:48:47 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1799948761.20120519194847@serebryakov.spb.ru> To: Gary Jennejohn In-Reply-To: <20120519162353.465585b1@ernst.jennejohn.org> References: <10910347966.20120519180126@serebryakov.spb.ru> <20120519162353.465585b1@ernst.jennejohn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Does -CURRENT support *Plug "computers? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2012 15:48:55 -0000 Hello, Gary. You wrote 19 =D0=BC=D0=B0=D1=8F 2012 =D0=B3., 18:23:53: GJ> It would make more sense to ask this question on freebsd-arm. ooops, sorry, missed embedded@ :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-fs@FreeBSD.ORG Sat May 19 16:50:18 2012 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 50C1810656D1 for ; Sat, 19 May 2012 16:50:18 +0000 (UTC) (envelope-from ef@math.uni-bonn.de) Received: from ems.math.uni-bonn.de (ems.math.uni-bonn.de [131.220.132.179]) by mx1.freebsd.org (Postfix) with ESMTP id 161338FC15 for ; Sat, 19 May 2012 16:50:18 +0000 (UTC) Received: from mz4.intra.net (pD9E80152.dip0.t-ipconnect.de [217.232.1.82]) by ems.math.uni-bonn.de (Postfix) with ESMTPSA id 209E8BC9A5 for ; Sat, 19 May 2012 18:50:17 +0200 (CEST) From: =?iso-8859-1?Q?Edgar_Fu=DF?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 19 May 2012 18:50:16 +0200 Message-Id: To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: Book on FFS 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, 19 May 2012 16:50:18 -0000 Is there a book (or other documentation) about FFS giving more details = than the 4.4BSD bible? I'm writing a Perl script that takes a subset of newfs's arguments, = reads a find -ls output and computes the fragmentation/bookkeeping = overhead for that particular data set. (The intent is to find out how = much the newfs parameters actually matter in terms of overhead for that = given data set.) In the course of researching what the exact overhead for the free list, = inodes and CG heads is, I learned (from discussions on NetBSD's = tech-kern list and from reading ufs/ffs/fs.h and mkfs.c) various = "interesting" things like files that need indirect blocks not being = allocated fragments, "number of blocks" and "number of data blocks" = (i.e. fs_size and fs_dsize) being in units of fragments, not blocks. I = suspect there is way more for me to learn in this field.= From owner-freebsd-fs@FreeBSD.ORG Sat May 19 20:22:28 2012 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 CFDAC106564A; Sat, 19 May 2012 20:22:28 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id EB7FF8FC14; Sat, 19 May 2012 20:22:26 +0000 (UTC) Received: by wibhj8 with SMTP id hj8so958602wib.13 for ; Sat, 19 May 2012 13:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=CUEjzUeoM6vkublWMFBHavyot1A+2oDenbP53gZHlBU=; b=WlaPxvmzbmIppTwGpJnzIGlA8zFi3zKCVW5chP5nMAwZ/ltFinRwIhJHoDjMHiFqzh H4IasA46DDdBahqE9hR6wmKlHtRtq2xo5AOl68AP6HZf7pYd8Lb5fiFjspX/nmsIFt3V 9LpGFOzT+fmHampyd1wV4LdNZ+AHezsetdLt9AygJdahbSGMdxW4wWnVOzd5003WW6TD 2qeVB4BBGrIrmWYa3hQ5b5xv4hL1EDSVfvXVpGGy4u7MXb5W9xrLXpUY8dqBVP7+eC2G UeYaY9z1/WxMYP21AXA5GL/p78GNhcdJtdlPszwihOuV/ewabJSmIJu9C8uP6LqLmjUw PNgg== Received: by 10.180.109.229 with SMTP id hv5mr22753555wib.0.1337458945528; Sat, 19 May 2012 13:22:25 -0700 (PDT) Received: from dft-labs.eu (dft-labs.eu. [80.87.128.179]) by mx.google.com with ESMTPS id f19sm18657520wiw.11.2012.05.19.13.22.23 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 May 2012 13:22:24 -0700 (PDT) Date: Sat, 19 May 2012 22:22:13 +0200 From: Mateusz Guzik To: pjd@freebsd.org Message-ID: <20120519202213.GA17691@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: [patch] Broken RLIMIT_FSIZE handling 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: Sat, 19 May 2012 20:22:28 -0000 Hello, vn_rlimit_fsize takes uio->uio_offset and uio->uio_resid into account when determining whether given write would exceed RLIMIT_FSIZE. When APPEND flag is specified, ZFS updates uio->uio_offset to point to the end of file. But this happens after a call to vn_rlimit_fsize, so vn_rlimit_fsize check can be rendered ineffective by thread that opens some file with O_APPEND and lseeks below RLIMIT_FSIZE before calling write. This fixes the problem for me: http://student.agh.edu.pl/~mjguzik/patches/zfs-rlimit-fsize.patch Slightly modified testcase stolen from pr standards/164793: http://student.agh.edu.pl/~mjguzik/patches/writelimit.c Without the patch this testacase will just finish by producing 80000 bytes file on ZFS. On UFS it gives the following output: failed when adding 27 bytes after 59994 bytes (error: File too large) Same happens on ZFS with the patch. -- Mateusz Guzik