From owner-freebsd-fs@FreeBSD.ORG Sun Nov 30 01:08:48 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 C2E3D1065670 for ; Sun, 30 Nov 2008 01:08:48 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 3D37B8FC14 for ; Sun, 30 Nov 2008 01:08:47 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1294817fgb.35 for ; Sat, 29 Nov 2008 17:08:46 -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=OnLODikmHwIyh/C/uNF5siER3hpNTGHmNJ82qPdLJIc=; b=cSbHy9/+KO743PC7Ith+0mqRTNn+TVpJREX/t6SJR8zybZCi9B0pJ3sE7pfjBfoAAO 0IyrvfUkCwZoHKqdekZXX79pKMWLgb7FlG6zyiQFzX5aV3IxH+GqX8yr+ryi75TV3V0d ZglEv1Yknmq4SXDCa63hn56pSaXX6ow3ToqHg= 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=RcOvFqM0JsY9MWaXWBnVPSlmtaSJZifiTan3deNsKvjhHPALoM71US4RbhcFdlrRjs IJNCxV1n5Ixu9VqfKGHVsiyt7MxRs3Lt4m23Wy36MUbEisBU3QBoLNTy5JBZcPSvuCUQ Dp74nY9qhQs5ERB9OQN5sC8/+5T001h5b2TWA= Received: by 10.181.197.2 with SMTP id z2mr3345841bkp.100.1228007326629; Sat, 29 Nov 2008 17:08:46 -0800 (PST) Received: by 10.180.236.13 with HTTP; Sat, 29 Nov 2008 17:08:46 -0800 (PST) Message-ID: <70e8236f0811291708h7ece06dcm1bff0081b5b0fde8@mail.gmail.com> Date: Sun, 30 Nov 2008 01:08:46 +0000 From: "Joao Barros" To: "Doug Rabson" In-Reply-To: <70e8236f0811241748w41884a12la50e4e63f83a7542@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <367b2c980811191412h5e0af470k165b37edc2fc5853@mail.gmail.com> <16C31872-6A83-4FAB-AC85-213D604CDDE4@rabson.org> <367b2c980811211331v551893a8sde2231c3bc65468c@mail.gmail.com> <70e8236f0811241748w41884a12la50e4e63f83a7542@mail.gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFSBoot try and bsdlabel bootstrap code 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, 30 Nov 2008 01:08:48 -0000 On Tue, Nov 25, 2008 at 1:48 AM, Joao Barros wrote: > On Fri, Nov 21, 2008 at 9:31 PM, Olivier SMEDTS wrote: >> 2008/11/20 Doug Rabson : >>> >>> On 19 Nov 2008, at 22:12, Olivier SMEDTS wrote: >>> >>>> Hello, >>>> >>>> I want to boot off a ZFS pool (version 13) on an USB stick for testing >>>> purposes. But I'm stuck with the bsdlabel bootstrap code size... >>>> I'm using a 2 hours old CURRENT. >>>> >>>> # kldload usb2_storage_mass >>>> # kldload zfs >>>> # dd if=/dev/zero of=/dev/da0 bs=512 count=32 >>>> # fdisk -BI da0 >>>> # dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 >>>> # bsdlabel -wB -b /boot/zfsboot da0s1 >>>> bsdlabel: boot code /boot/zfsboot is wrong size >>>> >>>> Is what I'm trying to do with bsdlabel wrong ? >>>> I previously tried with the default bootstrap code but I had an >>>> (expected) "boot: Not ufs" error at boot. >>>> >>>> PS : I'm not subscribed to this list. >>> >>> The process for install zfsboot is a bit manual (and undocumented). Try >>> something like this: >>> >>> # dd if=/boot/zfsboot of=/dev/da0s1 count=1 >>> # dd if=/boot/zfsboot of=/dev/ds0s1 skip=1 seek=1024 >>> >>>Alternatively, you might try using the brand new support for GPT that I committed yesterday: >>> >>> # gpt create -f da0 >>> # gpt boot -b /boot/pmbr -g /boot/gptzfsboot da0 >>> # gpt add -t freebsd-zfs da0 >>> # zpool create mypool da0p2 >> >> It works ! >> >> Now I'm stuck at loader(8) prompt. > > That's a me too. > > I tried this under vmware with LOADER_ZFS_SUPPORT=yes on make.conf: > # gpart create -s gpt ad0 > # gpart add -b 34 -s 128 -t freebsd-boot ad0 > ad0p1 added > # gpart add -b 162 -s 15078327 -t freebsd-zfs ad0 > ad0p2 added > # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 > # zpool create tank ad0p2 > # zpool set bootfs = tank tank > > lsdev on loader shows: > cd devices: > disk devices: > disk0: BIOS drive c: > disk0p1: FreeBSD boot > disk0p2: FreeBSD ZFS > pxe devices: > zfs devices: > > Any hints? > I'm trying to figure out why loader doesn't see my zfs pool and here's what I got: FreeBSD/i386 boot Default: tank:/boot/loader boot: status pool: tank config: NAME STATE tank ONLINE ad0p2 ONLINE I added some printfs on loader\main.c: guid = kargs->zfspool; unit = zfs_guid_to_unit(guid); if (unit >= 0) { sprintf(devname, "zfs%d", unit); setenv("currdev", devname, 1); } and guid returns the correct guid for my pool but unit returns -1 which by looking at zfs_guid_to_unit means something is not right. Any pointers Doug? -- Joao Barros From owner-freebsd-fs@FreeBSD.ORG Sun Nov 30 09:05:18 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 856E01065672 for ; Sun, 30 Nov 2008 09:05:18 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from itchy.rabson.org (unknown [IPv6:2002:50b1:e8f2:1::143]) by mx1.freebsd.org (Postfix) with ESMTP id 039308FC14 for ; Sun, 30 Nov 2008 09:05:18 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from [IPv6:2001:470:909f:1:21b:63ff:feb8:5abc] (unknown [IPv6:2001:470:909f:1:21b:63ff:feb8:5abc]) by itchy.rabson.org (Postfix) with ESMTP id 9F1023F9F; Sun, 30 Nov 2008 09:05:16 +0000 (GMT) Message-Id: From: Doug Rabson To: "Joao Barros" In-Reply-To: <70e8236f0811291708h7ece06dcm1bff0081b5b0fde8@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Sun, 30 Nov 2008 09:05:16 +0000 References: <367b2c980811191412h5e0af470k165b37edc2fc5853@mail.gmail.com> <16C31872-6A83-4FAB-AC85-213D604CDDE4@rabson.org> <367b2c980811211331v551893a8sde2231c3bc65468c@mail.gmail.com> <70e8236f0811241748w41884a12la50e4e63f83a7542@mail.gmail.com> <70e8236f0811291708h7ece06dcm1bff0081b5b0fde8@mail.gmail.com> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-fs@freebsd.org Subject: Re: ZFSBoot try and bsdlabel bootstrap code 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, 30 Nov 2008 09:05:18 -0000 On 30 Nov 2008, at 01:08, Joao Barros wrote: > On Tue, Nov 25, 2008 at 1:48 AM, Joao Barros > wrote: >> On Fri, Nov 21, 2008 at 9:31 PM, Olivier SMEDTS >> wrote: >>> 2008/11/20 Doug Rabson : >>>> >>>> On 19 Nov 2008, at 22:12, Olivier SMEDTS wrote: >>>> >>>>> Hello, >>>>> >>>>> I want to boot off a ZFS pool (version 13) on an USB stick for >>>>> testing >>>>> purposes. But I'm stuck with the bsdlabel bootstrap code size... >>>>> I'm using a 2 hours old CURRENT. >>>>> >>>>> # kldload usb2_storage_mass >>>>> # kldload zfs >>>>> # dd if=/dev/zero of=/dev/da0 bs=512 count=32 >>>>> # fdisk -BI da0 >>>>> # dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 >>>>> # bsdlabel -wB -b /boot/zfsboot da0s1 >>>>> bsdlabel: boot code /boot/zfsboot is wrong size >>>>> >>>>> Is what I'm trying to do with bsdlabel wrong ? >>>>> I previously tried with the default bootstrap code but I had an >>>>> (expected) "boot: Not ufs" error at boot. >>>>> >>>>> PS : I'm not subscribed to this list. >>>> >>>> The process for install zfsboot is a bit manual (and >>>> undocumented). Try >>>> something like this: >>>> >>>> # dd if=/boot/zfsboot of=/dev/da0s1 count=1 >>>> # dd if=/boot/zfsboot of=/dev/ds0s1 skip=1 seek=1024 >>>> >>>> Alternatively, you might try using the brand new support for GPT >>>> that I committed yesterday: >>>> >>>> # gpt create -f da0 >>>> # gpt boot -b /boot/pmbr -g /boot/gptzfsboot da0 >>>> # gpt add -t freebsd-zfs da0 >>>> # zpool create mypool da0p2 >>> >>> It works ! >>> >>> Now I'm stuck at loader(8) prompt. >> >> That's a me too. >> >> I tried this under vmware with LOADER_ZFS_SUPPORT=yes on make.conf: >> # gpart create -s gpt ad0 >> # gpart add -b 34 -s 128 -t freebsd-boot ad0 >> ad0p1 added >> # gpart add -b 162 -s 15078327 -t freebsd-zfs ad0 >> ad0p2 added >> # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 >> # zpool create tank ad0p2 >> # zpool set bootfs = tank tank >> >> lsdev on loader shows: >> cd devices: >> disk devices: >> disk0: BIOS drive c: >> disk0p1: FreeBSD boot >> disk0p2: FreeBSD ZFS >> pxe devices: >> zfs devices: >> >> Any hints? >> > > > I'm trying to figure out why loader doesn't see my zfs pool and here's > what I got: > > FreeBSD/i386 boot > Default: tank:/boot/loader > boot: status pool: tank > config: > NAME STATE > tank ONLINE > ad0p2 ONLINE > > I added some printfs on loader\main.c: > > guid = kargs->zfspool; > unit = zfs_guid_to_unit(guid); > if (unit >= 0) { > sprintf(devname, "zfs%d", unit); > setenv("currdev", devname, 1); > } > > and guid returns the correct guid for my pool but unit returns -1 > which by looking at zfs_guid_to_unit means something is not right. > > Any pointers Doug? It looks like loader didn't manage to find the pool for some reason. This probing process happens in sys/boot/zfs/zfs.c in the function zfs_dev_init(). Its supposed to taste all the available disks and partitions for the presence of a ZFS pool. The actual tasting process happens in vdev_probe(). From owner-freebsd-fs@FreeBSD.ORG Mon Dec 1 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 49AD91065675 for ; Mon, 1 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 359198FC27 for ; Mon, 1 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 mB1B6tSF052538 for ; Mon, 1 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 mB1B6s9N052534 for freebsd-fs@FreeBSD.org; Mon, 1 Dec 2008 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Dec 2008 11:06:54 GMT Message-Id: <200812011106.mB1B6s9N052534@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, 01 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 Mon Dec 1 13:57:38 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 BF26B1065676 for ; Mon, 1 Dec 2008 13:57:38 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from sorbesgroup.com (mail.sorbesgroup.com [217.159.241.118]) by mx1.freebsd.org (Postfix) with ESMTP id 780DB8FC0C for ; Mon, 1 Dec 2008 13:57:38 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from localhost (localhost.localdomain [127.0.0.1]) by sorbesgroup.com (Postfix) with ESMTP id 309B23C50367 for ; Mon, 1 Dec 2008 15:57:33 +0200 (EET) Received: from sorbesgroup.com ([127.0.0.1]) by localhost (sorbesgroup.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21806-02 for ; Mon, 1 Dec 2008 15:57:33 +0200 (EET) Received: from [192.168.0.80] (andrei [192.168.0.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sorbesgroup.com (Postfix) with ESMTP id 0829D3C50340 for ; Mon, 1 Dec 2008 15:57:32 +0200 (EET) Message-ID: <4933ED59.5070802@bsd.ee> Date: Mon, 01 Dec 2008 15:57:45 +0200 From: Andrei Kolu User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at localhost Cc: Subject: Disklabel Editor strange labeling 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, 01 Dec 2008 13:57:38 -0000 Hi, here is my disklabel editor "screenshot"- from where it got ad14cs1 partition name? When I created it then it was named ad14s1... --------------------------------------------------------------------------- FreeBSD Disklabel Editor Disk: ad14 Partition name: ad14cs1 Free: 293041602 blocks (139GB) Disk: ad18 Partition name: ad18s1 Free: 293041602 blocks (139GB) --------------------------------------------------------------------------- When I trie to create partition on this slice then I got error message: "Error mounting /dev/ad14cs1d on /tank/bootdir : No such file or directory" After I close sysinstall and restart it then partition disappear... --------------------------------------------------------------------------- Disk name: ad14 FDISK Partition Editor DISK Geometry: 18241 cyls/255 heads/63 sectors = 293041665 sectors (143086MB) Offset Size(ST) End Name PType Desc Subtype Flags 0 293046768 293046767 - 12 unused 0 --------------------------------------------------------------------------- FreeBSD testiserver 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Mon Dec 1 12:13:41 EET 2008 root@testiserver:/usr/obj/usr/src/sys/KERNEL amd64 From owner-freebsd-fs@FreeBSD.ORG Tue Dec 2 10:16:04 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 B4FA81065676 for ; Tue, 2 Dec 2008 10:16:04 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from sorbesgroup.com (mail.sorbesgroup.com [217.159.241.118]) by mx1.freebsd.org (Postfix) with ESMTP id 7572E8FC08 for ; Tue, 2 Dec 2008 10:16:04 +0000 (UTC) (envelope-from antik@bsd.ee) Received: from localhost (localhost.localdomain [127.0.0.1]) by sorbesgroup.com (Postfix) with ESMTP id 2EF813C506D6 for ; Tue, 2 Dec 2008 12:15:49 +0200 (EET) Received: from sorbesgroup.com ([127.0.0.1]) by localhost (sorbesgroup.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03442-09 for ; Tue, 2 Dec 2008 12:15:49 +0200 (EET) Received: from [192.168.0.80] (andrei [192.168.0.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sorbesgroup.com (Postfix) with ESMTP id E3F483C506D4 for ; Tue, 2 Dec 2008 12:15:48 +0200 (EET) Message-ID: <49350AE0.70408@bsd.ee> Date: Tue, 02 Dec 2008 12:16:00 +0200 From: Andrei Kolu User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org References: <4933ED59.5070802@bsd.ee> In-Reply-To: <4933ED59.5070802@bsd.ee> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at localhost Cc: Subject: Re: Disklabel Editor strange labeling 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, 02 Dec 2008 10:16:04 -0000 Andrei Kolu wrote: > Hi, > > here is my disklabel editor "screenshot"- from where it got ad14cs1 > partition name? When I created it then it was named ad14s1... > --------------------------------------------------------------------------- > > FreeBSD Disklabel Editor > > Disk: ad14 Partition name: ad14cs1 Free: 293041602 blocks (139GB) > Disk: ad18 Partition name: ad18s1 Free: 293041602 blocks (139GB) > --------------------------------------------------------------------------- > > > When I trie to create partition on this slice then I got error message: > > "Error mounting /dev/ad14cs1d on /tank/bootdir : No such file or > directory" > > After I close sysinstall and restart it then partition disappear... > --------------------------------------------------------------------------- > > Disk name: ad14 FDISK Partition > Editor > DISK Geometry: 18241 cyls/255 heads/63 sectors = 293041665 sectors > (143086MB) > > Offset Size(ST) End Name PType Desc > Subtype Flags > > 0 293046768 293046767 - 12 unused 0 > --------------------------------------------------------------------------- > > > FreeBSD testiserver 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Mon Dec > 1 12:13:41 EET 2008 root@testiserver:/usr/obj/usr/src/sys/KERNEL > amd64 > OK, finally resolved problem by filling drive with zeroes: # dd if=/dev/zero of=/dev/ad14 bs=10m From owner-freebsd-fs@FreeBSD.ORG Tue Dec 2 11:05:31 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 9B78A106567A for ; Tue, 2 Dec 2008 11:05:31 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id EC5BD8FC17 for ; Tue, 2 Dec 2008 11:05:30 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 89807 invoked from network); 2 Dec 2008 10:39:11 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 2 Dec 2008 10:39:11 -0000 Received: (qmail 38406 invoked by uid 907); 2 Dec 2008 10:38:48 -0000 Received: from midgard.transactionware.com (HELO STUDYPC) (192.168.1.55) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Tue, 02 Dec 2008 21:38:48 +1100 From: "Jan Mikkelsen" To: "'Wes Morgan'" , "'Matt Simerson'" Date: Tue, 2 Dec 2008 21:38:49 +1100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6838 Importance: Normal Thread-Index: AclIqgYOka1HNfubTKa7sEYbDvvTRwLvtSIg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: RE: Areca vs. ZFS performance testing. 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, 02 Dec 2008 11:05:31 -0000 Hi, Wes Morgan wrote: > On Sun, 16 Nov 2008, Matt Simerson wrote: >=20 > > The Areca cards do NOT have the cache enabled by default. I=20 > ordered the=20 > > optional battery and RAM upgrade for my collection of=20 > 1231ML cards. Even with=20 > > the BBWC, the cache is not enabled by default. I had to go=20 > out of my way to=20 > > enable it, on every single controller. >=20 > Are you using these areca cards successfully with large=20 > arrays? I found a=20 > 1680i card for a decent price and installed it this weekend,=20 > but since=20 > then I'm seeing the raidz2 pool that it's running hang so=20 > frequently that=20 > I can't even trust using it. The hangs occur in both 7-stable and=20 > 8-current with the new ZFS patch. Same exact settings that=20 > have been rock=20 > solid for me before now don't want to work at all. The drives=20 > are just set=20 > as JBOD -- the controller actually defaulted to this, so I=20 > didn't have to=20 > make any real changes in the BIOS. >=20 > Any tips on your setup? Did you have any similar problems? I am seeing I/O related lockups on 7.1-PRE with an Areca ARC-1220 = controller and eight drives in a RAID-6 array. The same hardware works fine with = 6.3. When I run gstat while it is happening I see I/O performance drop and = the time to service each write (ms/w) goes up, and then suddenly goes back = down to a sensible value. I have seen it get to about 22000ms. The system is essentially unusable for writes, which limits the utility = a bit. Reads seem fine. Is this similar to the behaviour you saw? Thanks, Jan Mikkelsen From owner-freebsd-fs@FreeBSD.ORG Tue Dec 2 12:04:37 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 42E56106564A; Tue, 2 Dec 2008 12:04:37 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id A3F708FC1A; Tue, 2 Dec 2008 12:04:36 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (unknown [74.193.182.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 1EF3DA16A620; Tue, 2 Dec 2008 06:04:35 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id mB2C4RhK000817; Tue, 2 Dec 2008 06:04:29 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Tue, 2 Dec 2008 06:04:27 -0600 (CST) From: Wes Morgan To: Jan Mikkelsen In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: RE: Areca vs. ZFS performance testing. 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, 02 Dec 2008 12:04:37 -0000 On Tue, 2 Dec 2008, Jan Mikkelsen wrote: > Hi, > > Wes Morgan wrote: >> On Sun, 16 Nov 2008, Matt Simerson wrote: >> >>> The Areca cards do NOT have the cache enabled by default. I >> ordered the >>> optional battery and RAM upgrade for my collection of >> 1231ML cards. Even with >>> the BBWC, the cache is not enabled by default. I had to go >> out of my way to >>> enable it, on every single controller. >> >> Are you using these areca cards successfully with large >> arrays? I found a >> 1680i card for a decent price and installed it this weekend, >> but since >> then I'm seeing the raidz2 pool that it's running hang so >> frequently that >> I can't even trust using it. The hangs occur in both 7-stable and >> 8-current with the new ZFS patch. Same exact settings that >> have been rock >> solid for me before now don't want to work at all. The drives >> are just set >> as JBOD -- the controller actually defaulted to this, so I >> didn't have to >> make any real changes in the BIOS. >> >> Any tips on your setup? Did you have any similar problems? > > I am seeing I/O related lockups on 7.1-PRE with an Areca ARC-1220 controller > and eight drives in a RAID-6 array. The same hardware works fine with 6.3. > > When I run gstat while it is happening I see I/O performance drop and the > time to service each write (ms/w) goes up, and then suddenly goes back down > to a sensible value. I have seen it get to about 22000ms. > > The system is essentially unusable for writes, which limits the utility a > bit. Reads seem fine. > > Is this similar to the behaviour you saw? Not quite. The zfs deadlock/hang effected both reads and writes, blocking either of them indefinitely. They were "fixed" by the most recent set of patches in -current. From owner-freebsd-fs@FreeBSD.ORG Tue Dec 2 17:33:46 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 990D11065675 for ; Tue, 2 Dec 2008 17:33:46 +0000 (UTC) (envelope-from cattelan@thebarn.com) Received: from slurp.thebarn.com (cattelan-host202.dsl.visi.com [208.42.117.202]) by mx1.freebsd.org (Postfix) with ESMTP id 40D208FC1A for ; Tue, 2 Dec 2008 17:33:46 +0000 (UTC) (envelope-from cattelan@thebarn.com) Received: from funky.thebarn.com (slurp.thebarn.com [208.42.117.201]) (authenticated bits=0) by slurp.thebarn.com (8.14.0/8.14.0) with ESMTP id mB2HMFHU022409; Tue, 2 Dec 2008 11:22:16 -0600 (CST) (envelope-from cattelan@thebarn.com) Message-ID: <49356EC7.80706@thebarn.com> Date: Tue, 02 Dec 2008 11:22:15 -0600 From: Russell Cattelan User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Dan References: <20081109174303.GA5146@ourbrains.org> In-Reply-To: <20081109174303.GA5146@ourbrains.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/8711/Tue Dec 2 09:07:32 2008 on slurp.thebarn.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: Will XFS be adopted 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, 02 Dec 2008 17:33:46 -0000 Dan wrote: > With XFS being adopted by Linux now for a number of years, I wonder why > it hasn't been by FreeBSD. It's a great FS that can be resized on the > fly which makes it a perfect journaling FS with volume managers. Anybody > know? > _______________________________________________ > 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" > So I find my self with a bit of extra time to actually try and make progress on XFS for FreeBSD again. I've started the process of essentially reporting xfs to FreeBSD, (alot of stuff has changed in XFS) It is still quite a ways off but I hope to have mount and read support working again shortly. The lastest work can be found at. http://oss.sgi.com/cgi-bin/gitweb.cgi?p=cattelan/FreeBSD_svn/.git;a=shortlog;h=refs/heads/xfs-work I do realize that I will never have enough time to fully support XFS but I hope to at least get it off the ground again and hopefully build some interest. -Russell Cattelan From owner-freebsd-fs@FreeBSD.ORG Tue Dec 2 23:04: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 105E51065676 for ; Tue, 2 Dec 2008 23:04:23 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id BD20B8FC1B for ; Tue, 2 Dec 2008 23:04:22 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1343994ywe.13 for ; Tue, 02 Dec 2008 15:04:21 -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=pYerFRNPUmWjJJCVAMFRQduSQmydiBomMLu+CEBmVew=; b=kg8ptAT4Q9xvDP+O1Gbf3yIMWll292zQ0Mypksly3Q5NoPlo9VwEKt3xPz1wzIHyk+ PtyOaT+dpyMfdG11C5xRIdvEwNM46ao9BwdWVwgwBG7e0m0qdq0SGC2iOXPCOhfZ6gGN TOJMGhzlR5hWxkKdNkWvm7QLJdy7+EUZ2RwEw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=qCxebIyB4DmW1MgZTfAPYNl2VTMG97/IXyJhmHw1yObj4YgHZIujZVVVw1ZXh7palj G6j0FXwse79+2bzAcqJcoKfTyFMQwmEKy7FXGrcXS2ZMdMx2JzKaGsXU2A5UtoBIS923 c3EZvIJqjRtbOaYhycUMvrVRFRX8I0/4yhBWs= Received: by 10.150.144.17 with SMTP id r17mr2059404ybd.240.1228259061864; Tue, 02 Dec 2008 15:04:21 -0800 (PST) Received: by 10.151.128.6 with HTTP; Tue, 2 Dec 2008 15:04:21 -0800 (PST) Message-ID: <5f67a8c40812021504p1d67fde1x3d9a9ef8d7214dfc@mail.gmail.com> Date: Tue, 2 Dec 2008 18:04:21 -0500 From: "Zaphod Beeblebrox" 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 filesystem size anomaly... 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, 02 Dec 2008 23:04:23 -0000 This is all with ZFS version 6 in FreeBSD-7.1-RC, fyi... I have a machine with the ports tree mounted in ZFS right out of the examples: [3:75:375]root@canoe:/usr/ports> zfs list | grep ports canoe/ports 3.54G 66.6G 2.35G /usr/ports canoe/ports/distfiles 1.19G 66.6G 1.19G /usr/ports/distfiles ... but the sizes here are curious. 1.2G for distfiles is about correct... but 2.35G for the rest of ports is unreasonable. [3:76:376]root@canoe:/usr/ports> du -hs . 1.6G . ... saying that ports + distfiles are 1.6G. There are no snapshots for either ports or distfiles. There are no open work directories. The machine has recently rebooted. The only directory with more than 20M in it is distfiles --- which is the subfilesystem. ... this number 2.35G is 2G more than I expect. Where is this space? From owner-freebsd-fs@FreeBSD.ORG Wed Dec 3 00:49:55 2008 Return-Path: Delivered-To: fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1060) id 2AEF91065677; Wed, 3 Dec 2008 00:49:55 +0000 (UTC) Date: Wed, 3 Dec 2008 00:49:55 +0000 From: Craig Rodrigues To: Alfred Perlstein Message-ID: <20081203004955.GA85280@crodrigues.org> References: <20081127205417.GE58709@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081127205417.GE58709@elvis.mu.org> User-Agent: Mutt/1.4.2.1i Cc: Craig Rodrigues , dfr@freebsd.org, fs@freebsd.org Subject: Re: questions about nmount and 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, 03 Dec 2008 00:49:55 -0000 On Thu, Nov 27, 2008 at 12:54:17PM -0800, Alfred Perlstein wrote: > What do you guys think? Is nmount up for this? Any pointers to > using nmount? Or should I sysctl? nmount() is up to the task. Look at the latest mount_nfs code in CURRENT. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-fs@FreeBSD.ORG Wed Dec 3 08:57: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 02533106568B for ; Wed, 3 Dec 2008 08:57:55 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 680A68FC2E for ; Wed, 3 Dec 2008 08:57:53 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id mB38bcCR027836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Dec 2008 09:37:38 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id mB38bZQA020251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Dec 2008 09:37:36 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id mB38bZJN076808; Wed, 3 Dec 2008 09:37:35 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id mB38bZNZ076807; Wed, 3 Dec 2008 09:37:35 +0100 (CET) (envelope-from ticso) Date: Wed, 3 Dec 2008 09:37:35 +0100 From: Bernd Walter To: Zaphod Beeblebrox Message-ID: <20081203083734.GC71750@cicely7.cicely.de> References: <5f67a8c40812021504p1d67fde1x3d9a9ef8d7214dfc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5f67a8c40812021504p1d67fde1x3d9a9ef8d7214dfc@mail.gmail.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.060, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: freebsd-fs@freebsd.org Subject: Re: ZFS filesystem size anomaly... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 08:57:55 -0000 On Tue, Dec 02, 2008 at 06:04:21PM -0500, Zaphod Beeblebrox wrote: > This is all with ZFS version 6 in FreeBSD-7.1-RC, fyi... > > I have a machine with the ports tree mounted in ZFS right out of the > examples: > > [3:75:375]root@canoe:/usr/ports> zfs list | grep ports > canoe/ports 3.54G 66.6G 2.35G /usr/ports > canoe/ports/distfiles 1.19G 66.6G 1.19G > /usr/ports/distfiles > > ... but the sizes here are curious. 1.2G for distfiles is about correct... > but 2.35G for the rest of ports is unreasonable. It always includes the subvolumes. So just canoe/ports alone is 2.35G - 1.19G. You can get more details with "zfs get all canoe/ports". -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-fs@FreeBSD.ORG Wed Dec 3 22:56:06 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 89CD61065686 for ; Wed, 3 Dec 2008 22:56:06 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id 1AC368FC16 for ; Wed, 3 Dec 2008 22:56:05 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by gxk12 with SMTP id 12so2646223gxk.19 for ; Wed, 03 Dec 2008 14:56:05 -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:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=CKmFJiglEyYkVnUsBUrNi5JrrmvcjWprUKCwjrAMMq4=; b=sKzOGJ3zYns0AE75S+X6ZQsAkvaIYC0rgq6X96iz1fRBrtnsBSGHhMMnVl1QrC6eTD YI6uy0mVntkCG0jQtH8p8yQTwYBimuHEvH5mr3wmbWf++TH/w1Z7q1nQdgk+v3GVLGkY a14JG3U0ZOHw+CJdrrsQruI/w6Qeckn0plkFQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=vWoqPd9IKRLO6hfksmxgTXFJ6nYrzUR4egmvmo/pxhZCGcd+g6k/lmv0+odT/XwzqV EVH7hRm/cyKsEYcmgZ3N+mtTcGWOzW8RYAGlT4bPcPkZ2LP5WyIw+wrXLrIn89G07dtu naxtVZ5C6f8Hjpex34K6BkNqi7OfPtA+B8Tdg= Received: by 10.151.142.2 with SMTP id u2mr26950388ybn.4.1228344823942; Wed, 03 Dec 2008 14:53:43 -0800 (PST) Received: by 10.150.123.1 with HTTP; Wed, 3 Dec 2008 14:53:43 -0800 (PST) Message-ID: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> Date: Wed, 3 Dec 2008 17:53:43 -0500 From: "Josh Carroll" To: "Kostik Belousov" In-Reply-To: <20081125150342.GL2042@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> Cc: freebsd-fs@freebsd.org, FreeBSD Stable Subject: Re: ext2 inode size patch - RE: PR kern/124621 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 22:56:06 -0000 > Ok, I describe my concern once more. I do not object against the checking > of the inode size. But, if inode size is changed, then some data is added > to the inode, that could (and usually does, otherwise why extend it ?) > change intrerpetation of the inode. Thus, we need a verification of the > fact that simply ignoring added fields does not damage filesystem or > cause user data corruption. Verification != testing. Let me take another crack at explaining why I think this patch is not dangerous. The inode size is determined by reading the following member: __u16 s_inode_size; of the ext2_super_block structure. I took a look at the Linux 2.6.27.7 kernel source, and indeed they do something very similar if not the same: #define EXT2_INODE_SIZE(s) (EXT2_SB(s)->s_inode_size) If you compare to what I did: #define EXT2_INODE_SIZE(s) ((s)->u.ext2_sb.s_inode_size) This is really the same thing, since EXT2_SB is defined (in the Linux kernel src as): #ifdef __KERNEL__ #include static inline struct ext2_sb_info *EXT2_SB(struct super_block *sb) { return sb->s_fs_info; } And struct ext2_sb_info has the following member: int s_inode_size; Essentially, the changes I made simply query the existing information from the filesystem, which is what the Linux kernel does as well. The inode size, blocks per group, etc are all defined at filesystem creation time by mke2fs and it ensures the sanity of the relationship between the inodes/blocks/block groups. The first diagram here: http://sunsite.nus.sg/LDP/LDP/tlk/node95.html Makes it clear that as long as the number of inodes per block and the blocks per group is is sane during fs creation, looking up the inode size as my patch does is fine, since the creation of the filesystem is ensures a correct by construction situation. We're simply reading the size of the inode based on the filesystem. I hope this is sufficient to convince some further thought about committing this. For those interested in the relevant Linux kernel source, you can have a look at line 105 of include/linux/ext2_fs.h from the linux-2.6.27.7 kernel source. Thanks, Josh From owner-freebsd-fs@FreeBSD.ORG Thu Dec 4 07:31:04 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 96C661065676; Thu, 4 Dec 2008 07:31:04 +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 666D38FC13; Thu, 4 Dec 2008 07:31:04 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id D38451CCF09; Thu, 4 Dec 2008 02:15:07 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 04 Dec 2008 02:15:07 -0500 X-Sasl-enc: EQDauYBCrxW/pU5OuZOqHdtKdL86qR9yYZfh2Ygwt3vM 1228374907 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 1BD5F24DF8; Thu, 4 Dec 2008 02:15:07 -0500 (EST) Message-ID: <49378379.5050900@FreeBSD.org> Date: Thu, 04 Dec 2008 07:15:05 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: Kostik Belousov References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> In-Reply-To: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> 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, FreeBSD Stable 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: Thu, 04 Dec 2008 07:31:04 -0000 Hi, The inode size for the ext3 filesystem which Gentoo created for my last install defaulted to 256 bytes, so I got bit by this problem. I can't speak for the write path. but the read path looks just fine to me, and the patch should go in ASAP. Josh Carroll wrote: >> Ok, I describe my concern once more. I do not object against the checking >> of the inode size. But, if inode size is changed, then some data is added >> to the inode, that could (and usually does, otherwise why extend it ?) >> change intrerpetation of the inode. Thus, we need a verification of the >> fact that simply ignoring added fields does not damage filesystem or >> cause user data corruption. Verification != testing. >> If folk are paranoid, then add a check for dynamic inode size and disable ext2fs writes by downgrading the mount in that case (We can do that, right? Can someone make sure Josh gets the help he needs here?) As Josh points out, the ext2 inode size is stored in the superblock. Whilst it may vary between ext2 filesystems, *the inode size itself does not appear to be something which one can modify in an existing ext2/3 filesystem*. Older ext2 filesystems may not contain the inode size field in the superblock, and the patch appears to default to 128 for that case. The double indirection thus introduced doesn't concern me, our ext2fs is not performance critical code, and the superblock is likely to sit in L2/L3 cache anyway (note: content free argument). Thanks to Josh for fixing this problem. cheers BMS From owner-freebsd-fs@FreeBSD.ORG Thu Dec 4 10:51:34 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 503BA1065678; Thu, 4 Dec 2008 10:51:34 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id E062B8FC16; Thu, 4 Dec 2008 10:51:33 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1L8Bnw-0005Kj-NG; Thu, 04 Dec 2008 12:51:32 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id mB4ApTZa061830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Dec 2008 12:51:30 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id mB4ApTum025259; Thu, 4 Dec 2008 12:51:29 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id mB4ApTom025258; Thu, 4 Dec 2008 12:51:29 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 4 Dec 2008 12:51:29 +0200 From: Kostik Belousov To: "Bruce M. Simpson" Message-ID: <20081204105129.GA2246@deviant.kiev.zoral.com.ua> References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <49378379.5050900@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <49378379.5050900@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1L8Bnw-0005Kj-NG 247ecf99707698ec13432c25c35defde X-Terabit: YES Cc: josh.carroll@gmail.com, freebsd-fs@freebsd.org, FreeBSD Stable 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: Thu, 04 Dec 2008 10:51:34 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 04, 2008 at 07:15:05AM +0000, Bruce M. Simpson wrote: > Hi, >=20 > The inode size for the ext3 filesystem which Gentoo created for my last= =20 > install defaulted to 256 bytes, so I got bit by this problem. >=20 > I can't speak for the write path. but the read path looks just fine to=20 > me, and the patch should go in ASAP. >=20 > Josh Carroll wrote: > >>Ok, I describe my concern once more. I do not object against the checki= ng > >>of the inode size. But, if inode size is changed, then some data is add= ed > >>to the inode, that could (and usually does, otherwise why extend it ?) > >>change intrerpetation of the inode. Thus, we need a verification of the > >>fact that simply ignoring added fields does not damage filesystem or > >>cause user data corruption. Verification !=3D testing. > >> =20 >=20 > If folk are paranoid, then add a check for dynamic inode size and=20 > disable ext2fs writes by downgrading the mount in that case (We can do=20 > that, right? Can someone make sure Josh gets the help he needs here?) >=20 > As Josh points out, the ext2 inode size is stored in the superblock.=20 > Whilst it may vary between ext2 filesystems, *the inode size itself does= =20 > not appear to be something which one can modify in an existing ext2/3=20 > filesystem*. >=20 > Older ext2 filesystems may not contain the inode size field in the=20 > superblock, and the patch appears to default to 128 for that case. The=20 > double indirection thus introduced doesn't concern me, our ext2fs is not= =20 > performance critical code, and the superblock is likely to sit in L2/L3= =20 > cache anyway (note: content free argument). >=20 > Thanks to Josh for fixing this problem. Bruce, feel free to commit the patch. I do not want to spend time on ext2 in any form, and due to our (only partly jokingly) rule of the "last committer is the owner", I do not want to analyze ext2 bug reports after. --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk3tjEACgkQC3+MBN1Mb4gsMACfdZOmzO3B2qwkehgi1lWJWB+s anMAoNKxfWj1QQ6gOIYnXXIRE6bPZeWs =8ohK -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-fs@FreeBSD.ORG Thu Dec 4 13:16:19 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 4F560106564A; Thu, 4 Dec 2008 13:16:19 +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 1ED1F8FC19; Thu, 4 Dec 2008 13:16:19 +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 820781CD17B; Thu, 4 Dec 2008 08:16:18 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 04 Dec 2008 08:16:18 -0500 X-Sasl-enc: rXF7KLAAqFGOMAFJIgwgyXV29LtEJzB+W0cOm9z9lnAU 1228396578 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 AEA733A2C1; Thu, 4 Dec 2008 08:16:17 -0500 (EST) Message-ID: <4937D820.8080803@FreeBSD.org> Date: Thu, 04 Dec 2008 13:16:16 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: Kostik Belousov References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125140601.GH2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250617q5fffb41exe20dfb8314fc4a9d@mail.gmail.com> <20081125142827.GI2042@deviant.kiev.zoral.com.ua> <8cb6106e0811250657q6fdf08b0x1e94f35fd0a7ed4f@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <49378379.5050900@FreeBSD.org> <20081204105129.GA2246@deviant.kiev.zoral.com.ua> In-Reply-To: <20081204105129.GA2246@deviant.kiev.zoral.com.ua> 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, FreeBSD Stable 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: Thu, 04 Dec 2008 13:16:19 -0000 Kostik Belousov wrote: > ... > Bruce, feel free to commit the patch. > > I do not want to spend time on ext2 in any form, and due to our (only > partly jokingly) rule of the "last committer is the owner", I do not > want to analyze ext2 bug reports after. > Yes, development resource is limited here too, and any involvement on my part here DOES NOT constitute any commitment, express or implied, to maintaining the ext2fs module beyond the change being considered right now. I find that this often has to be reiterated as people are prone to confusing the concepts "open source" and "free", basic economics dictates infinite demand for free goods, and we've all got lives to live. As per our off-list discussion: It's a damned if we do and damned if we don't situation. Take the patch and it eats someone's lunch, and our reptuation suffers. Don't take the patch and look like patriarchal killjoys, and our reputation siffers. Your specific objection is that the testing is insufficient to exercise the patch, and there could be an area of ext2 which this patch doesn't address. That can never be said with 100% certainty, but I agree with you. Content free argument: Based on my reading of the code, the patch must be considered experimental. Whilst the scope of the patch appears to be small, the symbol space of ext2 is bigger -- a case of feeping creaturism due to ext2 itself, but hey, that's evolution for you. If folk are happy with it going in, let it go in, but remember, you get the system you apply effort to. I myself consider the patch experimental -- but HEAD is an experiment, is it not? Reality is what you can get away with. cheers BMS From owner-freebsd-fs@FreeBSD.ORG Thu Dec 4 17:06:49 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 D91B51065673 for ; Thu, 4 Dec 2008 17:06:49 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id 76B148FC13 for ; Thu, 4 Dec 2008 17:06:49 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by gxk12 with SMTP id 12so3019100gxk.19 for ; Thu, 04 Dec 2008 09:06:48 -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:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Li2Y+DxJbqcg0TZ82JW5/oGyyFyprpt9aKKztSAm7IM=; b=K5UDgJeNf6OTehVoKlKgwT7Abg/PBDejDEGiqubwWZlzs7hYDL89ldxZRpQLzyf5l0 D9CiNPg9JU6qFE/ZHsJoNJcSQcdIJALJybaIv489fxQtsrdU8TADxl77Q733aFWqYFsU 2QTI7a+UFo4BvDZ1KlHOo2tFI/sRF8QDNUigI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=mEjMXYfctV4p0WRG0Rxn9aD6tr2B46tqf9N9ZjCrpwqi94cJnSyAk6TlcWPhZOu0Tt 2nPtzOlmsvP+1EGyYQ6DBh3mIvAtdSApPEC88zkIPMnRn8at1slPKVFqkI2dHwb89onw jQwDHQEtkvt6Crb5YxSsa5/kI40y88Crq5c3o= Received: by 10.151.103.11 with SMTP id f11mr10696708ybm.32.1228410164206; Thu, 04 Dec 2008 09:02:44 -0800 (PST) Received: by 10.150.123.1 with HTTP; Thu, 4 Dec 2008 09:02:44 -0800 (PST) Message-ID: <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com> Date: Thu, 4 Dec 2008 12:02:44 -0500 From: "Josh Carroll" To: "Gonzalo Nemmi" In-Reply-To: <200812041747.09040.gnemmi@gmail.com> 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> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ext2 inode size patch - RE: PR kern/124621 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2008 17:06:49 -0000 > Could you please point me to your patch and an explanation on how to apply it > and test it? You can grab the patch here: http://pflog.net/~floyd/ext2fs.diff To apply it: cd /usr/src/sys/gnu/fs patch < /path/to/ext2fs.diff cd /usr/src/sys/modules/ext2fs make clean && make kldload ./ext2fs.ko Then umount and mount again your ext2 file systems. This should apply cleanly to RELENG_7_0, RELENG_7_1 and RELENG_7 source. I'm not sure if it'll apply cleanly to -CURRENT or not (I can provide an updated patch if you need it). Note: if you have ext2fs built into your kernel, you'll have to build and install your kernel as usual after patching, instead of building the module separately. Also, if you already have ext2fs loaded, you'll need to kldunload it first of course. If you want to update the ext2fs.ko in your installed kernel in /boot/kernel, after a make in .../modules/ext2fs, you can "make install". Thanks, Josh From owner-freebsd-fs@FreeBSD.ORG Thu Dec 4 17:13:48 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 8678F1065673 for ; Thu, 4 Dec 2008 17:13:48 +0000 (UTC) (envelope-from gnemmi@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 383F18FC17 for ; Thu, 4 Dec 2008 17:13:48 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: by qyk11 with SMTP id 11so5106133qyk.19 for ; Thu, 04 Dec 2008 09:13:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=D/IZxoDBsYC9MtrwgJrfMVshXjkMMSbPZ3AW1LzXp2A=; b=Yps3iF3Kj7ZAEgb23jfCPacFTJ4HCenNfuI5GBfQip/BYzr4Zg0YsEPQYd580Kbtej mrKn/NEkd0Ok/hoZycgV4VejJGNSHql3uO6t8TbnSmB+sQ/ASFWTVQ4SUj5KMIhPhc93 ZJKte0GLemcyAvacAkHObn5p+s/E+Zj68Y/ho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=xTEmDXo2mFOqMlcC7+N8qEcWZRye9gOKp5StffNkHD3qs1CiYdgSsjKH7WWbq9EehR SkaaqyLY9cQvckRi0o49JeSczM5zQ2Raz7KHHioPcbMKpVQMqrr5nMiE3rpd2nL7KBJi zNSAQZP5CAFo5Bj5Ahl4svkkMXqgzI6NPIK1M= Received: by 10.214.149.3 with SMTP id w3mr15054314qad.111.1228409234693; Thu, 04 Dec 2008 08:47:14 -0800 (PST) Received: from ?192.168.1.2? ([190.177.205.95]) by mx.google.com with ESMTPS id 6sm8871917qwk.52.2008.12.04.08.47.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 04 Dec 2008 08:47:14 -0800 (PST) From: Gonzalo Nemmi To: freebsd-stable@freebsd.org, josh.carroll@gmail.com Date: Thu, 4 Dec 2008 17:47:08 -0200 User-Agent: KMail/1.9.10 References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> In-Reply-To: <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812041747.09040.gnemmi@gmail.com> Cc: freebsd-fs@freebsd.org 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: Thu, 04 Dec 2008 17:13:48 -0000 On Wednesday 03 December 2008 8:53:43 pm Josh Carroll wrote: > > Ok, I describe my concern once more. I do not object against the checking > > of the inode size. But, if inode size is changed, then some data is added > > to the inode, that could (and usually does, otherwise why extend it ?) > > change intrerpetation of the inode. Thus, we need a verification of the > > fact that simply ignoring added fields does not damage filesystem or > > cause user data corruption. Verification != testing. > > Let me take another crack at explaining why I think this patch is not > dangerous. > > The inode size is determined by reading the following member: > > __u16 s_inode_size; > > of the ext2_super_block structure. > > I took a look at the Linux 2.6.27.7 kernel source, and indeed they do > something very similar if not the same: > > #define EXT2_INODE_SIZE(s) (EXT2_SB(s)->s_inode_size) > > If you compare to what I did: > > #define EXT2_INODE_SIZE(s) ((s)->u.ext2_sb.s_inode_size) > > This is really the same thing, since EXT2_SB is defined (in the Linux > kernel src as): > > #ifdef __KERNEL__ > #include > static inline struct ext2_sb_info *EXT2_SB(struct super_block *sb) > { > return sb->s_fs_info; > } > > And struct ext2_sb_info has the following member: > > int s_inode_size; > > Essentially, the changes I made simply query the existing information > from the filesystem, which is what the Linux kernel does as well. > > The inode size, blocks per group, etc are all defined at filesystem > creation time by mke2fs and it ensures the sanity of the relationship > between the inodes/blocks/block groups. > > The first diagram here: > > http://sunsite.nus.sg/LDP/LDP/tlk/node95.html > > Makes it clear that as long as the number of inodes per block and the > blocks per group is is sane during fs creation, looking up the inode > size as my patch does is fine, since the creation of the filesystem is > ensures a correct by construction situation. We're simply reading the > size of the inode based on the filesystem. > > I hope this is sufficient to convince some further thought about > committing this. > > For those interested in the relevant Linux kernel source, you can have > a look at line 105 of include/linux/ext2_fs.h from the linux-2.6.27.7 > kernel source. > > Thanks, > Josh Could you please point me to your patch and an explanation on how to apply it and test it? I've been following your las emails referencing it ( on @questions and @hackers or current i think it was ... ) and I'd like to give it a spin in here ... I've followed the "can't mount ext2/3" problem for a time (since I have that problem) and would like to know to what extent for patch solves the problem. Here are some of the references: mounting linux partitions Fri May 9 18:05:26 UTC 2008 http://lists.freebsd.org/pipermail/freebsd-questions/2008-May/174588.html bad file descriptor when mounting an ext2fs. Tue Jun 10 11:08:46 UTC 2008 http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/176506.html mounting ext2fs partitions on FBSD7 ( third time a charm?) Fri Jul 4 23:33:53 UTC 2008 http://lists.freebsd.org/pipermail/freebsd-questions/2008-July/178219.html My case: root@inferna:~ # ls -l /dev/ad4s ad4s1% ad4s2% ad4s3% ad4s3a% ad4s3b% ad4s3c% ad4s3d% ad4s3e% ad4s3f% ad4s4% ad4s5% ad4s6% ad4s7% ad4s8% root@inferna:~ # ls -l /dev/ad4s root@inferna:~ # tune2fs -l /dev/ad4s1 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s6 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s7 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s8 | grep "Inode size" Inode size: 256 root@inferna:~ # tune2fs -l /dev/ad4s9 | grep "Inode size" BTW: I'm willing to run any tests you need me too, even if they imply a serious risk of loosing data on the 256 inode partitions. Regards -- Blessings Gonzalo Nemmi From owner-freebsd-fs@FreeBSD.ORG Thu Dec 4 17:57: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 7F2C81065675 for ; Thu, 4 Dec 2008 17:57:55 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 342798FC17 for ; Thu, 4 Dec 2008 17:57:55 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1786989yxb.13 for ; Thu, 04 Dec 2008 09:57:54 -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:references; bh=h4vcfvMKtpVLNd1n1GqnlwoR2qfRnRndBz/udfBTvrc=; b=iEqwKTIzMEmYfs+P1kLOuFZ9Iku0FD+KiEMeBh8+mQSAXy+SQKCQEFvQYbT4Wg8Jam gHe9WsHgQzZXEFziYe6FaLb6GquxKUrPmcG35zzOE0PqDEOnODJsslrl96zE6sqkEebY fbJOUI0D0LyfNapfhZ1DK8cBEU5OiORl1oO2k= 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:references; b=Bvhs64hlSIQQ2T49XfOveq2ICSRuJgoISE/0rGOBwQUfmdM0OchQlKi8LBicCCd4ar 8VnSUvEuSCt0Gc1mWGLsD8zhumPkLfUETL+iTyRChiIQJeUlZL0g3WIW9Ra8wRixAw4b Jrs8aHZHvDqt3vmbn/k1wUHvJowgOOvzVtQyM= Received: by 10.151.11.17 with SMTP id o17mr4039447ybi.119.1228413474520; Thu, 04 Dec 2008 09:57:54 -0800 (PST) Received: by 10.151.128.6 with HTTP; Thu, 4 Dec 2008 09:57:54 -0800 (PST) Message-ID: <5f67a8c40812040957h8d90b26t5092fa68c76bafb8@mail.gmail.com> Date: Thu, 4 Dec 2008 12:57:54 -0500 From: "Zaphod Beeblebrox" To: ticso@cicely.de In-Reply-To: <20081203083734.GC71750@cicely7.cicely.de> MIME-Version: 1.0 References: <5f67a8c40812021504p1d67fde1x3d9a9ef8d7214dfc@mail.gmail.com> <20081203083734.GC71750@cicely7.cicely.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS filesystem size anomaly... 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, 04 Dec 2008 17:57:55 -0000 On Wed, Dec 3, 2008 at 3:37 AM, Bernd Walter wrote: > On Tue, Dec 02, 2008 at 06:04:21PM -0500, Zaphod Beeblebrox wrote: > > This is all with ZFS version 6 in FreeBSD-7.1-RC, fyi... > > > > I have a machine with the ports tree mounted in ZFS right out of the > > examples: > > > > [3:75:375]root@canoe:/usr/ports> zfs list | grep ports > > canoe/ports 3.54G 66.6G 2.35G /usr/ports > > canoe/ports/distfiles 1.19G 66.6G 1.19G > > /usr/ports/distfiles > > > > ... but the sizes here are curious. 1.2G for distfiles is about > correct... > > but 2.35G for the rest of ports is unreasonable. > > It always includes the subvolumes. > So just canoe/ports alone is 2.35G - 1.19G. > You can get more details with "zfs get all canoe/ports". Yes... I understand that. There is a 2G discrepancy. Du on distfiles agrees --- 1.2G vs. 1.19. Du on ports says 1.6G --- including the 1.2 gig in distfiles. That means that du thinks that ports itself is 0.4 Gig, not 2.35 Gig. From owner-freebsd-fs@FreeBSD.ORG Thu Dec 4 20:34:02 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 39DE1106564A for ; Thu, 4 Dec 2008 20:34:02 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id D516A8FC17 for ; Thu, 4 Dec 2008 20:34:01 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by gxk12 with SMTP id 12so3115149gxk.19 for ; Thu, 04 Dec 2008 12:34:01 -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=xaWPJ6KtVDOzeTiFc5tTqLrHYCVMPtig054SUBU0M1U=; b=A9TCGPBXxrGCQ33ADXJ4N91wlZCrjC3VIrc6BePgOp6FKNtUnAbyWL10oPUFBglm5N 22Fz1GNBPDerypO4k5iixkjVcCh2x8neeQGRuRXI58E56KfmtbLK4IaAggDgKHsQ518f IzeRFb840IgbmoiTyqQWImStPVyRlwIfPURS4= 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=o9IczLIoi+ZyVEQBwOcFO0Qxv6nQDwOu4YJj9b44ZYXIt/JQ6cGgtt62NKHVD0NGxo Ze5l3CpUqWW6UIMQKR6/5SVpPTQE/EjB5ddgiPuUQAibcTcBUhg3Z4u+5w4hfxs9PsKU KnSqVCuxLAGMpBLSL+G5+cXIyGsZEAY5U4CR8= Received: by 10.231.13.130 with SMTP id c2mr444202iba.8.1228422116510; Thu, 04 Dec 2008 12:21:56 -0800 (PST) Received: by 10.231.19.11 with HTTP; Thu, 4 Dec 2008 12:21:56 -0800 (PST) Message-ID: <3a142e750812041221v26520a53q4f7df488af607305@mail.gmail.com> Date: Thu, 4 Dec 2008 21:21:56 +0100 From: "Paul B. Mahol" To: "Daichi GOTO" In-Reply-To: <4917E0C9.5020105@ongs.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4917E0C9.5020105@ongs.co.jp> Cc: freebsd-fs@freebsd.org, FreeBSD Current Subject: Re: [Call for Test] a patch for kern/121385 - Unionfs cross mount issue 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, 04 Dec 2008 20:34:02 -0000 On 11/10/08, Daichi GOTO wrote: > Hi Unionfs users > > About kern/121385 - Unionfs cross mount issue, by discussion at > EuroBSDCon2008, > unionfs does not allow user to do cross mount operation. If you have some > interest > this issue, please get this patch and try with current. I'll commit this > patch after 1 week later. > > PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/121385 > Patch: > http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-cross-mount.diff > > This issue was discussed at EuroBSDCon2008 FreeBSD developer summit. > Thanks for hrs and gnn :) > > -- > Daichi GOTO, http://people.freebsd.org/~daichi > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > I tested CURRENT and was unable to reproduce panic. -- Paul From owner-freebsd-fs@FreeBSD.ORG Fri Dec 5 00:36: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 976681065672 for ; Fri, 5 Dec 2008 00:36:21 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.246.90]) by mx1.freebsd.org (Postfix) with ESMTP id 5D3968FC1A for ; Fri, 5 Dec 2008 00:36:21 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.246.94]) by natial.ongs.co.jp (Postfix) with ESMTPSA id BE794125424; Fri, 5 Dec 2008 09:36:19 +0900 (JST) Message-ID: <49387783.7080503@freebsd.org> Date: Fri, 05 Dec 2008 09:36:19 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: "Paul B. Mahol" References: <4917E0C9.5020105@ongs.co.jp> <3a142e750812041221v26520a53q4f7df488af607305@mail.gmail.com> In-Reply-To: <3a142e750812041221v26520a53q4f7df488af607305@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, FreeBSD Current Subject: Re: [Call for Test] a patch for kern/121385 - Unionfs cross mount issue 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, 05 Dec 2008 00:36:21 -0000 Thanks for your test, Paul B. Mahol wrote: > On 11/10/08, Daichi GOTO wrote: >> Hi Unionfs users >> >> About kern/121385 - Unionfs cross mount issue, by discussion at >> EuroBSDCon2008, >> unionfs does not allow user to do cross mount operation. If you have some >> interest >> this issue, please get this patch and try with current. I'll commit this >> patch after 1 week later. >> >> PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/121385 >> Patch: >> http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-cross-mount.diff >> >> This issue was discussed at EuroBSDCon2008 FreeBSD developer summit. >> Thanks for hrs and gnn :) >> >> -- >> Daichi GOTO, http://people.freebsd.org/~daichi >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > > I tested CURRENT and was unable to reproduce panic. You cannot get the same panic described on kern/121385 as follow: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/121385 How-To-Repeat: # mkdir -p /unionfs/disk1 # mkdir -p /unionfs/disk2 # mount -t unionfs /unionfs/disk1 /unionfs/disk2 # mount -t unionfs /unionfs/disk2 /unionfs/disk1 # touch /unionfs/disk1/foo The r178483 (http://svn.freebsd.org/viewvc/base?view=revision&revision=178483) avoids this panic. Try without r178483 and you will get a panic. Some discussions with some developers, we are testing a new cross-mount issue patch, after some more check, I'll open it. thanks :) -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Fri Dec 5 10:11:19 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 425791065670; Fri, 5 Dec 2008 10:11:19 +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 D75068FC1A; Fri, 5 Dec 2008 10:11:18 +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 306B11CC6B8; Fri, 5 Dec 2008 05:11:18 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 05 Dec 2008 05:11:18 -0500 X-Sasl-enc: uxwnbMegg1OLlKySK7psLPt+G9idZ3/wtHdW0QEucwc7 1228471877 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 8157BC311; Fri, 5 Dec 2008 05:11:17 -0500 (EST) Message-ID: <4938FE44.9090608@FreeBSD.org> Date: Fri, 05 Dec 2008 10:11:16 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) 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> In-Reply-To: <200812041747.09040.gnemmi@gmail.com> 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: 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: Fri, 05 Dec 2008 10:11:19 -0000 Hi, I just tested the ext2fuse project on FreeBSD 7.1-PRERELEASE as of today and found that it works for read/write on an ext3 filesystem. The inode size was 128 -- I haven't exercised dynamic inode sizes. ext2fuse project: http://sourceforge.net/projects/ext2fuse Required FreeBSD patches: http://people.freebsd.org/~bms/dump/ext2fuse-freebsd.patch Steps: 1. fetch http://ovh.dl.sourceforge.net/sourceforge/ext2fuse/ext2fuse-src-0.8.1.tar.gz 2. tar xvf ext2fuse-src-0.8.1.tar.gz 3. patch -i ext2fuse-0.8.1-freebsd.patch 4. cd ext2fuse-src-0.8.1 5. aclocal ; automake ; autoconf 6. ./configure && gmake Performance seems quite slow, it could probably benefit from being ported to use UBLIO as ntfs-3g for FreeBSD has. I'm going to leave this thing for others to play with, this was a 20 minute bunk-off from other work. It shouldn't take much effort to create a port around it. cheers BMS From owner-freebsd-fs@FreeBSD.ORG Fri Dec 5 11:40:49 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 F3ADB1065677; Fri, 5 Dec 2008 11:40:48 +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 C806D8FC0C; Fri, 5 Dec 2008 11:40:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 1D0CB1CDBB4; Fri, 5 Dec 2008 06:40:48 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 05 Dec 2008 06:40:48 -0500 X-Sasl-enc: qlQqapjSLEkhsayyjDNOojkbOD9Qnp5XB4JCwfnh5gJ9 1228477247 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 8048830C5F; Fri, 5 Dec 2008 06:40:47 -0500 (EST) Message-ID: <4939133E.2000701@FreeBSD.org> Date: Fri, 05 Dec 2008 11:40:46 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.14 (X11/20080514) 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> In-Reply-To: <4938FE44.9090608@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: Fri, 05 Dec 2008 11:40:49 -0000 Bruce M. Simpson wrote: > ... > Performance seems quite slow, it could probably benefit from being > ported to use UBLIO as ntfs-3g for FreeBSD has. > > I'm going to leave this thing for others to play with, this was a 20 > minute bunk-off from other work. It shouldn't take much effort to > create a port around it. P.S. Ale's patch to use libublio for fusefs-ntfs is here, if anyone picks up on ext2fuse before I do: http://people.freebsd.org/~alepulver/fusefs-ntfs.diff This contains the necessary diffs for UBLIO. cheers BMS From owner-freebsd-fs@FreeBSD.ORG Fri Dec 5 12:57:25 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 B1A291065673 for ; Fri, 5 Dec 2008 12:57:25 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E3B1C8FC12 for ; Fri, 5 Dec 2008 12:57:24 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA24516; Fri, 05 Dec 2008 14:57:22 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <49392532.4000300@icyb.net.ua> Date: Fri, 05 Dec 2008 14:57:22 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-gnome@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: partition covering the whole slice 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, 05 Dec 2008 12:57:25 -0000 I have a disk with two slices and each slices has a single real partition covering the whole slice, sector-to-sector. I don't remember how I managed to configure the disk this way, is this even possible? :-) $ gpart show => 63 781422705 ad12 MBR (373G) 63 209712447 1 freebsd [active] (100G) 209712510 571705155 2 freebsd [active] (273G) 781417665 5103 - free - (2.5M) => 0 209712447 ufs/extbackup BSD (100G) 0 209712447 1 freebsd-ufs (100G) => 0 209712447 ad12s1 BSD (100G) 0 209712447 1 freebsd-ufs (100G) => 0 571705155 ufs/extstuff BSD (273G) 0 571705155 1 freebsd-ufs (273G) => 0 571705155 ad12s2 BSD (273G) 0 571705155 1 freebsd-ufs (273G) You can immediately spot another oddity - I never used glabel on this disk, but I did use tunefs -L to label the UFS filesystems within the partitions. Now it seems that the label of filesystems is also somehow recognized as a label for the whole slice. E.g. "ufs/extbackup" is exatcly the same as "ad12s1". Weird. Here's some additional data: $ ls -1 /dev/ad12* /dev/ad12 /dev/ad12s1 /dev/ad12s1a /dev/ad12s2 /dev/ad12s2a Looks usual. $ ls -1 /dev/ufs/ extbackup extbackupa extstuff extstuffa So there is one "normal" label for each filesystem and the second label for it as a filesystem in partition "a" of a labeled slice. There is nothing in /dev/label though. And a bit more: $ file -s /dev/ad12s1 /dev/ad12s1: Unix Fast File system [v2] (little-endian) last mounted on /automnt/ufs/extbackupa, volume name extbackup, last written at Tue Dec 2 17:47:21 2008, clean flag 1, readonly flag 0, number of blocks 13107027, number of data blocks 13002290, number of cylinder groups 35, block size 65536, fragment size 8192, average file size 16384, average number of files in dir 64, pending blocks to free 0, pending inodes to free 0, system-wide uuid 0, minimum percentage of free blocks 8, TIME optimization $ file -s /dev/ad12s1a /dev/ad12s1a: Unix Fast File system [v2] (little-endian) last mounted on /automnt/ufs/extbackupa, volume name extbackup, last written at Tue Dec 2 17:47:21 2008, clean flag 1, readonly flag 0, number of blocks 13107027, number of data blocks 13002290, number of cylinder groups 35, block size 65536, fragment size 8192, average file size 16384, average number of files in dir 64, pending blocks to free 0, pending inodes to free 0, system-wide uuid 0, minimum percentage of free blocks 8, TIME optimization So it looks like start of ad12s1 is the same as ad12s1a. On some better configured disks I see: $ file -s /dev/ad6s1 /dev/ad6s1: x86 boot sector; partition 4: ID=0xa5, active, starthead 0, startsector 0, 50000 sectors Ultimately I would like to fix this so that I don't see labels on the slices. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Fri Dec 5 13:11:28 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 3AAC8106564A; Fri, 5 Dec 2008 13:11:28 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 31B198FC1D; Fri, 5 Dec 2008 13:11:26 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA24872; Fri, 05 Dec 2008 15:11:25 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4939287C.3020208@icyb.net.ua> Date: Fri, 05 Dec 2008 15:11:24 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.18 (X11/20081124) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-geom@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: partition covering the whole slice [repost] 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, 05 Dec 2008 13:11:28 -0000 [Repost: I originally cc-ed gnome instead of geom; Sorry.] I have a disk with two slices and each slices has a single real partition covering the whole slice, sector-to-sector. I don't remember how I managed to configure the disk this way, is this even possible? :-) $ gpart show => 63 781422705 ad12 MBR (373G) 63 209712447 1 freebsd [active] (100G) 209712510 571705155 2 freebsd [active] (273G) 781417665 5103 - free - (2.5M) => 0 209712447 ufs/extbackup BSD (100G) 0 209712447 1 freebsd-ufs (100G) => 0 209712447 ad12s1 BSD (100G) 0 209712447 1 freebsd-ufs (100G) => 0 571705155 ufs/extstuff BSD (273G) 0 571705155 1 freebsd-ufs (273G) => 0 571705155 ad12s2 BSD (273G) 0 571705155 1 freebsd-ufs (273G) You can immediately spot another oddity - I never used glabel on this disk, but I did use tunefs -L to label the UFS filesystems within the partitions. Now it seems that the label of filesystems is also somehow recognized as a label for the whole slice. E.g. "ufs/extbackup" is exatcly the same as "ad12s1". Weird. Here's some additional data: $ ls -1 /dev/ad12* /dev/ad12 /dev/ad12s1 /dev/ad12s1a /dev/ad12s2 /dev/ad12s2a Looks usual. $ ls -1 /dev/ufs/ extbackup extbackupa extstuff extstuffa So there is one "normal" label for each filesystem and the second label for it as a filesystem in partition "a" of a labeled slice. There is nothing in /dev/label though. And a bit more: $ file -s /dev/ad12s1 /dev/ad12s1: Unix Fast File system [v2] (little-endian) last mounted on /automnt/ufs/extbackupa, volume name extbackup, last written at Tue Dec 2 17:47:21 2008, clean flag 1, readonly flag 0, number of blocks 13107027, number of data blocks 13002290, number of cylinder groups 35, block size 65536, fragment size 8192, average file size 16384, average number of files in dir 64, pending blocks to free 0, pending inodes to free 0, system-wide uuid 0, minimum percentage of free blocks 8, TIME optimization $ file -s /dev/ad12s1a /dev/ad12s1a: Unix Fast File system [v2] (little-endian) last mounted on /automnt/ufs/extbackupa, volume name extbackup, last written at Tue Dec 2 17:47:21 2008, clean flag 1, readonly flag 0, number of blocks 13107027, number of data blocks 13002290, number of cylinder groups 35, block size 65536, fragment size 8192, average file size 16384, average number of files in dir 64, pending blocks to free 0, pending inodes to free 0, system-wide uuid 0, minimum percentage of free blocks 8, TIME optimization So it looks like start of ad12s1 is the same as ad12s1a. On some better configured disks I see: $ file -s /dev/ad6s1 /dev/ad6s1: x86 boot sector; partition 4: ID=0xa5, active, starthead 0, startsector 0, 50000 sectors Ultimately I would like to fix this so that I don't see labels on the slices. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Sat Dec 6 15:38:22 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 C59E41065673 for ; Sat, 6 Dec 2008 15:38:22 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 48E318FC0A for ; Sat, 6 Dec 2008 15:38:21 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so525545fgb.35 for ; Sat, 06 Dec 2008 07:38:20 -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=07FpTQrzLl3fC2mFfLtNzYZNu3csJSBf4r/+kW92KK0=; b=XOq29pYqCWuWyIp59gN7bnvgjcVB46zUUPYHc5dfLnEcBVFfMoXpR2KZlcatVjDYc9 sSDJsRYDi5pGD/ZNDOpm5hls8S7mN/i1X7Ndu3IE32VFRfjjdYNfP6qwbyqTi+TuAiqs DWvpmQMyWaenziqfCcv+NSgphbFqPKFRYJx7Q= 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=fL4VnjCUoM/kAWfRe/oi/AkJ0nhnmYGEzFwUlzMq/wfXVbE8q2LKn1GgiQP9GzNKKY WqJtQZw1ZQjtKsHmUz7ptVDff122tgtut3We+sL8hNB8RR33Ta53+kgURjUHJ8jUk3UH B2fcZRJ8n7wAo5DJg5ugbmmL89ktWRN0wMOnM= Received: by 10.181.139.10 with SMTP id r10mr461568bkn.11.1228577900580; Sat, 06 Dec 2008 07:38:20 -0800 (PST) Received: by 10.180.236.13 with HTTP; Sat, 6 Dec 2008 07:38:20 -0800 (PST) Message-ID: <70e8236f0812060738x5e259df6la00529006c07fc23@mail.gmail.com> Date: Sat, 6 Dec 2008 15:38:20 +0000 From: "Joao Barros" To: "Doug Rabson" , "Paul Saab" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <367b2c980811191412h5e0af470k165b37edc2fc5853@mail.gmail.com> <16C31872-6A83-4FAB-AC85-213D604CDDE4@rabson.org> <367b2c980811211331v551893a8sde2231c3bc65468c@mail.gmail.com> <70e8236f0811241748w41884a12la50e4e63f83a7542@mail.gmail.com> <70e8236f0811291708h7ece06dcm1bff0081b5b0fde8@mail.gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFSBoot try and bsdlabel bootstrap code 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, 06 Dec 2008 15:38:23 -0000 On Sun, Nov 30, 2008 at 9:05 AM, Doug Rabson wrote: > > On 30 Nov 2008, at 01:08, Joao Barros wrote: > >> On Tue, Nov 25, 2008 at 1:48 AM, Joao Barros >> wrote: >>> >>> On Fri, Nov 21, 2008 at 9:31 PM, Olivier SMEDTS wrote: >>>> >>>> 2008/11/20 Doug Rabson : >>>>> >>>>> On 19 Nov 2008, at 22:12, Olivier SMEDTS wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I want to boot off a ZFS pool (version 13) on an USB stick for testing >>>>>> purposes. But I'm stuck with the bsdlabel bootstrap code size... >>>>>> I'm using a 2 hours old CURRENT. >>>>>> >>>>>> # kldload usb2_storage_mass >>>>>> # kldload zfs >>>>>> # dd if=/dev/zero of=/dev/da0 bs=512 count=32 >>>>>> # fdisk -BI da0 >>>>>> # dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 >>>>>> # bsdlabel -wB -b /boot/zfsboot da0s1 >>>>>> bsdlabel: boot code /boot/zfsboot is wrong size >>>>>> >>>>>> Is what I'm trying to do with bsdlabel wrong ? >>>>>> I previously tried with the default bootstrap code but I had an >>>>>> (expected) "boot: Not ufs" error at boot. >>>>>> >>>>>> PS : I'm not subscribed to this list. >>>>> >>>>> The process for install zfsboot is a bit manual (and undocumented). Try >>>>> something like this: >>>>> >>>>> # dd if=/boot/zfsboot of=/dev/da0s1 count=1 >>>>> # dd if=/boot/zfsboot of=/dev/ds0s1 skip=1 seek=1024 >>>>> >>>>> Alternatively, you might try using the brand new support for GPT that I >>>>> committed yesterday: >>>>> >>>>> # gpt create -f da0 >>>>> # gpt boot -b /boot/pmbr -g /boot/gptzfsboot da0 >>>>> # gpt add -t freebsd-zfs da0 >>>>> # zpool create mypool da0p2 >>>> >>>> It works ! >>>> >>>> Now I'm stuck at loader(8) prompt. >>> >>> That's a me too. >>> >>> I tried this under vmware with LOADER_ZFS_SUPPORT=yes on make.conf: >>> # gpart create -s gpt ad0 >>> # gpart add -b 34 -s 128 -t freebsd-boot ad0 >>> ad0p1 added >>> # gpart add -b 162 -s 15078327 -t freebsd-zfs ad0 >>> ad0p2 added >>> # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 >>> # zpool create tank ad0p2 >>> # zpool set bootfs = tank tank >>> >>> lsdev on loader shows: >>> cd devices: >>> disk devices: >>> disk0: BIOS drive c: >>> disk0p1: FreeBSD boot >>> disk0p2: FreeBSD ZFS >>> pxe devices: >>> zfs devices: >>> >>> Any hints? >>> >> >> >> I'm trying to figure out why loader doesn't see my zfs pool and here's >> what I got: >> >> FreeBSD/i386 boot >> Default: tank:/boot/loader >> boot: status pool: tank >> config: >> NAME STATE >> tank ONLINE >> ad0p2 ONLINE >> >> I added some printfs on loader\main.c: >> >> guid = kargs->zfspool; >> unit = zfs_guid_to_unit(guid); >> if (unit >= 0) { >> sprintf(devname, "zfs%d", unit); >> setenv("currdev", devname, 1); >> } >> >> and guid returns the correct guid for my pool but unit returns -1 >> which by looking at zfs_guid_to_unit means something is not right. >> >> Any pointers Doug? > > It looks like loader didn't manage to find the pool for some reason. This > probing process happens in sys/boot/zfs/zfs.c in the function > zfs_dev_init(). Its supposed to taste all the available disks and partitions > for the presence of a ZFS pool. The actual tasting process happens in > vdev_probe(). > > Paul Saab just commited this: http://svn.freebsd.org/changeset/base/185711 It's working now! Thank you very much to both! :-D -- Joao Barros From owner-freebsd-fs@FreeBSD.ORG Sat Dec 6 18:54:02 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 3F602106564A for ; Sat, 6 Dec 2008 18:54:02 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by mx1.freebsd.org (Postfix) with ESMTP id 05DC78FC1A for ; Sat, 6 Dec 2008 18:54:01 +0000 (UTC) (envelope-from paul.m.saab@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so508361rvf.43 for ; Sat, 06 Dec 2008 10:54:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc:sender; bh=vMUvp1ZI9OvXcfTgt7KmEsReJn2UxCLvI+s4AFiOTNg=; b=WqlzCxpw/53IZhTx7svTBDxt1tOgC73RMgdDoQd22M083D/vDTolU+C6EDiUDw9svq utfiXFqZRoeCgqA1ery6ugdPwsIpZyXp8X4pZ/Pua9PjH7B5GVEnVZKJTboQg/C4Ea0d 5cfGlrCIyhqB99KHCKMzluU9figeUmj2If/Zg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc :sender; b=SBlMCSvMfuIUIwQBrHvWVdolywUSsbs1Dt6+9fxaLXETzcDtCiyxNc2t9jtXN9LNPe Yx/j6unF8We1RAoSmCGF3ntrpaxjr583PxFIyZdYSBYWkMghBwGlLm7k95Iu9fOBErY5 1TWWUYGDMPzEg06ccec1qpqgcxgejAt04ANIg= Received: by 10.141.162.1 with SMTP id p1mr677253rvo.190.1228588223484; Sat, 06 Dec 2008 10:30:23 -0800 (PST) Received: from ?10.94.47.251? ([32.159.0.51]) by mx.google.com with ESMTPS id l31sm21665638rvb.2.2008.12.06.10.30.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 06 Dec 2008 10:30:22 -0800 (PST) References: <367b2c980811191412h5e0af470k165b37edc2fc5853@mail.gmail.com> <16C31872-6A83-4FAB-AC85-213D604CDDE4@rabson.org> <367b2c980811211331v551893a8sde2231c3bc65468c@mail.gmail.com> <70e8236f0811241748w41884a12la50e4e63f83a7542@mail.gmail.com> <70e8236f0811291708h7ece06dcm1bff0081b5b0fde8@mail.gmail.com> <70e8236f0812060738x5e259df6la00529006c07fc23@mail.gmail.com> Message-Id: <02D2F116-55EF-49D6-91C7-DE71D3AF6F55@mu.org> From: Paul Saab To: Joao Barros In-Reply-To: <70e8236f0812060738x5e259df6la00529006c07fc23@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (5G77) Mime-Version: 1.0 (iPhone Mail 5G77) Date: Sat, 6 Dec 2008 10:30:00 -0800 Sender: Paul Saab Cc: "freebsd-fs@freebsd.org" , Paul Saab Subject: Re: ZFSBoot try and bsdlabel bootstrap code 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, 06 Dec 2008 18:54:02 -0000 ya. I spent a while looking at this. when you look at the generated code it was obvious. including the wrong sys/type.h is bad On Dec 6, 2008, at 7:38 AM, "Joao Barros" wrote: > On Sun, Nov 30, 2008 at 9:05 AM, Doug Rabson wrote: >> >> On 30 Nov 2008, at 01:08, Joao Barros wrote: >> >>> On Tue, Nov 25, 2008 at 1:48 AM, Joao Barros >>> wrote: >>>> >>>> On Fri, Nov 21, 2008 at 9:31 PM, Olivier SMEDTS >>>> wrote: >>>>> >>>>> 2008/11/20 Doug Rabson : >>>>>> >>>>>> On 19 Nov 2008, at 22:12, Olivier SMEDTS wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I want to boot off a ZFS pool (version 13) on an USB stick for >>>>>>> testing >>>>>>> purposes. But I'm stuck with the bsdlabel bootstrap code size... >>>>>>> I'm using a 2 hours old CURRENT. >>>>>>> >>>>>>> # kldload usb2_storage_mass >>>>>>> # kldload zfs >>>>>>> # dd if=/dev/zero of=/dev/da0 bs=512 count=32 >>>>>>> # fdisk -BI da0 >>>>>>> # dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 >>>>>>> # bsdlabel -wB -b /boot/zfsboot da0s1 >>>>>>> bsdlabel: boot code /boot/zfsboot is wrong size >>>>>>> >>>>>>> Is what I'm trying to do with bsdlabel wrong ? >>>>>>> I previously tried with the default bootstrap code but I had an >>>>>>> (expected) "boot: Not ufs" error at boot. >>>>>>> >>>>>>> PS : I'm not subscribed to this list. >>>>>> >>>>>> The process for install zfsboot is a bit manual (and >>>>>> undocumented). Try >>>>>> something like this: >>>>>> >>>>>> # dd if=/boot/zfsboot of=/dev/da0s1 count=1 >>>>>> # dd if=/boot/zfsboot of=/dev/ds0s1 skip=1 seek=1024 >>>>>> >>>>>> Alternatively, you might try using the brand new support for >>>>>> GPT that I >>>>>> committed yesterday: >>>>>> >>>>>> # gpt create -f da0 >>>>>> # gpt boot -b /boot/pmbr -g /boot/gptzfsboot da0 >>>>>> # gpt add -t freebsd-zfs da0 >>>>>> # zpool create mypool da0p2 >>>>> >>>>> It works ! >>>>> >>>>> Now I'm stuck at loader(8) prompt. >>>> >>>> That's a me too. >>>> >>>> I tried this under vmware with LOADER_ZFS_SUPPORT=yes on make.conf: >>>> # gpart create -s gpt ad0 >>>> # gpart add -b 34 -s 128 -t freebsd-boot ad0 >>>> ad0p1 added >>>> # gpart add -b 162 -s 15078327 -t freebsd-zfs ad0 >>>> ad0p2 added >>>> # gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 >>>> # zpool create tank ad0p2 >>>> # zpool set bootfs = tank tank >>>> >>>> lsdev on loader shows: >>>> cd devices: >>>> disk devices: >>>> disk0: BIOS drive c: >>>> disk0p1: FreeBSD boot >>>> disk0p2: FreeBSD ZFS >>>> pxe devices: >>>> zfs devices: >>>> >>>> Any hints? >>>> >>> >>> >>> I'm trying to figure out why loader doesn't see my zfs pool and >>> here's >>> what I got: >>> >>> FreeBSD/i386 boot >>> Default: tank:/boot/loader >>> boot: status pool: tank >>> config: >>> NAME STATE >>> tank ONLINE >>> ad0p2 ONLINE >>> >>> I added some printfs on loader\main.c: >>> >>> guid = kargs->zfspool; >>> unit = zfs_guid_to_unit(guid); >>> if (unit >= 0) { >>> sprintf(devname, "zfs%d", unit); >>> setenv("currdev", devname, 1); >>> } >>> >>> and guid returns the correct guid for my pool but unit returns -1 >>> which by looking at zfs_guid_to_unit means something is not right. >>> >>> Any pointers Doug? >> >> It looks like loader didn't manage to find the pool for some >> reason. This >> probing process happens in sys/boot/zfs/zfs.c in the function >> zfs_dev_init(). Its supposed to taste all the available disks and >> partitions >> for the presence of a ZFS pool. The actual tasting process happens in >> vdev_probe(). >> >> > > Paul Saab just commited this: http://svn.freebsd.org/changeset/base/185711 > It's working now! Thank you very much to both! :-D > > > -- > Joao Barros