From owner-freebsd-fs@FreeBSD.ORG Sun Dec 7 06:37:03 2008 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 0A5D51065670 for ; Sun, 7 Dec 2008 06:37:03 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id D27118FC19 for ; Sun, 7 Dec 2008 06:37:02 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id E26571D0531; Sun, 7 Dec 2008 01:18:32 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Sun, 07 Dec 2008 01:18:32 -0500 X-Sasl-enc: BEYsYZ7FETBtOx8AVpz0jGvVIry7QuvUHkFb3CkTeKL5 1228630712 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 1C118AFB6; Sun, 7 Dec 2008 01:18:32 -0500 (EST) Message-ID: <493B6AB6.2040704@incunabulum.net> Date: Sun, 07 Dec 2008 06:18:30 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: josh.carroll@gmail.com References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com> In-Reply-To: <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Gonzalo Nemmi Subject: Re: ext2 inode size patch - RE: PR kern/124621 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 06:37:03 -0000 FYI: The ext2 IFS driver for Windows v1.11a also appears to have the inode size issue: http://www.fs-driver.org/ I was not able to mount an ext2 filesystem with 256 byte inode size using this driver. Its installer will see that the filesystem exists, that it's ext2, but whenever you try to mount, you get nothing -- a very similar failure mode to the FreeBSD ext2fs driver. Again, it sounds like the author is actively maintaining it, so it might be worth contacting him to pool resources. cheers, BMS From owner-freebsd-fs@FreeBSD.ORG Sun Dec 7 19:26:20 2008 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 5EAFB1065672 for ; Sun, 7 Dec 2008 19:26:20 +0000 (UTC) (envelope-from danielgonzalesn@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id DB87E8FC1F for ; Sun, 7 Dec 2008 19:26:19 +0000 (UTC) (envelope-from danielgonzalesn@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1051923fgb.35 for ; Sun, 07 Dec 2008 11:26:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=+dh8u8upe5ROqyY6jFe14c4jhfCwAwEo+9ZfenAJDlQ=; b=rCNsMAn5Rxzh7U8/w0IyhV6W3fvmY3+0j1K6tVKKABjCw9kFVOwcVc1c3UM7/TszS/ DtBUF+/P9delTWjvoYyg69iexhhgZKT2LGKq4o3R5hFgJec41Qtg1mY6lTBn/8nKHjFl hyxy2RcD2UP9LJ7PN2ut/ju65rJ9nijngeAO0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=w7iBQiZKbxj+3wbgjdvYA/6lLRSg5Qbwl7kzN2yQUFG2cTbjyIz4q1KD+Cr54pDgBN ac5CdCsvQULoPbaVtoLNXeWn/JLSb6trVqD0JEXBUDfAjWEdJwlMa2V5PyZnvNH59UsZ kQ44I05TACymVdQ4Hr3AVDxvxV5DUcIyIlHYo= Received: by 10.223.107.198 with SMTP id c6mr1116892fap.32.1228676666872; Sun, 07 Dec 2008 11:04:26 -0800 (PST) Received: by 10.223.109.74 with HTTP; Sun, 7 Dec 2008 11:04:26 -0800 (PST) Message-ID: <993c11f30812071104x3751b4a3g1ba39417eda68a12@mail.gmail.com> Date: Sun, 7 Dec 2008 14:04:26 -0500 From: DanielX To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Error install FreeBSD 7.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 19:26:20 -0000 hello, I had problems when trying to install FreeBSD 7.0 (amd and i386) to my dv2125nr HP Pavilion laptop and other HP Pavilion dv9700t laptop comes this error, install succeed, but I doubt it comes out that error: loading required module `pci` ACPI autoload failed - no search file or directory int=3D00000006 en=3D000000000 efl=3D00010882 eip=3D00460da8 =85.. BTX halted Thank you --=20 DanielX H. Gonzales Nu=F1ez Est. Ing. Sistemas Uni. Privada del Norte From owner-freebsd-fs@FreeBSD.ORG Mon Dec 8 09:53:23 2008 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 2FC2E106564A; Mon, 8 Dec 2008 09:53:23 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 034CC8FC0C; Mon, 8 Dec 2008 09:53:22 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id EBD111D574B; Mon, 8 Dec 2008 04:53:21 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 08 Dec 2008 04:53:21 -0500 X-Sasl-enc: rhfjXg4Yrj5X31Es0yCqqUod8Waew8NFB37cQG82go0R 1228730001 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 48DCA13183; Mon, 8 Dec 2008 04:53:21 -0500 (EST) Message-ID: <493CEE90.7050104@FreeBSD.org> Date: Mon, 08 Dec 2008 09:53:20 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.18 (X11/20081205) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> In-Reply-To: <4939133E.2000701@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 09:53:23 -0000 I have rolled a port for ext2fuse: http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar I look forward to your feedback. thanks, BMS From owner-freebsd-fs@FreeBSD.ORG Mon Dec 8 11:06:55 2008 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 9A46D1065677 for ; Mon, 8 Dec 2008 11:06:55 +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 87DA38FC12 for ; Mon, 8 Dec 2008 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB8B6tDI014251 for ; Mon, 8 Dec 2008 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB8B6t0L014247 for freebsd-fs@FreeBSD.org; Mon, 8 Dec 2008 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Dec 2008 11:06:55 GMT Message-Id: <200812081106.mB8B6t0L014247@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 11:06:55 -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/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129174 fs [nfs][zfs][panic] NFS v3 Panic when under high load ex o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129084 fs [udf] [panic] udf panic: getblk: size(67584) > MAXBSIZ f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/128633 fs [zfs] [lor] lock order reversal in zfs o kern/128514 fs [zfs] [mpt] problems with ZFS and LSILogic SAS/SATA Ad o kern/128173 fs [ext2fs] ls gives "Input/output error" on mounted ext3 o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127213 fs [tmpfs] sendfile on tmpfs data corruption o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125536 fs [ext2fs] ext 2 mounts cleanly but fails on commands li o kern/125149 fs [nfs][panic] changing into .zfs dir from nfs client ca o kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition o kern/122888 fs [zfs] zfs hang w/ prefetch on, zil off while running t o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha o bin/118249 fs mv(1): moving a directory changes its mtime o kern/116170 fs [panic] Kernel panic when mounting /tmp 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 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/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D 28 problems total. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 06:22:53 2008 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 1AB0E1065670 for ; Tue, 9 Dec 2008 06:22:53 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id E4F358FC17 for ; Tue, 9 Dec 2008 06:22:52 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: by wa-out-1112.google.com with SMTP id m34so719507wag.27 for ; Mon, 08 Dec 2008 22:22:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=K16pPVZuZFc4qmUFxwnz8QRdGVOt4ZHCscGokgCVGS4=; b=biFPpRtWQGoctERCnvpBS9/rwcjPO5PQNCLZPAZH/GRYpyD5zq4QyUV6UF5EZ/CKY+ s+UCSACWndkS1AzXgv6bM55opcfyMphhZl0B665y+r0/JYN/frYXQmVHsUCicjEc68Rv VX+E/KOMBg5UAqWcCMIBAXw1NaaAQvMVqJAVo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=ktm6ZHVXe5dOz9OMgDcl9noyZENiPPXw7mwPIW9wgkSyw95AQFHgZyvEEZmgNttjDX 2yUzKiBHkVz338J5RiT9g+N43YY08SblmO+BnBiC+iXP9jK6chMxmGWr2i5g+HrZYWfq +0zUgHL0FsdGxJ1Z5gUaP0E8hC4CbAo8YeJ+U= Received: by 10.114.81.1 with SMTP id e1mr2920761wab.212.1228802134232; Mon, 08 Dec 2008 21:55:34 -0800 (PST) Received: by 10.114.103.20 with HTTP; Mon, 8 Dec 2008 21:55:34 -0800 (PST) Message-ID: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> Date: Tue, 9 Dec 2008 00:55:34 -0500 From: "Bryan Alves" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS resize disk vdev X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 06:22:53 -0000 I'm thinking about using a hardware raid array with ZFS, using a single disk vdev zpool. I want the ability to add/remove disks to an array, and I'm still unsure of the stability of zfs as a whole. I'm looking for an easy way to resize and manage disks that are greater than 2 terabytes. If I have a single block device, /dev/da0, on my system that is represented by a zfs disk vdev, and the size of this block device grows (because the underlying hardware raid expands), will zfs correctly expand? And will it correctly expand in place? From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 06:43:58 2008 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 7BC85106564A for ; Tue, 9 Dec 2008 06:43:58 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 3C97E8FC1A for ; Tue, 9 Dec 2008 06:43:58 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id F1FB9178A7; Tue, 9 Dec 2008 17:43:55 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-18-158.lns10.syd7.internode.on.net [121.44.18.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id F0DEF1732D; Tue, 9 Dec 2008 17:43:48 +1100 (EST) Message-ID: <493E12EC.4050801@modulus.org> Date: Tue, 09 Dec 2008 17:40:44 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Bryan Alves , freebsd-fs@freebsd.org References: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> In-Reply-To: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ZFS resize disk vdev X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 06:43:58 -0000 Bryan Alves wrote: > I'm thinking about using a hardware raid array with ZFS, using a single disk > vdev zpool. I want the ability to add/remove disks to an array, and I'm > still unsure of the stability of zfs as a whole. I'm looking for an easy > way to resize and manage disks that are greater than 2 terabytes. > If I have a single block device, /dev/da0, on my system that is represented > by a zfs disk vdev, and the size of this block device grows (because the > underlying hardware raid expands), will zfs correctly expand? And will it > correctly expand in place? In theory, this works fine - I have never tried it myself. The only other way to expand a zpool is by adding more vdevs: You cannot change a vdev once it is created other than to take it from a single disk to a mirror. Sun's ZFS best practice guide states that you should avoid a single disk vdev because performance on the whole suffers and is worse than UFS. I am going to publish some benchmark figures soon to back this up, based on testing I did with a 16 disk hardware RAID6. ZFS was *alot* faster when I gave it the disks in a RAIDZ2 vdev. - Andrew From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 08:53:53 2008 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 AB44E1065672 for ; Tue, 9 Dec 2008 08:53:53 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net [70.243.84.13]) by mx1.freebsd.org (Postfix) with ESMTP id 00ABB8FC1E for ; Tue, 9 Dec 2008 08:53:52 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124]) by mail.jrv.org (8.14.3/8.13.1) with ESMTP id mB98MgQw017766; Tue, 9 Dec 2008 02:22:43 -0600 (CST) (envelope-from james-freebsd-fs2@jrv.org) Authentication-Results: mail.jrv.org; domainkeys=pass (testing) header.from=james-freebsd-fs2@jrv.org DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=NQZXmH0HhiAIWhrc5VeIkPSMmeT8rvWkYfhuhhJ/59/ERe3Oh7qJ2jzF38hergo9I 05v+sP7dWqNGE3+sGT5Zw58665cloPka87ADf/T30Dgew1Th86Bj8Q3N2pNekFuEmyp KwWFmZE/0UzcmW/I8XrXk/aoV+IN7sgS4iXI5oo= Message-ID: <493E2AD2.8070704@jrv.org> Date: Tue, 09 Dec 2008 02:22:42 -0600 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: Bryan Alves References: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> In-Reply-To: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS resize disk vdev X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 08:53:53 -0000 Bryan Alves wrote: > I'm thinking about using a hardware raid array with ZFS, using a single disk > vdev zpool. I want the ability to add/remove disks to an array, and I'm > still unsure of the stability of zfs as a whole. I'm looking for an easy > way to resize and manage disks that are greater than 2 terabytes. > > If I have a single block device, /dev/da0, on my system that is represented > by a zfs disk vdev, and the size of this block device grows (because the > underlying hardware raid expands), will zfs correctly expand? And will it > correctly expand in place? > I see no benefit to using hardware RAID for a vdev. If there is any concern over ZFS stability then you're using a filesystem you suspect on an - at best - really reliable disk: not a step forward! I think best practice is to configure the disk controller to present the disks as JBOD and let ZFS handle things: avoid fancy hardware RAID controllers altogether and use the fastest JBOD controller configuration available. Using a hardware RAID seems likely to hurt performance since the hardware RAID must issue extra reads for partial parity-stripe updates: ZFS never does in-place disk writes and rarely if ever does partial parity-stripe updates. Block allocation will suffer since the filesystem allocator can't know the geometry of the underlying storage array when laying out a file. Parity rebuilds ("resilvering") can be much faster in ZFS since only things that are different need to be recomputed when a disk is reattached to a redundant vdev (and if a disk is replaced free space need not have parity computed). And hardware RAID just adds another layer of processing to slow things down. I'm not sure how ZFS reacts to an existing disk drive suddenly becoming larger. Real disk drives don't do that and ZFS is intended to use real disks. There are some uberblocks (pool superblocks) at the end of the disk and ZFS probably won't be able to find them if the uberblocks at the front of the disk are clobbered and the "end of the disk" has moved out away from the remaining uberblocks. You can replace all of the members of a redundant vdev one-by-one with larger disks and increase the storage capacity of that vdev and hence the pool. I routinely run zpools of 4TB and 5TB, which isn't even warming up for some people. Sun has had customers with ZFS pools in the petabytes. "disks that are greater than 2 terabytes" are pocket change. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 09:58:39 2008 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 75B56106564A for ; Tue, 9 Dec 2008 09:58:39 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id EFC308FC17 for ; Tue, 9 Dec 2008 09:58:38 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L9zMO-0007fi-Fo for freebsd-fs@freebsd.org; Tue, 09 Dec 2008 09:58:32 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Dec 2008 09:58:32 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Dec 2008 09:58:32 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Tue, 09 Dec 2008 10:58:25 +0100 Lines: 58 Message-ID: References: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> <493E12EC.4050801@modulus.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7680E680A1F9AF4F9A1F69CC" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.18 (X11/20081125) In-Reply-To: <493E12EC.4050801@modulus.org> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: ZFS resize disk vdev X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 09:58:39 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7680E680A1F9AF4F9A1F69CC Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andrew Snow wrote: > Bryan Alves wrote: >> I'm thinking about using a hardware raid array with ZFS, using a >> single disk >> vdev zpool. I want the ability to add/remove disks to an array, and I= 'm >> still unsure of the stability of zfs as a whole. I'm looking for an e= asy >> way to resize and manage disks that are greater than 2 terabytes. >> If I have a single block device, /dev/da0, on my system that is >> represented >> by a zfs disk vdev, and the size of this block device grows (because t= he >> underlying hardware raid expands), will zfs correctly expand? And >> will it >> correctly expand in place? >=20 > In theory, this works fine - I have never tried it myself. The only > other way to expand a zpool is by adding more vdevs: You cannot change= > a vdev once it is created other than to take it from a single disk to a= > mirror. >=20 > Sun's ZFS best practice guide states that you should avoid a single dis= k > vdev because performance on the whole suffers and is worse than UFS. >=20 > I am going to publish some benchmark figures soon to back this up, base= d > on testing I did with a 16 disk hardware RAID6. ZFS was *alot* faster > when I gave it the disks in a RAIDZ2 vdev. You mean it was a lot faster *per disk*, right? (otherwise, it's completely expected that a large RAID array will be faster than its components). --------------enig7680E680A1F9AF4F9A1F69CC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJPkFBldnAQVacBcgRAmUcAKC84K4yUtlV8TCdG6SJla1xQbKSMACgpEk0 CTNOcJLtr1GTLyA/qLKz2W8= =xy03 -----END PGP SIGNATURE----- --------------enig7680E680A1F9AF4F9A1F69CC-- From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 12:10:35 2008 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 150E31065672 for ; Tue, 9 Dec 2008 12:10:35 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id CAD278FC08 for ; Tue, 9 Dec 2008 12:10:34 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id A9636173C9; Tue, 9 Dec 2008 23:10:32 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id A6CD917265; Tue, 9 Dec 2008 23:10:28 +1100 (EST) Message-ID: <493E6032.1060300@modulus.org> Date: Tue, 09 Dec 2008 23:10:26 +1100 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Ivan Voras , freebsd-fs@freebsd.org References: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> <493E12EC.4050801@modulus.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ZFS resize disk vdev X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 12:10:35 -0000 Ivan Voras wrote: > You mean it was a lot faster *per disk*, right? (otherwise, it's > completely expected that a large RAID array will be faster than its > components). Yeah - Software RAIDZ2 was faster than both ZFS and UFS on hardware RAID6 at sequential writing. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 13:53:50 2008 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 979E61065678 for ; Tue, 9 Dec 2008 13:53:50 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.187]) by mx1.freebsd.org (Postfix) with ESMTP id 4CC6E8FC18 for ; Tue, 9 Dec 2008 13:53:49 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by rn-out-0910.google.com with SMTP id j71so1758227rne.12 for ; Tue, 09 Dec 2008 05:53:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=BY/SoZplUP+5delFx/jwuQJZ5fzxwXQtKdB/M24NAI8=; b=A/74/Ft83cWtDFKErjaeL7e2hcGmXTozkJ5zwSs69IJp26mWyPksfaYf2+wlfFe8Zr eY5aeW/5Rui+1uMamARJFtBHOWUI91w8XFqsN88y2hpwYoBfIsKK5X8szoh/2kXUUd0b 0jUlkX/2huJG3KCo3GodV8lXWGF+fS16904Kk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=E16Ei+xk3zGv1fhaIX0PBc+VH3hhPCpOaQPKyFmifAqvNrXjkxoQCaFOYAwRDpj6ip uU1nkB3SRIrWYC/vpfpGWWA12b15tfnN3CceneRPA2igOyZsves28EpdsSiaKKNbdRuN CU1HhbeqA/8zXLvWarzw7wo/l9gG1bIyj3hTE= Received: by 10.231.16.74 with SMTP id n10mr1498iba.28.1228830829288; Tue, 09 Dec 2008 05:53:49 -0800 (PST) Received: by 10.231.16.194 with HTTP; Tue, 9 Dec 2008 05:53:49 -0800 (PST) Message-ID: <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> Date: Tue, 9 Dec 2008 14:53:49 +0100 From: "Paul B. Mahol" To: "Bruce M. Simpson" In-Reply-To: <493CEE90.7050104@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> <493CEE90.7050104@FreeBSD.org> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 13:53:50 -0000 On 12/8/08, Bruce M. Simpson wrote: > I have rolled a port for ext2fuse: > http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar Ignoring fact that is buggy, slooow and port doesnt have any cache implemented and port leaves files behind in share/doc/ext2fuse when package deleted it looks fine. -- Paul From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 14:27:44 2008 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 B56CF106564A for ; Tue, 9 Dec 2008 14:27:44 +0000 (UTC) (envelope-from chris@arnold.se) Received: from mailstore.infotropic.com (mailstore.infotropic.com [213.136.34.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0241C8FC18 for ; Tue, 9 Dec 2008 14:27:43 +0000 (UTC) (envelope-from chris@arnold.se) Received: (qmail 10796 invoked by uid 89); 9 Dec 2008 14:01:01 -0000 Received: by simscan 1.2.0 ppid: 10791, pid: 10793, t: 0.1087s scanners: attach: 1.2.0 clamav: 0.94/m: Received: from unknown (HELO ?192.168.123.35?) (chris@arnold.se@85.132.191.39) by mailstore.infotropic.com with ESMTPA; 9 Dec 2008 14:01:00 -0000 Date: Tue, 9 Dec 2008 15:01:00 +0100 (CET) From: Christopher Arnold X-X-Sender: chris@localhost To: freebsd-fs@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-message-flag: =?ISO-8859-1?Q?Outlook_isn=B4t_compliant_with_current_standards_please_install_another_mail_client!?= MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: ZFS and other filesystem semantics. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 14:27:44 -0000 Hi, i have been thinking a bit about filesytem semantics lately. Mainly about open files. Classicly if a file is open the filedescriptor continues accessing the same file regardless if it is deleted or someone did a mv and replaced it. But what happens in ZFS? * delete file in ZFS I guess this is a no brainer, standard unix way of accessing the old file. * The fs get snapshotted and file deleted Same as above i guess. * The fs gets snapshotted and later the snapshot get deleted... What happens here? Or maybe even: * The fs gets snapshotted, file deleted, then snapshot deleted. (These questions are actually just a sidestep from the issue im trying to figure out right no. But i guess they are nevertheless interesting.) The reason i have been thinking about this is that i'm implementing a remote RO filesystem with local caching. And to reduce latency i download chunks of the files and cache these chunks. I'm trying to keep the filesystem stateless, but my issue is that if the file get changed under our feet the resulting chunks would be from different files. Have anyone seen a nice solution to this issue? Does anyone have any ideas of how to implement unix like semantics over a stateless procotol without to much magic? /Chris -- http://www.arnold.se/chris/ From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 16:04:05 2008 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 484881065670 for ; Tue, 9 Dec 2008 16:04:05 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: from mail-qy0-f18.google.com (mail-qy0-f18.google.com [209.85.221.18]) by mx1.freebsd.org (Postfix) with ESMTP id EF5B68FC16 for ; Tue, 9 Dec 2008 16:04:04 +0000 (UTC) (envelope-from bryanalves@gmail.com) Received: by mail-qy0-f18.google.com with SMTP id 11so92693qyk.19 for ; Tue, 09 Dec 2008 08:04:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=C6l3CNKi1Dg0ZbjIb3bJh44wNu/g9RnTl7mciJCU64M=; b=KPLwOpWoLGEmuw7nOJd53UQXz/YOe7amNLh1769xlyTudnsswD/fMWn3EuFsna9bsx wOsnVunQb7n+Mmw3Ywi2GH+j1zX/X+XfJ5xsWuTlfOdsoYcH/95JkIlRq8lO6CUgUYGQ Ycosc9ik7pQQHKSn1AW3sZlocZZ8qkTxBahMA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=kefKtnhMEcSSu1c8oCHKT4RxMXsEczkK08Q2knLxVp5uU7PFYHLaYxFVS5EVcsD7d9 0hJ92QTxqbBfjNxQL3mJGFH3HWKZMOM+66xT2eA9hOqRfAGTJK+xrp/O74z/EnETIVvJ A0dLvFS2huQccuUD68IszzErfELS62sDxcxOY= Received: by 10.114.179.1 with SMTP id b1mr195761waf.70.1228838644105; Tue, 09 Dec 2008 08:04:04 -0800 (PST) Received: by 10.114.103.20 with HTTP; Tue, 9 Dec 2008 08:04:03 -0800 (PST) Message-ID: <92f477740812090804k102dcb62qcd893b3263da56a9@mail.gmail.com> Date: Tue, 9 Dec 2008 11:04:03 -0500 From: "Bryan Alves" To: freebsd-fs@freebsd.org In-Reply-To: <493E2AD2.8070704@jrv.org> MIME-Version: 1.0 References: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> <493E2AD2.8070704@jrv.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS resize disk vdev X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 16:04:05 -0000 On Tue, Dec 9, 2008 at 3:22 AM, James R. Van Artsdalen < james-freebsd-fs2@jrv.org> wrote: > Bryan Alves wrote: > > I'm thinking about using a hardware raid array with ZFS, using a single > disk > > vdev zpool. I want the ability to add/remove disks to an array, and I'm > > still unsure of the stability of zfs as a whole. I'm looking for an easy > > way to resize and manage disks that are greater than 2 terabytes. > > > > If I have a single block device, /dev/da0, on my system that is > represented > > by a zfs disk vdev, and the size of this block device grows (because the > > underlying hardware raid expands), will zfs correctly expand? And will > it > > correctly expand in place? > > > I see no benefit to using hardware RAID for a vdev. If there is any > concern over ZFS stability then you're using a filesystem you suspect on > an - at best - really reliable disk: not a step forward! I think best > practice is to configure the disk controller to present the disks as > JBOD and let ZFS handle things: avoid fancy hardware RAID controllers > altogether and use the fastest JBOD controller configuration available. > > Using a hardware RAID seems likely to hurt performance since the > hardware RAID must issue extra reads for partial parity-stripe updates: > ZFS never does in-place disk writes and rarely if ever does partial > parity-stripe updates. Block allocation will suffer since the > filesystem allocator can't know the geometry of the underlying storage > array when laying out a file. Parity rebuilds ("resilvering") can be > much faster in ZFS since only things that are different need to be > recomputed when a disk is reattached to a redundant vdev (and if a disk > is replaced free space need not have parity computed). And hardware > RAID just adds another layer of processing to slow things down. > > I'm not sure how ZFS reacts to an existing disk drive suddenly becoming > larger. Real disk drives don't do that and ZFS is intended to use real > disks. There are some uberblocks (pool superblocks) at the end of the > disk and ZFS probably won't be able to find them if the uberblocks at > the front of the disk are clobbered and the "end of the disk" has moved > out away from the remaining uberblocks. > > You can replace all of the members of a redundant vdev one-by-one with > larger disks and increase the storage capacity of that vdev and hence > the pool. > > I routinely run zpools of 4TB and 5TB, which isn't even warming up for > some people. Sun has had customers with ZFS pools in the petabytes. > "disks that are greater than 2 terabytes" are pocket change. My reason for wanting to use my hardware controller isn't for speed, it's for the ability to migrate in place. I'm currently using 5 750GB drives, and I would like the flexibility to be able to purchase a 6th and grow my array by 750GB in place. If I could achieve something, anything, similar in ZFS (namely, buy an amount of disks smaller than the number of total disks in the array and see a gain in storage capacity), I would use ZFS. If I could do something like take a zpool that exists of a raidz vdev of my 5 750GB drives, and then I go off and purchase 3 1.5TB new drives and create a second raidz vdev and stripe them, and have the ability to remove the vdev from the pool without data loss assuming I have enough free space, then I would be happy. Maybe I am insanely overthinking this, and the use case of wanting to tack on 1 or 2 new drives isn't worth stressing out about. I'm looking for a middle ground between keep an array as is and replace every drive in the array at once to see a tangible gain. Also I'm using the hardware raid controller because it reports which drive failed and fail LED lights up. If I can get a physical sign of which drive died (assuming I have per-drive lights) with ZFS, then that is a non-issue. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 9 16:41:55 2008 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 B5A941065670 for ; Tue, 9 Dec 2008 16:41:55 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from mail.tychl.net (unknown [IPv6:2001:470:1f01:716::1]) by mx1.freebsd.org (Postfix) with ESMTP id 85D9D8FC08 for ; Tue, 9 Dec 2008 16:41:55 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from localhost (localhost [127.0.0.1]) by mail.tychl.net (Postfix) with ESMTP id C3B091CB4D; Tue, 9 Dec 2008 11:41:31 -0500 (EST) X-Virus-Scanned: amavisd-new at tychl.net Received: from mail.tychl.net ([192.168.0.2]) by localhost (masq.tychl.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 4VQR0TlX31EC; Tue, 9 Dec 2008 11:41:30 -0500 (EST) Received: from [172.16.1.94] (unknown [172.16.1.94]) by mail.tychl.net (Postfix) with ESMTP id C1DA91CB4C; Tue, 9 Dec 2008 11:41:29 -0500 (EST) Message-ID: <493E9FB8.2090808@tychl.net> Date: Tue, 09 Dec 2008 11:41:28 -0500 From: Nick Gustas User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Bryan Alves References: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> In-Reply-To: <92f477740812082155y3365bec7v5574206dd1a98e26@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS resize disk vdev X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 16:41:55 -0000 Bryan Alves wrote: > I'm thinking about using a hardware raid array with ZFS, using a single disk > vdev zpool. I want the ability to add/remove disks to an array, and I'm > still unsure of the stability of zfs as a whole. I'm looking for an easy > way to resize and manage disks that are greater than 2 terabytes. > > If I have a single block device, /dev/da0, on my system that is represented > by a zfs disk vdev, and the size of this block device grows (because the > underlying hardware raid expands), will zfs correctly expand? And will it > correctly expand in place? > If you have ZFS on the raw da0 and not on partition, it will expand with a zpool export/import or a reboot after the hardware is done expanding the array. If you put ZFS on a partition, you'll first need to extend the partition after the expansion finishes. I have a friend running ZFS on a 24 port 3ware controller that has expanded his system from a 4 disk raid-5 to a 17 disk raid-6, 1 to 2 disks at a time. Obviously he's well past 2TB at this point. Performance isn't as good as it would be natively, but it's faster than needed and the only option at the moment. No troubles yet other than a disk failure or two, the system has been in use since Sep 2007. > zpool status pool: threeware state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM threeware ONLINE 0 0 0 da0 ONLINE 0 0 0 errors: No known data errors From owner-freebsd-fs@FreeBSD.ORG Wed Dec 10 14:46:11 2008 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 0409A1065670 for ; Wed, 10 Dec 2008 14:46:11 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id BD5408FC26 for ; Wed, 10 Dec 2008 14:46:10 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 894D76D43F; Wed, 10 Dec 2008 14:46:09 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 63A6B844B4; Wed, 10 Dec 2008 15:46:09 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Christopher Arnold References: Date: Wed, 10 Dec 2008 15:46:09 +0100 In-Reply-To: (Christopher Arnold's message of "Tue, 9 Dec 2008 15:01:00 +0100 (CET)") Message-ID: <86k5a8qea6.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS and other filesystem semantics. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 14:46:11 -0000 Christopher Arnold writes: > * The fs gets snapshotted and later the snapshot get deleted... > What happens here? Snapshots are mounted like ordinary file systems, you have to unmount them before you destroy them. Of course, you can also forcibly unmount them like you would any other file system, with the usual consequences. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Thu Dec 11 17:53:54 2008 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 7F062106564A for ; Thu, 11 Dec 2008 17:53:54 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net [IPv6:2a01:198:200:2a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 109248FC08 for ; Thu, 11 Dec 2008 17:53:53 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from roadrunner.spoerlein.net (e180183203.adsl.alicedsl.de [85.180.183.203]) by acme.spoerlein.net (8.14.2/8.14.2) with ESMTP id mBBHrp4O075265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 11 Dec 2008 18:53:52 +0100 (CET) (envelope-from uspoerlein@gmail.com) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.3/8.14.3) with ESMTP id mBBHroL4003105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 11 Dec 2008 18:53:50 +0100 (CET) (envelope-from uspoerlein@gmail.com) Received: (from uqs@localhost) by roadrunner.spoerlein.net (8.14.3/8.14.3/Submit) id mBBHro2n003104 for freebsd-fs@freebsd.org; Thu, 11 Dec 2008 18:53:50 +0100 (CET) (envelope-from uspoerlein@gmail.com) Date: Thu, 11 Dec 2008 18:53:49 +0100 From: Ulrich Spoerlein To: freebsd-fs@freebsd.org Message-ID: <20081211175349.GA2735@roadrunner.spoerlein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: ZFS backup advice X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 17:53:54 -0000 Servus, I'm looking for advice on setting up a ZFS based hard disk backup solution. Given a large set of data, with perhaps 500MB data changes per day and two 1 TB disks, which option would you prefer and why: A) Separate ZFS pools on both disk. Using zfs send|recv to transfer snapshots every 2-3 days, taking the "backup" pool offline in the time in between (to keep the disk safe from surges, etc). or B) One ZFS mirror pool across both disk, resilvering the second half every 2-3 days and then detaching it again. Right now I'm favouring option A, as I can selectively "backup" part of the pool (excluding /usr/obj for example, though it is <10% of total capacity, so not a strong point), can use compression on the backup-pool and can potentially keep more snapshots on it than on the live pool. It should also be faster than resilvering the mirror every other day. I'd use B, iff ZFS is able to "self-heal" defective sectors on one mirror half, even if it is not fully resilvered. Does anyone know if this is possible? Please keep me CC'ed. Thanks! Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-fs@FreeBSD.ORG Thu Dec 11 21:53:05 2008 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 A81441065676 for ; Thu, 11 Dec 2008 21:53:05 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityweb.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 4FE688FC1F for ; Thu, 11 Dec 2008 21:53:03 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from [127.0.0.1] ([70.88.211.149]) by portcityweb.com with MailEnable ESMTP; Thu, 11 Dec 2008 16:40:01 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <49418925.2030101@greatbaysoftware.com> Date: Thu, 11 Dec 2008 16:41:57 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: multipart/mixed; boundary="------------000602010109070101020607" X-WatchGuard-AntiVirus: part scanned. clean action=allow X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: gjournal root FS okay (with kern/128529 patch)? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2008 21:53:05 -0000 This is a multi-part message in MIME format. --------------000602010109070101020607 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow Folks, The recently discovered kern/128529 had me briefly worried, as we're planning to leverage gjournal pretty heavily with a RELENG_7 -based custom build. I've manually applied the fix (at present only in -CURRENT) to the 7.x sources can report that it appears to work well. I wanted to report that fact (as a vote for MFC) and also ask: with this fix in place does anyone have any lingering misgivings about use of gjournal for root filesystem? Our thanks to all responsible on kern/128529 and geom_journal in general. Charles -- **Charles Owens** *Great Bay Software** **|** v: *603.766.6105 *|** m: *603.866.0860 *|** f: *603.430.0713 *|** e: *cowens@GreatBaySoftware.com**** --------------000602010109070101020607-- From owner-freebsd-fs@FreeBSD.ORG Sat Dec 13 17:39:03 2008 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 910041065678 for ; Sat, 13 Dec 2008 17:39:03 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 4104A8FC21 for ; Sat, 13 Dec 2008 17:39:03 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 97049 invoked by uid 2001); 13 Dec 2008 17:39:02 -0000 Date: Sat, 13 Dec 2008 11:39:02 -0600 From: "Rick C. Petty" To: freebsd-fs@freebsd.org Message-ID: <20081213173902.GA96883@keira.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: UFS label limitations X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2008@kiwi-computer.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 17:39:03 -0000 I always found it strange that when creating or changing a UFS label, you were restricted to alphanumeric characters. I really wanted some sort of separator, so I took a look at the code. Since the checks use isalnum(3) it is possible to create labels that are not 7-bit clean, depending upon your locale. After further investigation, I can't see any reason (in geom_label or otherwise) that the characters should be restricted in such a way. I applied the attached (inline) patch and have had no troubles creating, editing, or mounting via UFS labels. The patch allows you to create labels with any characters except '/' (for obvious reasons) and should work with most locales (with the tiny exception that multibyte characters which use 0x2F in subsequent bytes should be rejected, since geom_label is locale-agnostic). Would someone mind reviewing and committing this patch? Thank you, -- Rick C. Petty --- src/sbin/newfs/newfs.c.orig 2007-03-02 14:07:59.000000000 -0600 +++ src/sbin/newfs/newfs.c 2008-12-12 19:13:19.000000000 -0600 @@ -168,11 +168,10 @@ case 'L': volumelabel = optarg; i = -1; - while (isalnum(volumelabel[++i])); - if (volumelabel[i] != '\0') { - errx(1, "bad volume label. Valid characters are alphanumerics."); - } - if (strlen(volumelabel) >= MAXVOLLEN) { + while ((ch = volumelabel[++i]) != '\0') + if (ch == '/') + errx(1, "bad volume label. \"/\" not allowed."); + if (i >= MAXVOLLEN) { errx(1, "bad volume label. Length is longer than %d.", MAXVOLLEN); } --- src/sbin/tunefs/tunefs.c.orig 2008-02-26 14:25:35.000000000 -0600 +++ src/sbin/tunefs/tunefs.c 2008-12-12 19:19:33.000000000 -0600 @@ -153,13 +153,12 @@ name = "volume label"; Lvalue = optarg; i = -1; - while (isalnum(Lvalue[++i])); - if (Lvalue[i] != '\0') { + while ((ch = Lvalue[++i]) != '\0') + if (ch == '/') errx(10, - "bad %s. Valid characters are alphanumerics.", + "bad %s. \"/\" not allowed.", name); - } - if (strlen(Lvalue) >= MAXVOLLEN) { + if (i >= MAXVOLLEN) { errx(10, "bad %s. Length is longer than %d.", name, MAXVOLLEN - 1); } From owner-freebsd-fs@FreeBSD.ORG Sat Dec 13 17:43:30 2008 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 40FBF106564A; Sat, 13 Dec 2008 17:43:30 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0F7B78FC26; Sat, 13 Dec 2008 17:43:29 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 6F2B21E6A70; Sat, 13 Dec 2008 12:43:29 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 13 Dec 2008 12:43:29 -0500 X-Sasl-enc: Dyb7IEaCqv/DJrY/agJKk4V7+1R07s91nUAWxmq0LoLq 1229190209 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id A90103A240; Sat, 13 Dec 2008 12:43:28 -0500 (EST) Message-ID: <4943F43B.4060105@incunabulum.net> Date: Sat, 13 Dec 2008 17:43:23 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.18 (X11/20081204) MIME-Version: 1.0 To: "Paul B. Mahol" References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> <493CEE90.7050104@FreeBSD.org> <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> In-Reply-To: <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, "Bruce M. Simpson" Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 17:43:30 -0000 Paul B. Mahol wrote: > On 12/8/08, Bruce M. Simpson wrote: > >> I have rolled a port for ext2fuse: >> http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar >> > > Ignoring fact that is buggy, slooow and port doesnt have any cache implemented > and port leaves files behind in share/doc/ext2fuse when package > deleted it looks fine. > Can you please relay this feedback to the authors of ext2fuse? As mentioned earlier in the thread, the ext2fuse code could benefit from UBLIO-ization. Are you or any other volunteers happy to help out here? Can you elaborate further on the files being left behind by the port? I didn't see this issue in my own testing. thank you BMS From owner-freebsd-fs@FreeBSD.ORG Sat Dec 13 18:46:11 2008 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 060AF1065673 for ; Sat, 13 Dec 2008 18:46:11 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from emh01.mail.saunalahti.fi (emh01.mail.saunalahti.fi [62.142.5.107]) by mx1.freebsd.org (Postfix) with ESMTP id B56428FC0C for ; Sat, 13 Dec 2008 18:46:10 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from saunalahti-vams (vs3-11.mail.saunalahti.fi [62.142.5.95]) by emh01-2.mail.saunalahti.fi (Postfix) with SMTP id A1DF51A9E9; Sat, 13 Dec 2008 20:31:01 +0200 (EET) Received: from emh03.mail.saunalahti.fi ([62.142.5.109]) by vs3-11.mail.saunalahti.fi ([62.142.5.95]) with SMTP (gateway) id A0046B9EC27; Sat, 13 Dec 2008 20:31:01 +0200 Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by emh03.mail.saunalahti.fi (Postfix) with SMTP id 503B5158A6F; Sat, 13 Dec 2008 20:30:59 +0200 (EET) Date: Sat, 13 Dec 2008 20:30:59 +0200 From: Jaakko Heinonen To: "Rick C. Petty" Message-ID: <20081213183058.GA20992@a91-153-125-115.elisa-laajakaista.fi> References: <20081213173902.GA96883@keira.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081213173902.GA96883@keira.kiwi-computer.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Antivirus: VAMS Cc: freebsd-fs@freebsd.org Subject: Re: UFS label limitations X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 18:46:11 -0000 Hi, On 2008-12-13, Rick C. Petty wrote: > I applied the attached (inline) patch and have had no troubles creating, > editing, or mounting via UFS labels. The patch allows you to create > labels with any characters except '/' (for obvious reasons) and should > work with most locales (with the tiny exception that multibyte characters > which use 0x2F in subsequent bytes should be rejected, since geom_label > is locale-agnostic). geom_label has problems with other characters too. The problem is that it doesn't encode characters for XML output properly. See these PRs: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/104389 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120044 This already causes problems with file systems which allow non-ASCII label names. IMO the problem should be addressed before extending allowed characters in UFS labels. -- Jaakko From owner-freebsd-fs@FreeBSD.ORG Sat Dec 13 19:23:21 2008 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 D899C1065672 for ; Sat, 13 Dec 2008 19:23:21 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 67CBB8FC1C for ; Sat, 13 Dec 2008 19:23:21 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 98002 invoked by uid 2001); 13 Dec 2008 19:23:20 -0000 Date: Sat, 13 Dec 2008 13:23:20 -0600 From: "Rick C. Petty" To: Jaakko Heinonen Message-ID: <20081213192320.GA97766@keira.kiwi-computer.com> References: <20081213173902.GA96883@keira.kiwi-computer.com> <20081213183058.GA20992@a91-153-125-115.elisa-laajakaista.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081213183058.GA20992@a91-153-125-115.elisa-laajakaista.fi> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org Subject: Re: UFS label limitations X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2008@kiwi-computer.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 19:23:21 -0000 On Sat, Dec 13, 2008 at 08:30:59PM +0200, Jaakko Heinonen wrote: > > geom_label has problems with other characters too. The problem is that > it doesn't encode characters for XML output properly. See these PRs: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/104389 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120044 > > This already causes problems with file systems which allow non-ASCII > label names. IMO the problem should be addressed before extending > allowed characters in UFS labels. Well at the very least can we allow all characters between 0x20 and 0x7e except for: "&/<>\ Why hasn't the patch from kern/104389 made it in to geom? It's been almost 20 months since any activity on it. The last patch seems pretty good, except for NUL and SOH (0x00 and 0x01), but can't you just use "&#xx;" encoding for those also? XML has its own limitations. I don't think it's worth limiting everybody else just because of this XML bug. -- Rick C. Petty From owner-freebsd-fs@FreeBSD.ORG Sat Dec 13 22:03:54 2008 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 CBDC71065672; Sat, 13 Dec 2008 22:03:54 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 467CE8FC1F; Sat, 13 Dec 2008 22:03:54 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so725379anc.13 for ; Sat, 13 Dec 2008 14:03:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=LGUxq6doJDnxefYUw+NSRuTz+HZkjBGPK7TXD/3K4+w=; b=PbzDKCnJVeOH06zl7f+4u2c0KatVvx0I25+I52jyV2c9ZZM7S4SAugMHV/M/1Uw5MJ u362QwY5RGUb8btz4Ge8tjQoXzpK0GH9jPPQyD56wGhjlpAA4qg4w4qjI2w9w3iIwSRH Hc+BVVtbElBqDeDfgiVj7/tGBLSbVSA1M7Jm0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=X8KrkbNZ/AdzLBz29JLeoj84i+8DfEqS2rRXn0071LnmomF5Qx1gNES9iQb2OVaX0d yJfp5wmlcAcAFtgHdwpgr+lZXMtqjblaEyUnQlAaebrCLMTgri+7FPGTAfKsvy6fkqNv 86iAY3uksmmS5to1T9U9l8gHIcBdC2vUgni8Q= Received: by 10.231.18.130 with SMTP id w2mr62605iba.11.1229205833060; Sat, 13 Dec 2008 14:03:53 -0800 (PST) Received: by 10.231.11.72 with HTTP; Sat, 13 Dec 2008 14:03:53 -0800 (PST) Message-ID: <3a142e750812131403p31841403ub9d5693278c74111@mail.gmail.com> Date: Sat, 13 Dec 2008 23:03:53 +0100 From: "Paul B. Mahol" To: "Bruce Simpson" In-Reply-To: <4943F43B.4060105@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> <493CEE90.7050104@FreeBSD.org> <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> <4943F43B.4060105@incunabulum.net> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, "Bruce M. Simpson" Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 22:03:54 -0000 On 12/13/08, Bruce Simpson wrote: > Paul B. Mahol wrote: >> On 12/8/08, Bruce M. Simpson wrote: >> >>> I have rolled a port for ext2fuse: >>> http://people.freebsd.org/~bms/dump/fusefs-ext2fs.tar >>> >> >> Ignoring fact that is buggy, slooow and port doesnt have any cache >> implemented >> and port leaves files behind in share/doc/ext2fuse when package >> deleted it looks fine. >> > > Can you please relay this feedback to the authors of ext2fuse? > > As mentioned earlier in the thread, the ext2fuse code could benefit from > UBLIO-ization. Are you or any other volunteers happy to help out here? Well, first higher priority would be to fix existing bugs. It would be very little gain with user cache, because it is already too much IMHO slow and adding user cache will not make it faster, but that is not port problem. > Can you elaborate further on the files being left behind by the port? I > didn't see this issue in my own testing. It install files in this way: test -z "/usr/local/share/doc/ext2fuse" || ./install-sh -c -d "/usr/local/share/doc/ext2fuse" make deinstall and pkg_delete doesnt not remove that files/dir, -- Paul