From owner-freebsd-fs@FreeBSD.ORG Sun Apr 10 17:03:14 2011 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 04478106564A for ; Sun, 10 Apr 2011 17:03:14 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward14.mail.yandex.net (forward14.mail.yandex.net [95.108.130.92]) by mx1.freebsd.org (Postfix) with ESMTP id 2BFB18FC13 for ; Sun, 10 Apr 2011 17:03:12 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward14.mail.yandex.net (Yandex) with ESMTP id 9AC6D19814B2; Sun, 10 Apr 2011 20:52:04 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1302454324; bh=zV5bc0M1I/Bjw1QF1WW+nnNFSO5zmcKFE5ptWZQa5Uo=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=WckdLDyjjJBH79amFWWUh5VKFN4JHN9JTUAiM1i7CxGDcvpgK3jG0UYfzb5bFslTB cOlXtGiU3slAWTdY+vt/CQPTYlQc5OZDkIcea1dGukAzra4bDahnAVXsSMRldVYxRW LythyGj+aKgYI5miEznvtunphDAHLdearMTqdJ6g= Received: from [178.141.6.151] (dynamic-178-141-6-151.kirov.comstar-r.ru [178.141.6.151]) by smtp13.mail.yandex.net (Yandex) with ESMTPSA id 088813898088; Sun, 10 Apr 2011 20:52:03 +0400 (MSD) Message-ID: <4DA1DFF4.6060508@yandex.ru> Date: Sun, 10 Apr 2011 20:51:00 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: warchild@space-marine.org References: <4DA0C78E.5020900@clash.no-ip.org> In-Reply-To: <4DA0C78E.5020900@clash.no-ip.org> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9E02F989B058185DD125C497" Cc: freebsd-fs@freebsd.org, Jurgen / WAR_CH|LD Subject: Re: ZFS: Booting problem with zfsboot and MBR 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, 10 Apr 2011 17:03:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9E02F989B058185DD125C497 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On 10.04.2011 00:54, Jurgen / WAR_CH|LD wrote: > Hello >=20 > Did you ever find a resolution to this problem? I have it and I really > need to fix it. What is exactly the problem? Did you see this PR? http://www.freebsd.org/cgi/query-pr.cgi?pr=3D153552 --=20 WBR, Andrey V. Elsukov --------------enig9E02F989B058185DD125C497 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJNod/1AAoJEAHF6gQQyKF6/9wH/RuaDtdva93ZoLx+CFZr6gdI dkmDgxhADrGsXQJYIb47uHEdjOkCc1rWqN2rJaETiZp+QMhN3ENiGBbTBYNublgm EHkbpLog8H98rQMnJjRnPpEygC6zEfdRKXuXHjGDKECwzhJaI1/mpOBLjRDpiS79 q/f3IxdBb+mu4gqu1tIgPA6KKuDuYkv51/ZASWPjkE49Very5z2wXFSflS0wDz6a eszsibM48xGf5R44GEMErFnKta1pG0QXWTeKMjMGjehcPW+Ryr5CFaWs1EY//lHC 6ROvFkJSfXws5DrM1iXaXcAnAENkHGYekT8OsLO/05VvUO575r7uJxeX7sFiXsU= =ATZS -----END PGP SIGNATURE----- --------------enig9E02F989B058185DD125C497-- From owner-freebsd-fs@FreeBSD.ORG Sun Apr 10 19:36:29 2011 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 2F646106566B; Sun, 10 Apr 2011 19:36:29 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 060348FC1A; Sun, 10 Apr 2011 19:36:27 +0000 (UTC) Received: by fxm11 with SMTP id 11so4226105fxm.13 for ; Sun, 10 Apr 2011 12:36:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=KyOZAmSsjuZU3q1tbNSbI4Flcnl7HSZRedPVlWIwVTs=; b=ohFrU7IhQIhND9zMUaT8Z68aHGDyNrehgjkq/D33Wm6Q5HW12PNTDHMUlbgg0KIToe TD6dG36rWvcnDi9OHx1hxIFOVCKym4TTrsBYbrSHXzxk43w5qyUdOAlgX1mjwnWXp7fq qtATBxKoKx9snLT1Yaj4XN9YQMHlpZx53vVA4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=ov2ZQbw+RoN9yQ57EYmcipRnowH+imMzp+mHbbCy0I7NMdieIz6U88hdbo2ugbJAd1 9248gi1eh9DMiCSm2b6kMxAR7fNVbjBJuVDueeRuHj8t69wF5dXdjmsBmaZU3s9bWreL Wtzw+kY7Gllanl3uncGhxEtlWYobUnYzWU+r4= Received: by 10.223.23.195 with SMTP id s3mr1453799fab.83.1302464187046; Sun, 10 Apr 2011 12:36:27 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id t2sm1377341faa.23.2011.04.10.12.36.23 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2011 12:36:24 -0700 (PDT) From: Mikolaj Golub To: Freddie Cash References: <20110402084431.GB1849@garage.freebsd.pl> X-Comment-To: Freddie Cash Sender: Mikolaj Golub Date: Sun, 10 Apr 2011 22:36:22 +0300 In-Reply-To: (Freddie Cash's message of "Mon, 4 Apr 2011 11:08:16 -0700") Message-ID: <86aafxx5jd.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: FreeBSD Filesystems , FreeBSD Stable , FreeBSD-Current , Pawel Jakub Dawidek Subject: Re: Any success stories for HAST + ZFS? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2011 19:36:29 -0000 On Mon, 4 Apr 2011 11:08:16 -0700 Freddie Cash wrote: FC> Once the deadlock patches above are MFC'd to -STABLE, I can do an FC> upgrade cycle and test them. Committed to STABLE. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Sun Apr 10 21:30:12 2011 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 0BA40106566B for ; Sun, 10 Apr 2011 21:30:12 +0000 (UTC) (envelope-from warchild@clash.no-ip.org) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id BDAD88FC14 for ; Sun, 10 Apr 2011 21:30:11 +0000 (UTC) Received: from ip-211.ish.com.au ([203.29.62.211]:28346 helo=ish.com.au) by fish.ish.com.au with esmtp (Exim 4.69) (envelope-from ) id 1Q92Cr-0000oV-1C; Mon, 11 Apr 2011 07:30:05 +1000 Received: from [203.29.62.154] (HELO ip-154.ish.com.au) by ish.com.au (CommuniGate Pro SMTP 5.4c3h) with ESMTP id 7065118; Mon, 11 Apr 2011 07:30:04 +1000 X-CTCH-RefID: str=0001.0A150204.4DA2215D.00CC,ss=1,fgs=0 Message-ID: <4DA2215C.30700@clash.no-ip.org> Date: Mon, 11 Apr 2011 07:30:04 +1000 From: Jurgen / WAR_CH|LD User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: "Andrey V. Elsukov" References: <4DA0C78E.5020900@clash.no-ip.org> <4DA1DFF4.6060508@yandex.ru> In-Reply-To: <4DA1DFF4.6060508@yandex.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 10 Apr 2011 22:25:50 +0000 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Booting problem with zfsboot and MBR X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: warchild@space-marine.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2011 21:30:12 -0000 Thanks. I had two disks in a mirror, and no reason to be using MBR. So I removed one disk from the array, repartitioned using GPT brought it back into the mirror and then completed the other drive (I completed all of this off the livefs fixit). Once I copied the zpool.cache over my system booted again. Thanks. Jurgen On 11/04/11 2:51 AM, Andrey V. Elsukov wrote: > On 10.04.2011 00:54, Jurgen / WAR_CH|LD wrote: >> Hello >> >> Did you ever find a resolution to this problem? I have it and I really >> need to fix it. > > What is exactly the problem? Did you see this PR? > http://www.freebsd.org/cgi/query-pr.cgi?pr=153552 > -- -------------------------------> Jurgen / WAR_CH|LD warchild@clash.no-ip.org http://clash.no-ip.org From owner-freebsd-fs@FreeBSD.ORG Mon Apr 11 11:07:01 2011 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 1097C1065673 for ; Mon, 11 Apr 2011 11:07:01 +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 D992A8FC19 for ; Mon, 11 Apr 2011 11:07:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3BB70Om025869 for ; Mon, 11 Apr 2011 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3BB70KY025867 for freebsd-fs@FreeBSD.org; Mon, 11 Apr 2011 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Apr 2011 11:07:00 GMT Message-Id: <201104111107.p3BB70KY025867@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, 11 Apr 2011 11:07:01 -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/156241 fs [zfs] 'zfs send' does not prevents disks to suspend if o kern/156193 fs [ufs] [hang] UFS snapshot hangs && deadlocks processes o kern/156168 fs [nfs] [panic] Kernel panic under concurrent access ove o kern/156039 fs [nullfs] [unionfs] nullfs + unionfs do not compose, re o kern/155940 fs [libzfs] [patch] zfs list /filesystem does not work. o kern/155615 fs [zfs] zfs v28 broken on sparc64 -current o kern/155587 fs [zfs] [panic] kernel panic with zfs o kern/155484 fs [ufs] GPT + UFS boot don't work well together o kern/155411 fs [regression] [8.2-release] [tmpfs]: mount: tmpfs : No o kern/155199 fs [ext2fs] ext3fs mounted as ext2fs gives I/O errors o bin/155104 fs [zfs][patch] use /dev prefix by default when importing o kern/154930 fs [zfs] cannot delete/unlink file from full volume -> EN o kern/154828 fs [msdosfs] Unable to create directories on external USB o kern/154491 fs [smbfs] smb_co_lock: recursive lock for object 1 o kern/154447 fs [zfs] [panic] Occasional panics - solaris assert somew f kern/154228 fs [md] md getting stuck in wdrain state o kern/153996 fs [zfs] zfs root mount error while kernel is not located o kern/153847 fs [nfs] [panic] Kernel panic from incorrect m_free in nf o kern/153753 fs [zfs] ZFS v15 - grammatical error when attempting to u o kern/153716 fs [zfs] zpool scrub time remaining is incorrect o kern/153695 fs [patch] [zfs] Booting from zpool created on 4k-sector o kern/153680 fs [xfs] 8.1 failing to mount XFS partitions o kern/153520 fs [zfs] Boot from GPT ZFS root on HP BL460c G1 unstable o kern/153418 fs [zfs] [panic] Kernel Panic occurred writing to zfs vol o kern/153351 fs [zfs] locking directories/files in ZFS o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small p kern/152488 fs [tmpfs] [patch] mtime of file updated when only inode o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o kern/151845 fs [smbfs] [patch] smbfs should be upgraded to support Un o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/150207 fs zpool(1): zpool import -d /dev tries to open weird dev o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa f kern/149022 fs [hang] File system operations hangs with suspfs state o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs p bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic p kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [ffs] [snapshot] System crashes when manipulat o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 223 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Apr 11 18:26:17 2011 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 5C5DA1065670; Mon, 11 Apr 2011 18:26:17 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id C17398FC08; Mon, 11 Apr 2011 18:26:16 +0000 (UTC) Received: by yie12 with SMTP id 12so2687750yie.13 for ; Mon, 11 Apr 2011 11:26:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UJMMtolQWTT4fQ+9HTtbK9IgHf+m4L3tOdO3FJZHnrg=; b=MNE9uyrVxcJtlR7L0JaYR8sVI7oPUELKT9A+jbpqBt0eWXK1X3STrahSw3iqlJc9jV Swt+OCC9UOu0p33CTdPDix7nocXIayziRJpndos27+dSI1g83kVeZ5DKB5+y8cWR5GTN jv1OWzXf1UU4Bx8W86+T69nIGCjcyaYn44iDE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qAvmKvB7awCxquNEzj649QG6PEFhytT17BT6ABjQO34Hu0cfkQ7JI9PQnHhkV4eO/v WxBdFypln28Iq0IyAsJwT4yIFr1tEVSpDphJcSPHwILezH7yD3B3HlMUX8QEmxllZdD0 2nxe6gZcMRwNi0XikDjfaKUei+kL5H/PJLrIM= MIME-Version: 1.0 Received: by 10.90.249.25 with SMTP id w25mr3166759agh.55.1302546375731; Mon, 11 Apr 2011 11:26:15 -0700 (PDT) Received: by 10.90.67.9 with HTTP; Mon, 11 Apr 2011 11:26:15 -0700 (PDT) In-Reply-To: <86aafxx5jd.fsf@kopusha.home.net> References: <20110402084431.GB1849@garage.freebsd.pl> <86aafxx5jd.fsf@kopusha.home.net> Date: Mon, 11 Apr 2011 11:26:15 -0700 Message-ID: From: Freddie Cash To: Mikolaj Golub Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Filesystems , FreeBSD Stable , FreeBSD-Current , Pawel Jakub Dawidek Subject: Re: Any success stories for HAST + ZFS? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2011 18:26:17 -0000 On Sun, Apr 10, 2011 at 12:36 PM, Mikolaj Golub wrote= : > On Mon, 4 Apr 2011 11:08:16 -0700 Freddie Cash wrote: > =C2=A0FC> Once the deadlock patches above are MFC'd to -STABLE, I can do = an > =C2=A0FC> upgrade cycle and test them. > > Committed to STABLE. Updated src tree to r220537. Recompiled world, kernel, etc. Installed world, kernel, etc. ZFSv28 patch was not affected. Everything is detected correctly, everything comes up correctly. See a new option (reload) in the RC script for hast. Can create/change role for 24 hast devices simultaneously. Can switch between master/slave modes. Have 5 rsyncs running in parallel without any issues, transferring 80-120 Mbps over the network (just under 100 Mbps seems to be the average right now). Switching roles while the rsyncs are running succeeds without deadlocking (obviously, rsync complains a whole bunch while the switch happens as the pool disappears out from underneath it, but it picks up again when the pool is back in place). Hitting the reset switch on the box while the rsyncs are running doesn't affect the hast devices or the pool, beyond losing the last 5 seconds of writes. It's only been a couple of hours of testing and hammering, but so far things are much more stable/performant than before. Anything else I should test? --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Mon Apr 11 19:52:44 2011 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 9E2041065677; Mon, 11 Apr 2011 19:52:44 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3EB9F8FC08; Mon, 11 Apr 2011 19:52:43 +0000 (UTC) Received: by bwz12 with SMTP id 12so6206625bwz.13 for ; Mon, 11 Apr 2011 12:52:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type:content-transfer-encoding; bh=kXIXPANkKpQfDqNW8Pj3qaLyTIsoM6htLetHO/WepfM=; b=GkXOfFDsMseHPfCbnfV05SMG63JFgMyNdjrU3qz/eiHxSChcDFk7z+8QorA2aXDyk4 b115IhM4Vu/6WO1nIKjyFn3+viqXL4Logymdz47Rkl1iK5hgpY2uaJ6Te4tDyg9c+foJ I/qofbOfLwT3bD4dmNuCuk8Q7tMI2+UII/ZyI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type :content-transfer-encoding; b=kEIoJBv+Jxh+KJFQ0dzA0L2IUtnEKySaFI07inqX/cZn7S6m/gyOSotY50Fm2o9I6t jDjtdtrhoAqTB6/lWxG/bATgH6OKYOLEZq9rLx91q7JbuJcD2Oqvbbk4B1/gsor7ctCp AanzG2HzMG0XS2B6v2t1/Oqjmjubdarzl3sOM= Received: by 10.204.19.80 with SMTP id z16mr1150205bka.198.1302551562281; Mon, 11 Apr 2011 12:52:42 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id l1sm3411966bkl.1.2011.04.11.12.52.39 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Apr 2011 12:52:40 -0700 (PDT) From: Mikolaj Golub To: Freddie Cash References: <20110402084431.GB1849@garage.freebsd.pl> <86aafxx5jd.fsf@kopusha.home.net> X-Comment-To: Freddie Cash Sender: Mikolaj Golub Date: Mon, 11 Apr 2011 22:52:37 +0300 In-Reply-To: (Freddie Cash's message of "Mon, 11 Apr 2011 11:26:15 -0700") Message-ID: <867hb0tvju.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Cc: Mikolaj Golub , FreeBSD Filesystems , FreeBSD-Current , Pawel Jakub Dawidek , FreeBSD Stable Subject: Re: Any success stories for HAST + ZFS? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2011 19:52:44 -0000 On Mon, 11 Apr 2011 11:26:15 -0700 Freddie Cash wrote: FC> On Sun, Apr 10, 2011 at 12:36 PM, Mikolaj Golub wrote: >> On Mon, 4 Apr 2011 11:08:16 -0700 Freddie Cash wrote: >> šFC> Once the deadlock patches above are MFC'd to -STABLE, I can do an >> šFC> upgrade cycle and test them. >> >> Committed to STABLE. FC> Updated src tree to r220537. Recompiled world, kernel, etc. FC> Installed world, kernel, etc. ZFSv28 patch was not affected. FC> Everything is detected correctly, everything comes up correctly. See FC> a new option (reload) in the RC script for hast. FC> Can create/change role for 24 hast devices simultaneously. FC> Can switch between master/slave modes. FC> Have 5 rsyncs running in parallel without any issues, transferring FC> 80-120 Mbps over the network (just under 100 Mbps seems to be the FC> average right now). FC> Switching roles while the rsyncs are running succeeds without FC> deadlocking (obviously, rsync complains a whole bunch while the switch FC> happens as the pool disappears out from underneath it, but it picks up FC> again when the pool is back in place). FC> Hitting the reset switch on the box while the rsyncs are running FC> doesn't affect the hast devices or the pool, beyond losing the last 5 FC> seconds of writes. FC> It's only been a couple of hours of testing and hammering, but so far FC> things are much more stable/performant than before. Cool! Thanks for reporting! FC> Anything else I should test? Nothing particular, but any tests and reports are appreciated. E.g. ones of the recent features Pawel has added are checksum and compression. You could try different options and compare :-) -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Tue Apr 12 08:37:28 2011 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 93BDB106566C; Tue, 12 Apr 2011 08:37:28 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (constantine.ingresso.co.uk [IPv6:2001:470:1f09:176e::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5EAA08FC0C; Tue, 12 Apr 2011 08:37:28 +0000 (UTC) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ingresso.co.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1Q9Z6E-000623-Ju; Tue, 12 Apr 2011 09:37:26 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.74 (FreeBSD)) (envelope-from ) id 1Q9Z6E-0002qY-J0; Tue, 12 Apr 2011 09:37:26 +0100 To: fjwcash@gmail.com, trociny@freebsd.org In-Reply-To: Message-Id: From: Pete French Date: Tue, 12 Apr 2011 09:37:26 +0100 Cc: freebsd-fs@freebsd.org, pjd@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Any success stories for HAST + ZFS? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2011 08:37:28 -0000 > Everything is detected correctly, everything comes up correctly. See > a new option (reload) in the RC script for hast. same here - have patched the master databse achines, all came up fine, everything running erfectly, have flip-flopped between the two machines with no ill effects whatsoever, and all looking very good. cheers, -pete. From owner-freebsd-fs@FreeBSD.ORG Tue Apr 12 19:20:12 2011 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 4D71E106566B for ; Tue, 12 Apr 2011 19:20:12 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id D9F948FC0C for ; Tue, 12 Apr 2011 19:20:10 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 8F72945EE6; Tue, 12 Apr 2011 21:20:08 +0200 (CEST) Received: from localhost (host-80-54-90-198.eimg.pl [80.54.90.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 41E8E45E93; Tue, 12 Apr 2011 21:20:03 +0200 (CEST) Date: Tue, 12 Apr 2011 21:19:51 +0200 From: Pawel Jakub Dawidek To: linimon@FreeBSD.org Message-ID: <20110412191951.GR40382@garage.freebsd.pl> References: <201104092010.p39KACms029143@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="//h4sZKAxcnndsN6" Content-Disposition: inline In-Reply-To: <201104092010.p39KACms029143@freefall.freebsd.org> X-OS: FreeBSD 9.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.5 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/156241: [zfs] 'zfs send' does not prevents disks to suspend if no other activity 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, 12 Apr 2011 19:20:12 -0000 --//h4sZKAxcnndsN6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 09, 2011 at 08:10:12PM +0000, linimon@FreeBSD.org wrote: > Old Synopsis: 'zfs send' does not prevents disks to suspend if no other a= ctivity > New Synopsis: [zfs] 'zfs send' does not prevents disks to suspend if no o= ther activity >=20 > Responsible-Changed-From-To: freebsd-bugs->freebsd-fs > Responsible-Changed-By: linimon > Responsible-Changed-When: Sat Apr 9 20:09:50 UTC 2011 > Responsible-Changed-Why:=20 > Over to maintainer(s). >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D156241 This looks like a problem with mfi(4) and not ZFS. Mark would you mind reassigning this PR to mfi(4) maintainer or proper mailing list (freebsd-hardware?)? Thanks. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --//h4sZKAxcnndsN6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk2kpdcACgkQForvXbEpPzQjPgCgvX8asp+Au9BKFBJ/5LSUWwK0 KL0An24Q4HP/FdLWus2V+7On4qDLOtln =yPwm -----END PGP SIGNATURE----- --//h4sZKAxcnndsN6-- From owner-freebsd-fs@FreeBSD.ORG Tue Apr 12 20:32:14 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AB421065670; Tue, 12 Apr 2011 20:32:14 +0000 (UTC) (envelope-from pjd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 619BC8FC08; Tue, 12 Apr 2011 20:32:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3CKWEJU091896; Tue, 12 Apr 2011 20:32:14 GMT (envelope-from pjd@freefall.freebsd.org) Received: (from pjd@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3CKWDxS091883; Tue, 12 Apr 2011 20:32:13 GMT (envelope-from pjd) Date: Tue, 12 Apr 2011 20:32:13 GMT Message-Id: <201104122032.p3CKWDxS091883@freefall.freebsd.org> To: koie@suri.co.jp, pjd@FreeBSD.org, freebsd-fs@FreeBSD.org, pjd@FreeBSD.org From: pjd@FreeBSD.org Cc: Subject: Re: kern/155940: [libzfs] [patch] zfs list /filesystem does not work. 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, 12 Apr 2011 20:32:14 -0000 Synopsis: [libzfs] [patch] zfs list /filesystem does not work. State-Changed-From-To: open->closed State-Changed-By: pjd State-Changed-When: wto 12 kwi 2011 20:31:13 UTC State-Changed-Why: Fix committed to HEAD, thanks! Responsible-Changed-From-To: freebsd-fs->pjd Responsible-Changed-By: pjd Responsible-Changed-When: wto 12 kwi 2011 20:31:13 UTC Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=155940 From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 05:48:21 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96ACC106564A; Wed, 13 Apr 2011 05:48:21 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 701D78FC08; Wed, 13 Apr 2011 05:48:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3D5mLpK096347; Wed, 13 Apr 2011 05:48:21 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3D5mLDZ096342; Wed, 13 Apr 2011 05:48:21 GMT (envelope-from remko) Date: Wed, 13 Apr 2011 05:48:21 GMT Message-Id: <201104130548.p3D5mLDZ096342@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-fs@FreeBSD.org, freebsd-hardware@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: kern/156241: [mfi] 'zfs send' does not prevents disks to suspend if no other activity 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, 13 Apr 2011 05:48:21 -0000 Old Synopsis: [zfs] 'zfs send' does not prevents disks to suspend if no other activity New Synopsis: [mfi] 'zfs send' does not prevents disks to suspend if no other activity Responsible-Changed-From-To: freebsd-fs->freebsd-hardware Responsible-Changed-By: remko Responsible-Changed-When: Wed Apr 13 05:47:55 UTC 2011 Responsible-Changed-Why: Pawel says this might be hardware related, assign it to that group and tag the ticket as [mfi]. http://www.freebsd.org/cgi/query-pr.cgi?pr=156241 From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 07:52:38 2011 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 21F31106564A for ; Wed, 13 Apr 2011 07:52:38 +0000 (UTC) (envelope-from mailing.lists@streamvia.net) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by mx1.freebsd.org (Postfix) with ESMTP id C2A3B8FC0A for ; Wed, 13 Apr 2011 07:52:37 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs01.streamvia.com (Postfix) with ESMTP id 632331437C5 for ; Wed, 13 Apr 2011 08:33:51 +0100 (BST) X-Virus-Scanned: amavisd-new at zcs01.streamvia.com Received: from zcs01.streamvia.com ([127.0.0.1]) by localhost (zcs01.streamvia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4VEMjYhrOUhS for ; Wed, 13 Apr 2011 08:33:48 +0100 (BST) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by zcs01.streamvia.com (Postfix) with ESMTP id 8EB5C1437CA for ; Wed, 13 Apr 2011 08:33:48 +0100 (BST) Date: Wed, 13 Apr 2011 08:33:48 +0100 (BST) From: Mailing Lists Sender: ed.stout@streamvia.net To: freebsd-fs@freebsd.org Message-ID: In-Reply-To: <202b7a73-bc0f-4c58-9c2a-8c9c42e66394@zcs01> MIME-Version: 1.0 X-Originating-IP: [212.119.4.226] X-Mailer: Zimbra 7.0.1_GA_3105 (ZimbraWebClient - SAF3 (Win)/7.0.1_GA_3105) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: siisch0: Timeout on slot 30 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ed S List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2011 07:52:38 -0000 Morning All, I see there has been a few threads relating to something similar, specifically around port multiplier time outs using the SIIS module, with a patch even provided at one point - however this patch doesnt appear to be valid any more, 2 of the 3 chunks are already in the 8.2 release and from checking the cvs logs; when i try to apply, avoiding the roll back, 1 chunk does apply. I think the patch does make some difference, in that it doesnt make the disks stall for as long as frequently but the errors still appear in the logs. Currently running FreeBSD 8.2-RELEASE, with the zfs v28 patch. The main chassis has a Silicon Image 3124 in, with an estata port - connected to the esata port is another disk shelf with 5 disks in, all in one raidz pool. When i run a scrub on the external esata shelf, i see time outs in my logs: siisch0: Error while READ LOG EXT siisch0: Error while READ LOG EXT siisch0: Timeout on slot 30 siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 siisch0: ... waiting for slots 04440000 siisch0: Timeout on slot 26 siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 siisch0: ... waiting for slots 00440000 siisch0: Timeout on slot 22 siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 siisch0: ... waiting for slots 00040000 siisch0: Timeout on slot 18 siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 siisch0: Error while READ LOG EXT siisch0: Error while READ LOG EXT siisch0 is the port multiplier , the slot number seems crazy to me (as i dont have 30 slots, theres only 5 in the external shelf) - although im not sure if this references something else. I dont believe this is a hardware problem, ive tried with replacement devices/controller cards, still see the above. Anyone else seeing this or have any thoughts? Thanks, Ed From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 08:59:40 2011 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 093D71065670 for ; Wed, 13 Apr 2011 08:59:40 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id E4BC68FC14 for ; Wed, 13 Apr 2011 08:59:39 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta03.emeryville.ca.mail.comcast.net with comcast id WwwS1g0021smiN4A3wzfJH; Wed, 13 Apr 2011 08:59:39 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta20.emeryville.ca.mail.comcast.net with comcast id Wwze1g00A1t3BNj8gwzepk; Wed, 13 Apr 2011 08:59:39 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 496AF9B42B; Wed, 13 Apr 2011 01:59:38 -0700 (PDT) Date: Wed, 13 Apr 2011 01:59:38 -0700 From: Jeremy Chadwick To: Mailing Lists Message-ID: <20110413085938.GA51187@icarus.home.lan> References: <202b7a73-bc0f-4c58-9c2a-8c9c42e66394@zcs01> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: siisch0: Timeout on slot 30 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, 13 Apr 2011 08:59:40 -0000 On Wed, Apr 13, 2011 at 08:33:48AM +0100, Mailing Lists wrote: > Morning All, > > > I see there has been a few threads relating to something similar, specifically around port multiplier time outs using the SIIS module, with a patch even provided at one point - however this patch doesnt appear to be valid any more, 2 of the 3 chunks are already in the 8.2 release and from checking the cvs logs; when i try to apply, avoiding the roll back, 1 chunk does apply. I think the patch does make some difference, in that it doesnt make the disks stall for as long as frequently but the errors still appear in the logs. > > Currently running FreeBSD 8.2-RELEASE, with the zfs v28 patch. The main chassis has a Silicon Image 3124 in, with an estata port - connected to the esata port is another disk shelf with 5 disks in, all in one raidz pool. When i run a scrub on the external esata shelf, i see time outs in my logs: > > > > siisch0: Error while READ LOG EXT > siisch0: Error while READ LOG EXT > siisch0: Timeout on slot 30 > siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 > siisch0: ... waiting for slots 04440000 > siisch0: Timeout on slot 26 > siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 > siisch0: ... waiting for slots 00440000 > siisch0: Timeout on slot 22 > siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 > siisch0: ... waiting for slots 00040000 > siisch0: Timeout on slot 18 > siisch0: siis_timeout is 03040000 ss 44440000 rs 44440000 es 00000000 sts 801f2040 serr 00280000 > siisch0: Error while READ LOG EXT > siisch0: Error while READ LOG EXT > > > siisch0 is the port multiplier , the slot number seems crazy to me (as i dont have 30 slots, theres only 5 in the external shelf) - although im not sure if this references something else. I dont believe this is a hardware problem, ive tried with replacement devices/controller cards, still see the above. > > Anyone else seeing this or have any thoughts? I cannot help you with your problem, but I can help reduce your confusion regarding "slot numbers seeming crazy". Based on a analysis of the src/sys/dev/siis code, there is no 1:1 relation between a slot number and a disk/port/drive-bay/device. "Slot" in this context means something completely different; do not correlate the two things[1]. I don't know what "slot" means in this context; mav@ will know for certain. Take a look at src/sys/dev/siis/siis.h, specifically the "struct siis_channel" structure. You'll see there are multiple "slots" (declared as struct siis_slot) per channel. Each slot appears to have its own identification number -- in the kernel printf(), it's referred to as slot->slot. Thus: channel->slot[X]->slot Your controller has multiple channels -- and each channel can have up to 256 (0-255) slots. Each slot has a separate DMA channel associated with it, as well as a separate CCB, and a separate timeout value. There can be up to 256 (0-255) "slots" assigned to an individual SATA controller channel. A channel on SATA usually correlates (1:1) to a disk, but I don't know how port multipliers fit into the picture (I do on a physical level, just not on a software level). Controller channels can also have their own DMA channel (see [1] again). This is pretty cool from a performance perspective; I'd never looked at siis until now. Anyway, point being: slot != SATA port. Hopefully that relieves your concern there. [1]: Anyone working with technology needs to accept the fact that there are too many words in the English language that are synonyms for "thing". Common tech terms for such: index, slot, port, channel, bay, tag, port, bus, volume, and even LUN (yes, as in SCSI LUN). I'm forgetting some commonly-used others. When these terms are used with someone who lacks context of what the term actually refers to (on a technical/software/hardware level), confusion guaranteed. Am I recommending the printf()s be changed? Absolutely not. Just know that slot != SATA port. Regarding LUN: I still see people correlating (1:1) a LUN with a disk. When you introduce these people to SANs, where a LUN often consists of multiple devices (commonly disks), confusion is guaranteed. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 09:26:40 2011 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 BAF8A106566C for ; Wed, 13 Apr 2011 09:26:39 +0000 (UTC) (envelope-from mailing.lists@streamvia.net) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by mx1.freebsd.org (Postfix) with ESMTP id 7C9428FC17 for ; Wed, 13 Apr 2011 09:26:39 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs01.streamvia.com (Postfix) with ESMTP id 0003F1437F6; Wed, 13 Apr 2011 10:26:37 +0100 (BST) X-Virus-Scanned: amavisd-new at zcs01.streamvia.com Received: from zcs01.streamvia.com ([127.0.0.1]) by localhost (zcs01.streamvia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQBmIrGwnf08; Wed, 13 Apr 2011 10:26:31 +0100 (BST) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by zcs01.streamvia.com (Postfix) with ESMTP id AAE1B1437F5; Wed, 13 Apr 2011 10:26:31 +0100 (BST) Date: Wed, 13 Apr 2011 10:26:31 +0100 (BST) From: Ed S Sender: ed.stout@streamvia.net To: Jeremy Chadwick Message-ID: <7f0ad987-7a90-4904-8160-4932f6b9c2ae@zcs01> In-Reply-To: <20110413085938.GA51187@icarus.home.lan> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Originating-IP: [212.119.4.226] X-Mailer: Zimbra 7.0.1_GA_3105 (ZimbraWebClient - SAF3 (Win)/7.0.1_GA_3105) Cc: freebsd-fs@freebsd.org Subject: Re: siisch0: Timeout on slot 30 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, 13 Apr 2011 09:26:40 -0000 > I cannot help you with your problem, but I can help reduce your > confusion regarding "slot numbers seeming crazy". Thanks for the reply, interesting reading - hopefully someone else will have seen something similar, or at least how to progress troubleshooting further :) From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 15:35:42 2011 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 A27F41065672 for ; Wed, 13 Apr 2011 15:35:42 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [64.81.247.49]) by mx1.freebsd.org (Postfix) with ESMTP id 59CC18FC13 for ; Wed, 13 Apr 2011 15:35:40 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id p3DF5tPa015944; Wed, 13 Apr 2011 08:05:56 -0700 (PDT) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201104131505.p3DF5tPa015944@chez.mckusick.com> To: Sergi Seira In-reply-to: <4DA45042.5060204@cdmon.com> Date: Wed, 13 Apr 2011 08:05:55 -0700 From: Kirk McKusick X-Spam-Status: No, score=0.0 required=5.0 tests=MISSING_MID, UNPARSEABLE_RELAY autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on chez.mckusick.com Cc: freebsd-fs@freebsd.org Subject: Re: background fsck high load on 8.1 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, 13 Apr 2011 15:35:42 -0000 > Date: Tue, 12 Apr 2011 15:14:42 +0200 > From: Sergi Seira > To: freebsd-current@freebsd.org > Subject: background fsck high load on 8.1 > > Hello, > > We've experienced that background fsck on 8.1 degrades server > performance on a higher degree than in previous fbsd versions (6.3, > 7.3; amd64). > > We've noticed it after upgrading - same hardware - to a 8.1-RELEASE. > Now, performance of other services (i.e. apache, mysql) during a > background fsck falls miserably. > > Is there any way to calm fsck down?, nice(1)?, some sysctl? > > We have also gmirror, but we prevent to rebuild it if there is a > fsck running in background. > > Thanks for your help, > regards, > Sergi This is the first report that I have heard of the higher level of slowdown by background fsck on 8.X systems. My guess is that it comes about from work done to make the I/O subsystem faster which in turn allows fsck to have a higher impact. For a period we were working on a kernel feature (associated with nice) that would allow the system to throttle I/O activity for a given process. It turns out to be a much harder problem than it at first appears. We set this aside when we got journaled soft updates working as they eliminate the need for background fsck. While journaled soft updates are too big of a change to be merged back into the 8.X tree, we do expect them to be used by default on 9.X systems. Kirk McKusick From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 17:04:18 2011 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 7C991106566C for ; Wed, 13 Apr 2011 17:04:18 +0000 (UTC) (envelope-from kungfujesus06@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 10F8F8FC12 for ; Wed, 13 Apr 2011 17:04:17 +0000 (UTC) Received: by fxm11 with SMTP id 11so797424fxm.13 for ; Wed, 13 Apr 2011 10:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=dFXnbPTu2MnuZ4UiBMjxg611BcqBsEPEP8hNeZitWJQ=; b=W7dmykmLijWJIajgztHw2Tb71SM/Y3wf7nC/+11I+DrmQ6Vv5UgAD2RvIssUYbGnDJ ab6wqjnoabCFRfsQ2KIvSKz/s0yISOBWqJbUvRBpoeUmfakvJkWoK37Bgi6p7AtDK6Do +0VqW0oHR1UWcxmtmS9J/oaQAVq8JkLkIcQUM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=tqgRl/3eYTew5RjOYw5ieq5jwffIzZiMdb32ruVdSvSnspEBCNVAsucEBrUOsFEIly 1qaL1fqDk6H95L8UBqRFvmEPNLDs7HzZmJ/kZ1edLmgYKjQVhl0vziIfrIAkPIWARNFq NRnHER/ffedDQrgywAs+058DTaOh//TgjUvOo= MIME-Version: 1.0 Received: by 10.223.160.8 with SMTP id l8mr1342253fax.114.1302714256956; Wed, 13 Apr 2011 10:04:16 -0700 (PDT) Received: by 10.223.118.204 with HTTP; Wed, 13 Apr 2011 10:04:16 -0700 (PDT) Date: Wed, 13 Apr 2011 13:04:16 -0400 Message-ID: From: Adam Stylinski To: koie@suri.co.jp Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: siisch0: Timeout on slot 30 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, 13 Apr 2011 17:04:18 -0000 I've encountered similar situations with my Silicon Image SATA controller which uses internally a SATA port multiplier for the E-SATA ports. When used in conjunction with enough disks I'd constantly get these issues. In short I'd avoid port multipliers until a proper bug fix has been found for this driver. From owner-freebsd-fs@FreeBSD.ORG Wed Apr 13 17:39:29 2011 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 8F525106564A for ; Wed, 13 Apr 2011 17:39:29 +0000 (UTC) (envelope-from mailing.lists@streamvia.net) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by mx1.freebsd.org (Postfix) with ESMTP id 4DBC98FC14 for ; Wed, 13 Apr 2011 17:39:28 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs01.streamvia.com (Postfix) with ESMTP id 181A8143848; Wed, 13 Apr 2011 18:39:28 +0100 (BST) X-Virus-Scanned: amavisd-new at zcs01.streamvia.com Received: from zcs01.streamvia.com ([127.0.0.1]) by localhost (zcs01.streamvia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id muXmwGoipJ9C; Wed, 13 Apr 2011 18:39:20 +0100 (BST) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by zcs01.streamvia.com (Postfix) with ESMTP id 99FC8143855; Wed, 13 Apr 2011 18:39:20 +0100 (BST) Date: Wed, 13 Apr 2011 18:39:20 +0100 (BST) From: Ed S To: Adam Stylinski Message-ID: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Originating-IP: [81.187.15.18] X-Mailer: Zimbra 7.0.1_GA_3105 (ZimbraWebClient - SAF3 (Mac)/7.0.1_GA_3105) Cc: freebsd-fs@freebsd.org, koie@suri.co.jp Subject: Re: siisch0: Timeout on slot 30 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, 13 Apr 2011 17:39:29 -0000 > I've encountered similar situations with my Silicon Image SATA > controller > which uses internally a SATA port multiplier for the E-SATA ports. > When > used in conjunction with enough disks I'd constantly get these > issues. In > short I'd avoid port multipliers until a proper bug fix has been > found for > this driver. I found this in the webcvs and thought there might some relation - although im not seeing the panic: http://lists.freebsd.org/pipermail/freebsd-fs/2010-September/009438.html Revision 1.1.2.30: download - view: text, markup, annotated - select for diffs Thu Sep 30 04:23:03 2010 UTC (6 months, 1 week ago) by mav Branches: RELENG_8 Diff to: previous 1.1.2.29: preferred, colored; branchpoint 1.1: preferred, colored Changes since revision 1.1.2.29: +8 -5 lines SVN rev 213293 on 2010-09-30 04:23:03Z by mav MFC r212732: Fix panic, when due to some kind of congestion on FIS-based switching port multiplier some command triggers false positive timeout, but then completes normally. Also saw this was the list where mav@ posted a patch previously, i dont see anything in the commit logs that might fix this issue in current/head. But might boot it up and see... Thanks, Ed From owner-freebsd-fs@FreeBSD.ORG Thu Apr 14 11:13:20 2011 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 25C48106566B for ; Thu, 14 Apr 2011 11:13:20 +0000 (UTC) (envelope-from s.seira@cdmon.com) Received: from correo.cdmon.com (correo.cdmon.com [212.36.82.9]) by mx1.freebsd.org (Postfix) with ESMTP id CE8878FC20 for ; Thu, 14 Apr 2011 11:13:19 +0000 (UTC) Received: from genocida (localhost.cdmon.com [127.0.0.1]) by correo.cdmon.com (Postfix) with ESMTP id 68284130CF3 for ; Thu, 14 Apr 2011 12:54:28 +0200 (CEST) Received: from antispam (localhost.cdmon.com [127.0.0.1]) by correo.cdmon.com (Postfix) with ESMTP id 191F2130C2B for ; Thu, 14 Apr 2011 12:54:28 +0200 (CEST) Received: from [192.168.0.30] (155.Red-88-2-251.staticIP.rima-tde.net [88.2.251.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by correo.cdmon.com (Postfix) with ESMTP id BC7F9130C1C; Thu, 14 Apr 2011 12:54:27 +0200 (CEST) Message-ID: <4DA6D269.1040702@cdmon.com> Date: Thu, 14 Apr 2011 12:54:33 +0200 From: Sergi Seira User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100515 Lightning/1.0b1 Icedove/3.0.4 MIME-Version: 1.0 To: Kirk McKusick References: <201104131505.p3DF5tPa015944@chez.mckusick.com> In-Reply-To: <201104131505.p3DF5tPa015944@chez.mckusick.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: background fsck high load on 8.1 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, 14 Apr 2011 11:13:20 -0000 Hello, thanks for the explanation, I can confirm this behaviour on serveral upgraded boxes. We'll look forward to journaled soft updates or maybe switching to zfs. Anyway it isn't happening that much, only on hard resets. Regards, Sergi On 13/04/11 17:05, Kirk McKusick wrote: >> Date: Tue, 12 Apr 2011 15:14:42 +0200 >> From: Sergi Seira >> To: freebsd-current@freebsd.org >> Subject: background fsck high load on 8.1 >> >> Hello, >> >> We've experienced that background fsck on 8.1 degrades server >> performance on a higher degree than in previous fbsd versions (6.3, >> 7.3; amd64). >> >> We've noticed it after upgrading - same hardware - to a 8.1-RELEASE. >> Now, performance of other services (i.e. apache, mysql) during a >> background fsck falls miserably. >> >> Is there any way to calm fsck down?, nice(1)?, some sysctl? >> >> We have also gmirror, but we prevent to rebuild it if there is a >> fsck running in background. >> >> Thanks for your help, >> regards, >> Sergi > > This is the first report that I have heard of the higher level of > slowdown by background fsck on 8.X systems. My guess is that it > comes about from work done to make the I/O subsystem faster which > in turn allows fsck to have a higher impact. > > For a period we were working on a kernel feature (associated with > nice) that would allow the system to throttle I/O activity for a > given process. It turns out to be a much harder problem than it at > first appears. We set this aside when we got journaled soft updates > working as they eliminate the need for background fsck. While > journaled soft updates are too big of a change to be merged back > into the 8.X tree, we do expect them to be used by default on 9.X > systems. > > Kirk McKusick -- ---8<-------------------- Sergi Seira i Espunya Departament de Sistemes s.seira@cdmon.com www.cdmon.com 93 567 7577 902 364 138 91 182 2767 ext:161 -------------------->8--- From owner-freebsd-fs@FreeBSD.ORG Thu Apr 14 14:12:49 2011 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 A20A9106566B for ; Thu, 14 Apr 2011 14:12:49 +0000 (UTC) (envelope-from mailing.lists@streamvia.net) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by mx1.freebsd.org (Postfix) with ESMTP id 579A98FC13 for ; Thu, 14 Apr 2011 14:12:49 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs01.streamvia.com (Postfix) with ESMTP id 466D614390B; Thu, 14 Apr 2011 15:12:48 +0100 (BST) X-Virus-Scanned: amavisd-new at zcs01.streamvia.com Received: from zcs01.streamvia.com ([127.0.0.1]) by localhost (zcs01.streamvia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmL0msmox5lA; Thu, 14 Apr 2011 15:12:44 +0100 (BST) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by zcs01.streamvia.com (Postfix) with ESMTP id 79201143909; Thu, 14 Apr 2011 15:12:44 +0100 (BST) Date: Thu, 14 Apr 2011 15:12:44 +0100 (BST) From: Ed S To: Adam Stylinski Message-ID: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Originating-IP: [212.119.4.226] X-Mailer: Zimbra 7.0.1_GA_3105 (ZimbraWebClient - SAF3 (Win)/7.0.1_GA_3105) Cc: freebsd-fs@freebsd.org, koie@suri.co.jp Subject: Re: siisch0: Timeout on slot 30 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, 14 Apr 2011 14:12:49 -0000 > I found this in the webcvs and thought there might some relation - > although im not seeing the panic: > > http://lists.freebsd.org/pipermail/freebsd-fs/2010-September/009438.html > Revision 1.1.2.30: download - view: text, markup, annotated - select > for diffs > Thu Sep 30 04:23:03 2010 UTC (6 months, 1 week ago) by mav > Branches: RELENG_8 > Diff to: previous 1.1.2.29: preferred, colored; branchpoint 1.1: > preferred, colored > Changes since revision 1.1.2.29: +8 -5 lines > SVN rev 213293 on 2010-09-30 04:23:03Z by mav > > MFC r212732: > Fix panic, when due to some kind of congestion on FIS-based switching > port multiplier some command triggers false positive timeout, but > then > completes normally. > > Also saw this was the list where mav@ posted a patch previously, i > dont see anything in the commit logs that might fix this issue in > current/head. But might boot it up and see... > > Thanks, > > Ed After doing a bit more digging, it seems that the below has fixed it for my shelf - so far.... :) hint.siisch.0.sata_rev=1 I was only ever seeing timeouts on siisch0 so assume i dont need to limit any further channels... Thanks, Ed From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 04:59:04 2011 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 64D9F106566B for ; Fri, 15 Apr 2011 04:59:04 +0000 (UTC) (envelope-from ptyll@nitronet.pl) Received: from mail.nitronet.pl (smtp.nitronet.pl [195.90.106.27]) by mx1.freebsd.org (Postfix) with ESMTP id 240B28FC16 for ; Fri, 15 Apr 2011 04:59:04 +0000 (UTC) Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.75 (FreeBSD)) (envelope-from ) id 1QAaiB-0007ag-CK for freebsd-fs@freebsd.org; Fri, 15 Apr 2011 06:32:51 +0200 Date: Fri, 15 Apr 2011 06:30:16 +0200 From: Pawel Tyll X-Priority: 3 (Normal) Message-ID: <1555997556.20110415063016@nitronet.pl> To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Nitronet.pl X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: ptyll@nitronet.pl X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false Subject: Consistent ZFS freeze while replacing. 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, 15 Apr 2011 04:59:04 -0000 Hi list, I'm running FreeBSD 8.2-STABLE #0: Wed Apr 13 03:03:08 CEST 2011 (amd64) along with http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110317.patch.xz I replaced one device with another, and when replace was finishing, pool froze. After two reboots (first one resulted in freeze while importing the pool), system came up with pool in following state: pool: storage state: ONLINE scan: resilvered 689G in 19h35m with 0 errors on Thu Apr 14 23:37:10 2011 config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da16 ONLINE 0 0 0 da17 ONLINE 0 0 0 da18 ONLINE 0 0 0 da19 ONLINE 0 0 0 da20 ONLINE 0 0 0 da21 ONLINE 0 0 0 da22 ONLINE 0 0 0 da23 ONLINE 0 0 0 raidz1-1 ONLINE 0 0 0 gpt/ST-5XW25KAR ONLINE 0 0 0 da6 ONLINE 0 0 0 replacing-2 ONLINE 0 0 0 da1 ONLINE 0 0 0 gpt/ST-5XW24JDN ONLINE 0 0 0 gpt/ST-5XW0PKCM ONLINE 0 0 0 da5 ONLINE 0 0 0 da3 ONLINE 0 0 0 da7 ONLINE 0 0 0 da4 ONLINE 0 0 0 raidz1-3 ONLINE 0 0 0 gpt/ST-5XW10ZKX ONLINE 0 0 0 gpt/ST-5XW1A9L6 ONLINE 0 0 0 gpt/ST-5XW1BNGJ ONLINE 0 0 0 gpt/ST-5XW1ALPW ONLINE 0 0 0 gpt/ST-5XW11AQ5 ONLINE 0 0 0 gpt/ST-5XW1330J ONLINE 0 0 0 gpt/ST-5XW18MD4 ONLINE 0 0 0 gpt/ST-5XW10VB0 ONLINE 0 0 0 logs mirror-2 ONLINE 0 0 0 gpt/ssd1-log ONLINE 0 0 0 gpt/ssd2-log ONLINE 0 0 0 cache gpt/ssd1-cache ONLINE 0 0 0 gpt/ssd2-cache ONLINE 0 0 0 This happened to me twice already and I have five more drives to replace. Any ideas? From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 10:12:17 2011 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 6FCF6106564A for ; Fri, 15 Apr 2011 10:12:17 +0000 (UTC) (envelope-from mailing.lists@streamvia.net) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by mx1.freebsd.org (Postfix) with ESMTP id 2E7758FC1D for ; Fri, 15 Apr 2011 10:12:16 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs01.streamvia.com (Postfix) with ESMTP id E6F45143022; Fri, 15 Apr 2011 11:12:15 +0100 (BST) X-Virus-Scanned: amavisd-new at zcs01.streamvia.com Received: from zcs01.streamvia.com ([127.0.0.1]) by localhost (zcs01.streamvia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OXDrAfHJ2Yl3; Fri, 15 Apr 2011 11:12:07 +0100 (BST) Received: from zcs01.streamvia.com (zcs01.streamvia.com [178.63.87.235]) by zcs01.streamvia.com (Postfix) with ESMTP id 400CA142FC1; Fri, 15 Apr 2011 11:12:07 +0100 (BST) Date: Fri, 15 Apr 2011 11:12:06 +0100 (BST) From: Ed S To: Adam Stylinski Message-ID: <7f5a42d2-b3d5-4094-bd5f-eb284d664b5d@zcs01> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Originating-IP: [212.119.4.226] X-Mailer: Zimbra 7.0.1_GA_3105 (ZimbraWebClient - SAF3 (Win)/7.0.1_GA_3105) Cc: freebsd-fs@freebsd.org, koie@suri.co.jp Subject: Re: siisch0: Timeout on slot 30 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, 15 Apr 2011 10:12:17 -0000 > After doing a bit more digging, it seems that the below has fixed it > for my shelf - so far.... :) > > hint.siisch.0.sata_rev=1 > > I was only ever seeing timeouts on siisch0 so assume i dont need to > limit any further channels... > > Thanks, > > Ed Maybe a potential bug in the driver when used with port multipliers, it seems it only sets the first disk of the channel down to rev 1: ada0-4 are all on ch0: pmp0 at siisch0 bus 0 scbus0 target 15 lun 0 ada0 at siisch0 bus 0 scbus0 target 0 lun 0 ada1 at siisch0 bus 0 scbus0 target 1 lun 0 ada2 at siisch0 bus 0 scbus0 target 2 lun 0 ada3 at siisch0 bus 0 scbus0 target 3 lun 0 ada4 at siisch0 bus 0 scbus0 target 4 lun 0 [root@boss ~]# cat /var/log/messages|grep transfer Apr 14 21:11:35 boss kernel: pmp0: 150.000MB/s transfers (SATA 1.x, NONE, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada5: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada6: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 14 21:11:35 boss kernel: ada7: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 11:51:08 2011 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 75276106566C for ; Fri, 15 Apr 2011 11:51:08 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id F386C8FC12 for ; Fri, 15 Apr 2011 11:51:07 +0000 (UTC) Received: by people.fsn.hu (Postfix, from userid 1001) id A7F267C922A; Fri, 15 Apr 2011 13:32:22 +0200 (CEST) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.2 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MF-ACE0E1EA [pR: 15.3477] X-CRM114-CacheID: sfid-20110415_13322_6FC8D08A X-CRM114-Status: Good ( pR: 15.3477 ) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Fri Apr 15 13:32:22 2011 X-DSPAM-Confidence: 0.9948 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4da82cc6419031969112107 X-DSPAM-Factors: 27, From*Attila Nagy , 0.00010, FreeBSD, 0.00053, >+I, 0.00102, >+Hi, 0.00192, wrote+>, 0.00196, to+>, 0.00223, (in, 0.00293, cache, 0.00310, cache, 0.00310, >+>, 0.00328, >+>, 0.00328, wrote, 0.00452, with+>, 0.00506, STABLE, 0.00556, FreeBSD+8, 0.00617, not+sure, 0.00617, logs, 0.00694, list+>, 0.00694, 03+08, 0.00792, mirror, 0.00792, Apr, 0.00840, Apr, 0.00840, #0, 0.00923, config, 0.00977, Wed+Apr, 0.01000, Thu+Apr, 0.01000, X-Spambayes-Classification: ham; 0.00 Received: from japan.t-online.private (japan.t-online.co.hu [195.228.243.99]) by people.fsn.hu (Postfix) with ESMTPSA id 465267C921F; Fri, 15 Apr 2011 13:32:22 +0200 (CEST) Message-ID: <4DA82CC5.4000007@fsn.hu> Date: Fri, 15 Apr 2011 13:32:21 +0200 From: Attila Nagy User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090817 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0 MIME-Version: 1.0 To: Pawel Tyll References: <1555997556.20110415063016@nitronet.pl> In-Reply-To: <1555997556.20110415063016@nitronet.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Consistent ZFS freeze while replacing. 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, 15 Apr 2011 11:51:08 -0000 Hi, On 04/15/11 06:30, Pawel Tyll wrote: > Hi list, > > I'm running FreeBSD 8.2-STABLE #0: Wed Apr 13 03:03:08 CEST 2011 > (amd64) along with > http://people.freebsd.org/~mm/patches/zfs/v28/stable-8-zfsv28-20110317.patch.xz > > I replaced one device with another, and when replace was finishing, > pool froze. After two reboots (first one resulted in freeze while > importing the pool), system came up with pool in following state: > > pool: storage > state: ONLINE > scan: resilvered 689G in 19h35m with 0 errors on Thu Apr 14 23:37:10 2011 > config: > > NAME STATE READ WRITE CKSUM > storage ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > da16 ONLINE 0 0 0 > da17 ONLINE 0 0 0 > da18 ONLINE 0 0 0 > da19 ONLINE 0 0 0 > da20 ONLINE 0 0 0 > da21 ONLINE 0 0 0 > da22 ONLINE 0 0 0 > da23 ONLINE 0 0 0 > raidz1-1 ONLINE 0 0 0 > gpt/ST-5XW25KAR ONLINE 0 0 0 > da6 ONLINE 0 0 0 > replacing-2 ONLINE 0 0 0 > da1 ONLINE 0 0 0 > gpt/ST-5XW24JDN ONLINE 0 0 0 > gpt/ST-5XW0PKCM ONLINE 0 0 0 > da5 ONLINE 0 0 0 > da3 ONLINE 0 0 0 > da7 ONLINE 0 0 0 > da4 ONLINE 0 0 0 > raidz1-3 ONLINE 0 0 0 > gpt/ST-5XW10ZKX ONLINE 0 0 0 > gpt/ST-5XW1A9L6 ONLINE 0 0 0 > gpt/ST-5XW1BNGJ ONLINE 0 0 0 > gpt/ST-5XW1ALPW ONLINE 0 0 0 > gpt/ST-5XW11AQ5 ONLINE 0 0 0 > gpt/ST-5XW1330J ONLINE 0 0 0 > gpt/ST-5XW18MD4 ONLINE 0 0 0 > gpt/ST-5XW10VB0 ONLINE 0 0 0 > logs > mirror-2 ONLINE 0 0 0 > gpt/ssd1-log ONLINE 0 0 0 > gpt/ssd2-log ONLINE 0 0 0 > cache > gpt/ssd1-cache ONLINE 0 0 0 > gpt/ssd2-cache ONLINE 0 0 0 > > This happened to me twice already and I have five more drives to > replace. Any ideas? I'm not sure it's the same, but I can consistently reach this situation when replacing while a scrub is in progress (or replacing more than one drive). So far I could only get a working pool in these cases, if I stopped (in single user, even the pool import freezes every operation on zf) scrub, or replace, so only one left. From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 13:18:10 2011 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 75C87106564A for ; Fri, 15 Apr 2011 13:18:10 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 332B68FC16 for ; Fri, 15 Apr 2011 13:18:09 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AoAHAGI9qE2DaFvO/2dsb2JhbACET5NwjjezDpErgSmDTXgEjXg X-IronPort-AV: E=Sophos;i="4.64,219,1301889600"; d="scan'208";a="117507863" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 15 Apr 2011 08:49:10 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 335D3B3F24 for ; Fri, 15 Apr 2011 08:49:10 -0400 (EDT) Date: Fri, 15 Apr 2011 08:49:10 -0400 (EDT) From: Rick Macklem To: freebsd-fs@freebsd.org Message-ID: <1369404502.72409.1302871750151.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Subject: RFC: make the experimental NFS subsystem the default one 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, 15 Apr 2011 13:18:10 -0000 Hi, I think that the experimental NFS server is now ready for generic use and that the experimental NFS client will be soon, after some commits over the next week or so. How do folks feel w.r.t. making these the default? My plan is to make the server the default first (the "-e" option on mountd and nfsd would become a no-op) and a new option on mountd and nfsd ("-o" sound ok?) would be needed to run what is currently the regular server. (I am not proposing taking out the regular client/server at this time, simply making them the non-default ones.) For the client, "newnfs" would become "nfs" and what is now "nfs" would become "oldnfs" for file system type. (This wouldn't happen until a series of commits bring "newnfs" in line with "nfs" for various things, including default mount options, plus diskless booting for NFSv3 gets fixed.) So, comments w.r.t. this would be appreciated, rick From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 14:04:37 2011 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 2A9651065672 for ; Fri, 15 Apr 2011 14:04:37 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 1209B8FC14 for ; Fri, 15 Apr 2011 14:04:36 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta03.emeryville.ca.mail.comcast.net with comcast id Xplr1g0071vN32cA3q4cvR; Fri, 15 Apr 2011 14:04:36 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta22.emeryville.ca.mail.comcast.net with comcast id Xq4b1g00K1t3BNj8iq4cqo; Fri, 15 Apr 2011 14:04:36 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 50A999B42B; Fri, 15 Apr 2011 07:04:35 -0700 (PDT) Date: Fri, 15 Apr 2011 07:04:35 -0700 From: Jeremy Chadwick To: freebsd-fs@freebsd.org Message-ID: <20110415140435.GA4278@icarus.home.lan> References: <1369404502.72409.1302871750151.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1369404502.72409.1302871750151.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: RFC: make the experimental NFS subsystem the default one 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, 15 Apr 2011 14:04:37 -0000 On Fri, Apr 15, 2011 at 08:49:10AM -0400, Rick Macklem wrote: > I think that the experimental NFS server is now ready for generic use > and that the experimental NFS client will be soon, after some commits > over the next week or so. > > How do folks feel w.r.t. making these the default? > > My plan is to make the server the default first (the "-e" option on > mountd and nfsd would become a no-op) and a new option on mountd and > nfsd ("-o" sound ok?) would be needed to run what is currently the > regular server. (I am not proposing taking out the regular client/server > at this time, simply making them the non-default ones.) > > For the client, "newnfs" would become "nfs" and what is now "nfs" > would become "oldnfs" for file system type. (This wouldn't happen > until a series of commits bring "newnfs" in line with "nfs" for > various things, including default mount options, plus diskless > booting for NFSv3 gets fixed.) > > So, comments w.r.t. this would be appreciated, rick I can't speak for others, but I would feel much more comfortable if a well-written and verbose document/web page was put up somewhere with a full, concise list of what the changes are. Additionally, documentation stating *exactly* what to do / provide you in the case something starts acting wonky would be highly beneficial (commands, kernel stuff, whatever would help you in troubleshooting). NFS, as I'm sure you know, is one of those things where if you break it people get *very* (rightfully) upset. NFS breakage is one of the reasons I moved away from Linux back in the mid-to-late-90s (true). The last thing I need is to upgrade our FreeBSD-based filer to find that while I'm sleeping NFS suddenly behaves oddly or breaking (either on our clients or the server). The reason I haven't tried the experimental NFS server is simply because I have absolutely no idea what the improvements are; no documentation + no incentive = no try. :-) The man page for nfsd(8)'s -e flag tells me nothing more than it's "experimental code" and adds NFSv4 support (the latter does not interest me). Stuff that concerns me the most (for our environment): - Works properly when used with PXE booting and an NFS-based install (e.g. a new 8.2-RELEASE box is being built/installed via serial console and PXE that mounts an NFS filesystem for installation data; will this work if the NFS server is running this experimental code?). I remember you mentioning something to me a long time ago, and I'm almost certainly remembering it wrong, about how the PXE boot client (/boot/pxeboot) on FreeBSD uses a very old version of the NFS protocol. - Works properly when used with *very* old FreeBSD clients. How old? I'm talking 6.4-STABLE old. Yes, we do in fact have boxes that old that are in production. - Works exactly the same, configuration and performance-wise, as the existing (non-experimental) code. Focusing on NFSv2 and NFSv3 here, specifically UDP (the default). NFSv4 does not matter to us in any way shape or form. - Has the experimental code been stress-tested? If so, how? I've heard of people doing silly things like testing with filesystem benchmark utilities -- which pass/work fine, but the instant someone tries using something like rsnapshot (like we do), the thing falls apart. I'm concerned greatly about things like the kernel "deadlocking" (alive but isn't actually responsive to a lot of things), unkillable processes, processes stuck in bad states due to NFS oddities, or abysmal performance. My intent here is not to sound overly critical, but critical enough to make sure you triple-check all your ducks are in a row. :-) -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 15:23:43 2011 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 39B8A106566B for ; Fri, 15 Apr 2011 15:23:43 +0000 (UTC) (envelope-from conall@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id EA03E8FC14 for ; Fri, 15 Apr 2011 15:23:42 +0000 (UTC) Received: by vws18 with SMTP id 18so2774430vws.13 for ; Fri, 15 Apr 2011 08:23:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=GzZW/73VxyT08V5arCZK/OIVFBdaf8HGJ3t/+Mu63z4=; b=IYnypjTTMXJuxHtA5cTXy40UBZ5q6w7Q6qPvV+Wi9Me2qItIsUsmRwMKMGSqdmG+O6 ya7X9LL3YREybZBaFsJhLEUai0uixkik16eCSHxDDewNd1KFYxYFMibh00PwTCHNwOji iN3KyyIV80XlkXUApcWpPjHqgFtxcLThTv9DI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=WjthiagxJ47yTaLujzjZ+n4TSPSEvTiRpvlAWKZBnuamohpAtBGF/6ryq0YAmSDJk+ wvedpo7+TatauWBlcmSawiqP2pImQRZ+Mi68IaNLXfhwbi/OPN1XNxDGTJUWgMJGiAzf FvtGbjTUt9q+9fGsfNebX2zsM0bdXWbNv2RYw= MIME-Version: 1.0 Received: by 10.52.100.2 with SMTP id eu2mr3177812vdb.20.1302879574460; Fri, 15 Apr 2011 07:59:34 -0700 (PDT) Sender: conall@gmail.com Received: by 10.52.161.74 with HTTP; Fri, 15 Apr 2011 07:59:34 -0700 (PDT) Date: Fri, 15 Apr 2011 15:59:34 +0100 X-Google-Sender-Auth: l8eW1mGcfmcoZPMgQj78a0HBXa4 Message-ID: From: "Conall O'Brien" To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Problems Terminating zpool scrub... 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, 15 Apr 2011 15:23:43 -0000 Hello, I've got a NAS box running 8-STABLEW [1] which I'm running with 5x Western Digital 2TB disks. One of the disks was having DMA issues as reported in dmesg, so I began the usual zfs workflow of "zpool offline pool dev", physically removing it and tried to "zpool replace pool dev" but my attempts to do so fail, actually the zpool command keeps ending up in uninterruptable wait (the D state). Before resorting to replacing the disk, a zpool scrub was in progress. Now, I can't kill it using "zpool scrub -s pool", it too ends up in the D state. Is there another way than "zpool scrub -s pool" to terminate a scrub process, so I can proceed with the disk replacement. I care more about resilvering my pool before getting around to scrubbing it. Thanks! [1] For completeness, uname -a reports FreeBSD galvatron.taku.ie 8.2-STABLE FreeBSD 8.2-STABLE #1: Sat Mar 19 13:18:46 UTC 2011 root@galvatron.taku.ie:/usr/src/obj/usr/src/sys/GALVATRON amd64 -- Conall O'Brien From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 22:24:49 2011 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 2E2CD106566C for ; Fri, 15 Apr 2011 22:24:48 +0000 (UTC) (envelope-from dan@3geeks.org) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id B0BA28FC08 for ; Fri, 15 Apr 2011 22:24:48 +0000 (UTC) Received: by yie12 with SMTP id 12so1562446yie.13 for ; Fri, 15 Apr 2011 15:24:48 -0700 (PDT) Received: by 10.236.77.161 with SMTP id d21mr1333728yhe.119.1302904921887; Fri, 15 Apr 2011 15:02:01 -0700 (PDT) Received: from [10.0.1.240] (99-126-192-237.lightspeed.austtx.sbcglobal.net [99.126.192.237]) by mx.google.com with ESMTPS id l74sm1414921yhn.96.2011.04.15.15.02.00 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2011 15:02:01 -0700 (PDT) From: Daniel Mayfield Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Fri, 15 Apr 2011 17:01:58 -0500 Message-Id: To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: question on extended attributes 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, 15 Apr 2011 22:24:49 -0000 I'm trying to use rsync and rsnapshot to make backup copies of my Mac to = my freebsd 8.2 server . When I specify syncing extended attributes as = well, I get an error for any file on the Mac that has a resource fork:=20= rsync: rsync_xal_set: = lsetxattr("Documents/","com.apple.ResourceFork") failed: No space = left on device (28) I'd love to work on fixing this, but I'm seeing a bunch of references to = UFS1 vs UFS2 in the extended attribute readme. But I'm not sure what = I'm actually using (I took the default when it setup, which says = ufs2+softdep, but mount simply says ufs). Can someone help point me in the right direction? daniel= From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 00:01:16 2011 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 C50C61065674 for ; Sat, 16 Apr 2011 00:01:16 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by mx1.freebsd.org (Postfix) with ESMTP id 710838FC08 for ; Sat, 16 Apr 2011 00:01:16 +0000 (UTC) Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta06.westchester.pa.mail.comcast.net with comcast id Xzud1g0030ldTLk5601GG8; Sat, 16 Apr 2011 00:01:16 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta04.westchester.pa.mail.comcast.net with comcast id Y01E1g0011t3BNj3Q01EjH; Sat, 16 Apr 2011 00:01:16 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8706F9B42B; Fri, 15 Apr 2011 17:01:12 -0700 (PDT) Date: Fri, 15 Apr 2011 17:01:12 -0700 From: Jeremy Chadwick To: Daniel Mayfield Message-ID: <20110416000112.GA13487@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: question on extended attributes 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, 16 Apr 2011 00:01:16 -0000 On Fri, Apr 15, 2011 at 05:01:58PM -0500, Daniel Mayfield wrote: > I'm trying to use rsync and rsnapshot to make backup copies of my Mac to my freebsd 8.2 server . When I specify syncing extended attributes as well, I get an error for any file on the Mac that has a resource fork: > > rsync: rsync_xal_set: lsetxattr("Documents/","com.apple.ResourceFork") failed: No space left on device (28) > > I'd love to work on fixing this, but I'm seeing a bunch of references to UFS1 vs UFS2 in the extended attribute readme. But I'm not sure what I'm actually using (I took the default when it setup, which says ufs2+softdep, but mount simply says ufs). > > Can someone help point me in the right direction? Sorry if this sounds harsh or rude, but can I ask you what exactly extended filesystem attributes (usually ACLs) have to do with file resource forks on OS X? AFAIK they have nothing to do with one another. Also, you're aware of how Apple solved the resource fork problem when archiving something in a .zip file, right? The "_MACOSX" directory within the .zip. So basically what I'm saying/getting at is this: there is no solution for the resource fork issue on Apple products, since nothing other than Apple products knows/supports resource forks.. And this comes from someone who's an old Apple II developer (yes, we had resource forks on files on the IIGS). You may have to detect files with resource forks and .zip them first. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 00:06:44 2011 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 E6D3E106566B for ; Sat, 16 Apr 2011 00:06:44 +0000 (UTC) (envelope-from dan@3geeks.org) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id AB1068FC08 for ; Sat, 16 Apr 2011 00:06:44 +0000 (UTC) Received: by yie12 with SMTP id 12so1581274yie.13 for ; Fri, 15 Apr 2011 17:06:44 -0700 (PDT) Received: by 10.236.168.100 with SMTP id j64mr1390852yhl.397.1302912403758; Fri, 15 Apr 2011 17:06:43 -0700 (PDT) Received: from [10.0.1.240] (99-126-192-237.lightspeed.austtx.sbcglobal.net [99.126.192.237]) by mx.google.com with ESMTPS id 44sm1474785yhl.53.2011.04.15.17.06.42 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2011 17:06:43 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Daniel Mayfield In-Reply-To: <20110416000112.GA13487@icarus.home.lan> Date: Fri, 15 Apr 2011 19:06:40 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <337FAD9E-6973-4CA4-96E2-4A24F69916AF@3geeks.org> References: <20110416000112.GA13487@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org Subject: Re: question on extended attributes 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, 16 Apr 2011 00:06:45 -0000 On Apr 15, 2011, at 7:01 PM, Jeremy Chadwick wrote: > On Fri, Apr 15, 2011 at 05:01:58PM -0500, Daniel Mayfield wrote: >> I'm trying to use rsync and rsnapshot to make backup copies of my Mac = to my freebsd 8.2 server . When I specify syncing extended attributes = as well, I get an error for any file on the Mac that has a resource = fork:=20 >>=20 >> rsync: rsync_xal_set: = lsetxattr("Documents/","com.apple.ResourceFork") failed: No space = left on device (28) >>=20 >> I'd love to work on fixing this, but I'm seeing a bunch of references = to UFS1 vs UFS2 in the extended attribute readme. But I'm not sure what = I'm actually using (I took the default when it setup, which says = ufs2+softdep, but mount simply says ufs). >>=20 >> Can someone help point me in the right direction? >=20 > Sorry if this sounds harsh or rude, but can I ask you what exactly > extended filesystem attributes (usually ACLs) have to do with file > resource forks on OS X? AFAIK they have nothing to do with one = another. OS X stores resource forks (and a few other things) as extended = attributes on HFS+ filesystems these days. Or at least that's how it = presents the HFS+ concept of a resource fork to unix programs like rsync = that understand extended attributes. > Also, you're aware of how Apple solved the resource fork problem when > archiving something in a .zip file, right? The "_MACOSX" directory > within the .zip. This is sub optimal as I'd like to be able to inspect/modify the "data = fork" of the file on the freebsd box too. For example, editing files = while I'm ssh'd into the freebsd machine remotely, but still preserving = the icon when it gets copied back. If I were to do as you described, I = may as well setup netatalk and build a time machine style backup device. = That isn't my goal. daniel From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 00:19:55 2011 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 C39D91065672 for ; Sat, 16 Apr 2011 00:19:55 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 842E18FC12 for ; Sat, 16 Apr 2011 00:19:55 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAIfgqE2DaFvO/2dsb2JhbACET6I1iG+qO5FAgSmDTXgEjXo X-IronPort-AV: E=Sophos;i="4.64,222,1301889600"; d="scan'208";a="117599605" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 15 Apr 2011 20:19:36 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 904E6B3F2C; Fri, 15 Apr 2011 20:19:36 -0400 (EDT) Date: Fri, 15 Apr 2011 20:19:36 -0400 (EDT) From: Rick Macklem To: Daniel Mayfield Message-ID: <1660005215.123902.1302913176495.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <337FAD9E-6973-4CA4-96E2-4A24F69916AF@3geeks.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: question on extended attributes 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, 16 Apr 2011 00:19:55 -0000 > On Apr 15, 2011, at 7:01 PM, Jeremy Chadwick wrote: > > > On Fri, Apr 15, 2011 at 05:01:58PM -0500, Daniel Mayfield wrote: > >> I'm trying to use rsync and rsnapshot to make backup copies of my > >> Mac to my freebsd 8.2 server . When I specify syncing extended > >> attributes as well, I get an error for any file on the Mac that has > >> a resource fork: > >> > >> rsync: rsync_xal_set: > >> lsetxattr("Documents/","com.apple.ResourceFork") failed: No > >> space left on device (28) > >> > >> I'd love to work on fixing this, but I'm seeing a bunch of > >> references to UFS1 vs UFS2 in the extended attribute readme. But > >> I'm not sure what I'm actually using (I took the default when it > >> setup, which says ufs2+softdep, but mount simply says ufs). > >> > >> Can someone help point me in the right direction? > > > > Sorry if this sounds harsh or rude, but can I ask you what exactly > > extended filesystem attributes (usually ACLs) have to do with file > > resource forks on OS X? AFAIK they have nothing to do with one > > another. > > OS X stores resource forks (and a few other things) as extended > attributes on HFS+ filesystems these days. Or at least that's how it > presents the HFS+ concept of a resource fork to unix programs like > rsync that understand extended attributes. > > > Also, you're aware of how Apple solved the resource fork problem > > when > > archiving something in a .zip file, right? The "_MACOSX" directory > > within the .zip. > > This is sub optimal as I'd like to be able to inspect/modify the "data > fork" of the file on the freebsd box too. For example, editing files > while I'm ssh'd into the freebsd machine remotely, but still > preserving the icon when it gets copied back. If I were to do as you > described, I may as well setup netatalk and build a time machine style > backup device. That isn't my goal. > I don't believe that resource forks are available under FreeBSD at this time. Solaris supports the "subfile" concept, which is basically the same as far as I know, so it seems there might be something inside ZFS, although I suspect it isn't available for FreeBSD? Does anyone familiar with ZFS know more? From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 00:33:08 2011 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 577D41065672 for ; Sat, 16 Apr 2011 00:33:08 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 3D1BE8FC0C for ; Sat, 16 Apr 2011 00:33:07 +0000 (UTC) Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta06.emeryville.ca.mail.comcast.net with comcast id Y0Gf1g0030b6N64A60Z7Vo; Sat, 16 Apr 2011 00:33:07 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta03.emeryville.ca.mail.comcast.net with comcast id Y0Z61g00i1t3BNj8P0Z7jD; Sat, 16 Apr 2011 00:33:07 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id AB6169B42B; Fri, 15 Apr 2011 17:33:06 -0700 (PDT) Date: Fri, 15 Apr 2011 17:33:06 -0700 From: Jeremy Chadwick To: Daniel Mayfield Message-ID: <20110416003306.GA13853@icarus.home.lan> References: <20110416000112.GA13487@icarus.home.lan> <337FAD9E-6973-4CA4-96E2-4A24F69916AF@3geeks.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <337FAD9E-6973-4CA4-96E2-4A24F69916AF@3geeks.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: question on extended attributes 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, 16 Apr 2011 00:33:08 -0000 On Fri, Apr 15, 2011 at 07:06:40PM -0500, Daniel Mayfield wrote: > > On Apr 15, 2011, at 7:01 PM, Jeremy Chadwick wrote: > > > On Fri, Apr 15, 2011 at 05:01:58PM -0500, Daniel Mayfield wrote: > >> I'm trying to use rsync and rsnapshot to make backup copies of my Mac to my freebsd 8.2 server . When I specify syncing extended attributes as well, I get an error for any file on the Mac that has a resource fork: > >> > >> rsync: rsync_xal_set: lsetxattr("Documents/","com.apple.ResourceFork") failed: No space left on device (28) > >> > >> I'd love to work on fixing this, but I'm seeing a bunch of references to UFS1 vs UFS2 in the extended attribute readme. But I'm not sure what I'm actually using (I took the default when it setup, which says ufs2+softdep, but mount simply says ufs). > >> > >> Can someone help point me in the right direction? > > > > Sorry if this sounds harsh or rude, but can I ask you what exactly > > extended filesystem attributes (usually ACLs) have to do with file > > resource forks on OS X? AFAIK they have nothing to do with one another. > > OS X stores resource forks (and a few other things) as extended attributes on HFS+ filesystems these days. Or at least that's how it presents the HFS+ concept of a resource fork to unix programs like rsync that understand extended attributes. I'll assume you're right. With that assumption in place: OS X rsync supports extended attributes, which when used (on an OS X client) reads data from HFS+ extattr. How exactly do you expect this data to be saved on a non-HFS+ filesystem, such as BSD FFS/UFS, or Linux ext2fs, or Solaris UFS? How will rsync (on the server side, meaning the process that's actually writing the data to a file on the filesystem) know what to do with this data? The only way this would be possible is if rsync had its own custom way of saving resource forks on a remote system (they would have to be separate files). Restoration would require that rsync know what to do with some "specially-named files" to represent the resource fork portion. Keep reading for an example. > > Also, you're aware of how Apple solved the resource fork problem when > > archiving something in a .zip file, right? The "_MACOSX" directory > > within the .zip. > > This is sub optimal as I'd like to be able to inspect/modify the "data fork" of the file on the freebsd box too. For example, editing files while I'm ssh'd into the freebsd machine remotely, but still preserving the icon when it gets copied back. If I were to do as you described, I may as well setup netatalk and build a time machine style backup device. That isn't my goal. Resource forks are a pain in the ass and have been for the past 20 years: again, they existed on the Apple IIGS (which used either ProDOS or HFS filesystems), and the only thing that supported them aside from the filesystem and OS itself was -- ding ding -- ShrinkIt (.shk). It amazes me that Apple continues to use them. How do they work when you format your OS X filesystems as FFS? I'm sure Apple has some kludge there for it. History lesson with validations: The Apple IIGS (specifically GS/OS) had support for resource forks. The only thing that could use them was GS/OS. You could use GS ShrinkIt to save/archive something with resource forks, and it would pop up a dialog warning you of the repercussions if you tried to restore/extract it on a non-GS/OS (e.g. PC, and sometimes Macintosh) machine. If you were using standard ShrinkIt (ProDOS), there was no support for resource forks. So guess how Andy McFadden -- famous Apple II programmer -- solved this problem with the multi-platform nulib archiver? If a resource fork is encountered in a .shk (ShrinkIt) file, and the platform you're restoring on is non-GS/OS, the resource fork portion is stored as a *separate file* with "_rsrc_" appended to the filename. Apple has effectively done the exact same thing with .zip and the _MACOSX directory. rsync would need to mimic that functionality to ensure cross-platform compatibility (storage and retrieval of resource forks). -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 00:57:02 2011 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 0F154106564A for ; Sat, 16 Apr 2011 00:57:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id AAFCB8FC08 for ; Sat, 16 Apr 2011 00:57:01 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAL7oqE2DaFvO/2dsb2JhbACET6I1iG+qL5E9gSmDTXgEjXo X-IronPort-AV: E=Sophos;i="4.64,222,1301889600"; d="scan'208";a="117601634" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 15 Apr 2011 20:57:00 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id C5A25B3F5B; Fri, 15 Apr 2011 20:57:00 -0400 (EDT) Date: Fri, 15 Apr 2011 20:57:00 -0400 (EDT) From: Rick Macklem To: Jeremy Chadwick Message-ID: <1924310048.124584.1302915420741.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110415140435.GA4278@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: RFC: make the experimental NFS subsystem the default one 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, 16 Apr 2011 00:57:02 -0000 > > I can't speak for others, but I would feel much more comfortable if a > well-written and verbose document/web page was put up somewhere with a > full, concise list of what the changes are. Well, if you mean source code changes, I can't think of how I could come up with this. The experimental NFS implementation is based on work I started in 2003 and is a separate implementation from the other one in FreeBSD, so I can't produce any kind of "log" of changes for it. (I started from the code in OpenBSD2.6, but there would be very little of that code left at this point.) I can tell you that, as far as I know, it supports NFSv2 and NFSv3 in the same way the other/regular server does. (There might be an obscure case where it returns a different errno for some failure or similar, but nothing that I am aware of.) I ran it in production mode for a few years, where the clients were mostly Linux 2.4 and 2.6 systems, plus a FreeBSD4.6 system and didn't see issues when they used NFSv3 mounts. I would like to think that folks won't notice anything when they switch over, but I am not nieve(sp?) enough to believe no one will find problems with it. The one area that is different is what nfsstat reports, since the "-e" version includes extra information. If that causes difficulties for folks, it should be possible to implement a "old nfsstat -s" compatible output that just reports the same information as "nfsstat -s" does now. > Additionally, > documentation > stating *exactly* what to do / provide you in the case something > starts > acting wonky would be highly beneficial (commands, kernel stuff, > whatever would help you in troubleshooting). > I can't think of a good answer for this, either, because it depends upon what "wonky" means. I don't think it's much different than any other issue that shows up in freebsd-current (or freebsd-stable or freebsd-fs) or a PR? (Then add the "-o" option to flip back to the old server until the problem gets resolved.) > NFS, as I'm sure you know, is one of those things where if you break > it > people get *very* (rightfully) upset. NFS breakage is one of the > reasons I moved away from Linux back in the mid-to-late-90s (true). > The > last thing I need is to upgrade our FreeBSD-based filer to find that > while I'm sleeping NFS suddenly behaves oddly or breaking (either on > our > clients or the server). > > The reason I haven't tried the experimental NFS server is simply > because > I have absolutely no idea what the improvements are; no documentation > + > no incentive = no try. :-) The man page for nfsd(8)'s -e flag tells me > nothing more than it's "experimental code" and adds NFSv4 support (the > latter does not interest me). > Well, about the only improvement is NFSv4, so for you there is no incentive at this time. Hopefully you may find the better file locking, ACLs etc that NFSv4 offsers useful improvements someday. It does have a rather novel DRC (duplicate request cache), which I believe works better, particularily when clients use TCP, but I can't say that you'll see a noticible change because of this. (Maybe less mbuf hungry compared to the generic one in the FreeBSD8 krpc.) > Stuff that concerns me the most (for our environment): > > - Works properly when used with PXE booting and an NFS-based install > (e.g. a new 8.2-RELEASE box is being built/installed via serial > console and PXE that mounts an NFS filesystem for installation data; > will this work if the NFS server is running this experimental > code?). I remember you mentioning something to me a long time ago, > and I'm almost certainly remembering it wrong, about how the PXE boot > client (/boot/pxeboot) on FreeBSD uses a very old version of the NFS > protocol. > Well, I've PXE booted from it using the old pxeboot code that used NFSv2 and the recent code that I modified to use NFSv3. I don't see why there would be a problem, but obviously I can't guarantee that. > - Works properly when used with *very* old FreeBSD clients. How old? > I'm talking 6.4-STABLE old. Yes, we do in fact have boxes that old > that are in production. > As noted above, I have used it with a FreeBSD4.6 client, but I don't have any old FreeBSD systems to test against any more. > - Works exactly the same, configuration and performance-wise, as the > existing (non-experimental) code. Focusing on NFSv2 and NFSv3 here, > specifically UDP (the default). NFSv4 does not matter to us in any > way shape or form. > I believe it will, but can't say it will. > - Has the experimental code been stress-tested? If so, how? I've heard > of people doing silly things like testing with filesystem benchmark > utilities -- which pass/work fine, but the instant someone tries > using something like rsnapshot (like we do), the thing falls apart. > > I'm concerned greatly about things like the kernel "deadlocking" > (alive > but isn't actually responsive to a lot of things), unkillable > processes, > processes stuck in bad states due to NFS oddities, or abysmal > performance. > Well, all I have access to these days are two laptops and one old desktop system. Someone was going to look at trying it in FreeBSD's network perf cluster, but I don't know if that has happened. I have heard some positive reports from others, but... As noted above, I did run an earlier version of the server in production mode when I first ported it to FreeBSD and it handled the loads we had well, but that's a long time ago. One of the reasons that I was encouraged to suggest this is to get it more widely tested. I can only do so much in this regard and that has already happened. If others aren't willing to try and run it, it can't progress beyond where it is now. Maybe someone from Isilon could chime in with some information on what testing they've put it through, recognizing that their system is significantly different and without giving out any information that they would consider proprietary? Again, I can't guarantee there won't be a regression, but until others try to run it, I/we won't know. > My intent here is not to sound overly critical, but critical enough to > make sure you triple-check all your ducks are in a row. :-) > Well, I can't think of more that I can do than answer, as above. From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 01:23:39 2011 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 BA0E4106566C for ; Sat, 16 Apr 2011 01:23:39 +0000 (UTC) (envelope-from dan@3geeks.org) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5928FC18 for ; Sat, 16 Apr 2011 01:23:39 +0000 (UTC) Received: by ywf7 with SMTP id 7so486222ywf.13 for ; Fri, 15 Apr 2011 18:23:38 -0700 (PDT) Received: by 10.90.183.18 with SMTP id g18mr2960823agf.73.1302917017546; Fri, 15 Apr 2011 18:23:37 -0700 (PDT) Received: from [10.0.1.240] (99-126-192-237.lightspeed.austtx.sbcglobal.net [99.126.192.237]) by mx.google.com with ESMTPS id 6sm3124030anx.46.2011.04.15.18.23.35 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2011 18:23:36 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Daniel Mayfield In-Reply-To: <20110416003306.GA13853@icarus.home.lan> Date: Fri, 15 Apr 2011 20:23:34 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <1A369F02-452C-4812-A461-C9A4748AC340@3geeks.org> References: <20110416000112.GA13487@icarus.home.lan> <337FAD9E-6973-4CA4-96E2-4A24F69916AF@3geeks.org> <20110416003306.GA13853@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1084) Cc: freebsd-fs@freebsd.org Subject: Re: question on extended attributes 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, 16 Apr 2011 01:23:39 -0000 >>>> rsync: rsync_xal_set: = lsetxattr("Documents/","com.apple.ResourceFork") failed: No space = left on device (28) >>>=20 >>> Sorry if this sounds harsh or rude, but can I ask you what exactly >>> extended filesystem attributes (usually ACLs) have to do with file >>> resource forks on OS X? AFAIK they have nothing to do with one = another. >>=20 >> OS X stores resource forks (and a few other things) as extended = attributes on HFS+ filesystems these days. Or at least that's how it = presents the HFS+ concept of a resource fork to unix programs like rsync = that understand extended attributes. >=20 > I'll assume you're right. With that assumption in place: OS X rsync > supports extended attributes, which when used (on an OS X client) = reads > data from HFS+ extattr. >=20 > How exactly do you expect this data to be saved on a non-HFS+ > filesystem, such as BSD FFS/UFS, or Linux ext2fs, or Solaris UFS? How > will rsync (on the server side, meaning the process that's actually > writing the data to a file on the filesystem) know what to do with = this > data? >=20 > The only way this would be possible is if rsync had its own custom way > of saving resource forks on a remote system (they would have to be > separate files). Restoration would require that rsync know what to do > with some "specially-named files" to represent the resource fork > portion. Keep reading for an example. Rsync sees it as an extended attribute, a black box as it were, and = simply copies it byte for byte to the remote side which then attempts to = store the (very large) extended attribute. That's where the above = message comes from (rsync : "." . on the freebsd box is what is = emitting the no space left message). I fully admit that its a bit of a hack, but I'm just looking for a place = to start within the code so I can try to allow for arbitrarily sized = extended attributes (or at least allocate an inode for large extattrs). = Google gives me this: = http://lists.samba.org/archive/rsync/2009-October/024124.html which = confirms that the size limit of the extattr is to blame. The poster = there had a similar idea to what you described, but I'm not satisfied = with that. daniel= From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 01:25:38 2011 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 D735E106566B for ; Sat, 16 Apr 2011 01:25:38 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 95DDC8FC08 for ; Sat, 16 Apr 2011 01:25:35 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAIjvqE2DaFvO/2dsb2JhbACET6I1sz6RPYEpg014BI16 X-IronPort-AV: E=Sophos;i="4.64,222,1301889600"; d="scan'208";a="118495641" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 15 Apr 2011 21:25:34 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 69E81B3F2F; Fri, 15 Apr 2011 21:25:34 -0400 (EDT) Date: Fri, 15 Apr 2011 21:25:34 -0400 (EDT) From: Rick Macklem To: Daniel Mayfield Message-ID: <945861089.125242.1302917134332.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: FreeBSD FS Subject: Re: question on extended attributes 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, 16 Apr 2011 01:25:38 -0000 Oh, I don't know if this might help, but... The Mac OS X NFS client will create a bunch of .XXX files to store the resource forks. So, if you NFS mounted the FreeBSD volume on your Mac and then copied the subtree to the NFS mount point, Mac OS X "might" create the fake resource fork files for you? (I'm not sure which Mac copy programs know about resource forks.) If this works, you'll see a bunch of stuff in the directories with names that start with ._ if I recall correctly. Not sure what you can do with them on FreeBSD though? rick From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 01:36:09 2011 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 358BB1065672 for ; Sat, 16 Apr 2011 01:36:09 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id F0D2C8FC08 for ; Sat, 16 Apr 2011 01:36:08 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id p3G1a7aY023540; Fri, 15 Apr 2011 20:36:07 -0500 (CDT) Date: Fri, 15 Apr 2011 20:36:07 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Rick Macklem In-Reply-To: <1924310048.124584.1302915420741.JavaMail.root@erie.cs.uoguelph.ca> Message-ID: References: <1924310048.124584.1302915420741.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Fri, 15 Apr 2011 20:36:07 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: RFC: make the experimental NFS subsystem the default one 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, 16 Apr 2011 01:36:09 -0000 On Fri, 15 Apr 2011, Rick Macklem wrote: > >> My intent here is not to sound overly critical, but critical enough to >> make sure you triple-check all your ducks are in a row. :-) > > Well, I can't think of more that I can do than answer, as above. It is my feeling that you have been unnecessarily slammed. I have not tried the experimental NFS but then again I am not running the latest FreeBSD either. When I do update my FreeBSD, I will be sure to use your experimental version. My main interest is interoperability with systems other than FreeBSD such as Solaris, Linux, and Apple's OS X. Client throughput of FreeBSD's default NFS is low. I would be hoping to get more throughput. Also, modern NFS uses TCP so I would expect to use that. I am also using the automounter and hope that the updated NFS works at least as well (or better) than the default one. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 02:06:01 2011 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 85A5E106564A for ; Sat, 16 Apr 2011 02:06:01 +0000 (UTC) (envelope-from dan@3geeks.org) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4A3848FC14 for ; Sat, 16 Apr 2011 02:06:00 +0000 (UTC) Received: by ywf7 with SMTP id 7so492358ywf.13 for ; Fri, 15 Apr 2011 19:06:00 -0700 (PDT) Received: by 10.236.170.69 with SMTP id o45mr1421712yhl.488.1302919560527; Fri, 15 Apr 2011 19:06:00 -0700 (PDT) Received: from [10.0.1.237] (99-126-192-237.lightspeed.austtx.sbcglobal.net [99.126.192.237]) by mx.google.com with ESMTPS id l30sm1398586yhn.6.2011.04.15.19.05.58 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2011 19:05:59 -0700 (PDT) References: <945861089.125242.1302917134332.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <945861089.125242.1302917134332.JavaMail.root@erie.cs.uoguelph.ca> Mime-Version: 1.0 (iPhone Mail 8G4) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <380C2890-68F4-4153-9306-965543F622EF@3geeks.org> X-Mailer: iPhone Mail (8G4) From: Daniel Mayfield Date: Fri, 15 Apr 2011 21:05:54 -0500 To: Rick Macklem Cc: FreeBSD FS Subject: Re: question on extended attributes 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, 16 Apr 2011 02:06:01 -0000 > Oh, I don't know if this might help, but... >=20 > The Mac OS X NFS client will create a bunch of .XXX files to store > the resource forks. So, if you NFS mounted the FreeBSD volume on > your Mac and then copied the subtree to the NFS mount point, Mac OS X > "might" create the fake resource fork files for you? (I'm not sure > which Mac copy programs know about resource forks.) If this works, > you'll see a bunch of stuff in the directories with names that start > with ._ if I recall correctly. Not sure what you can do with them on > FreeBSD though? I've seen that behavior too. My goal is have this work over ssh, as I am of= ten accessing things remotely. I want to be able do work on the freebsd sid= e(read, write, move or delete files) without leaving nfs droppings all over m= y filesystem. Think more along the lines of active/active working hosts than as a backup f= ile repository. I'm looking for least surprise when using the freebsd side.= Daniel= From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 02:15:09 2011 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 864BE106564A for ; Sat, 16 Apr 2011 02:15:09 +0000 (UTC) (envelope-from z0.0z.furukawa@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 59F0E8FC17 for ; Sat, 16 Apr 2011 02:15:09 +0000 (UTC) Received: by pzk27 with SMTP id 27so1594365pzk.13 for ; Fri, 15 Apr 2011 19:15:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=tKxDKsggTi/Bcy3x9JTm9llfhGwQgkuMI+8CyPAmyYE=; b=Bi/LcXM0rdzLMHJzvMh9y5lg32krbw2F7tNGbs99Iq7y76zTWusZO0cuxr/Xni110O S/fY/cK2TvOY/9HriT9QO6e3KSPuSMkEoRY4ntAuQ5+iwvWPfTKIuavBN3AoYbg2kmaD /YpOSoDWX8TRKb10m2oreE+50k5F2mjqKI1+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=W80j0L56fU+tVdKMqExIl/LPsegVjC4WyyN4rKGYCsUYpkzXCFx44jQFhI1m6+toTT FQ4qkgYbQoofEKcVhVeQiKtHSm+Aqr7JPXtHdAryvlKcdLIsKkFluNjKPSfY1d4cdSn9 QYFeFj9fybZLGrl6X883xyb4fe6k65gxt1H8w= Received: by 10.142.120.38 with SMTP id s38mr1176774wfc.128.1302918765406; Fri, 15 Apr 2011 18:52:45 -0700 (PDT) Received: from [172.16.211.46] (atago.c.csce.kyushu-u.ac.jp [133.5.17.150]) by mx.google.com with ESMTPS id y2sm4395730wfd.20.2011.04.15.18.52.43 (version=SSLv3 cipher=OTHER); Fri, 15 Apr 2011 18:52:44 -0700 (PDT) Message-ID: <4DA8F664.9030008@gmail.com> Date: Sat, 16 Apr 2011 10:52:36 +0900 From: Jun Furukawa User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ja; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: cdp_c has incomplete type error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2011 02:15:09 -0000 When$B!!(BI compiled the following C language code which hooks vn_write function on FreeBSD8.2, I get "error: field 'cdp_c' has incomplete type" error. Here we list the C source code, Makefile and the compiler messages. Can anyone help me please? ************************vn_hook.c*********************************** #include /* module */ #include /* module */ #include /* module */ #include /* size_t, copyin, copyout, malloc */ #include /* copyin, copyout */ #include /* struct thread */ #include /* vnops */ #include /* msdosfs_vnodeops */ #include /* malloc */ #include /* cdpd_data */ typedef int (*vnw_t)(struct file*, struct uio*, struct ucred*, int flags, struct thread*); int vn_write_hook(struct file *fp, struct uio *uio, struct ucred *active_cred, int flags, struct thread *td); int caesar_encrypt (char *str, int len, int key); vnw_t old_vn_write; /* caesar encription */ int caesar_encrypt (char *str, int len, int key) { int i; for (i = 0; i < len ; i++) { if (str[i] != '\0') { str[i] += key; } } return 0; } /* vn_write hook */ int vn_write_hook(struct file *fp, struct uio *uio, struct ucred *active_cred, int flags, struct thread *td) { /* The definition of struct file */ /* from /usr/include/sys/file.h */ //struct file { // ... // struct vnode *f_vnode; /* NULL or applicable vnode */ // ... for f_offset */ // // struct cdev_privdata *f_cdevpriv; /* (d) Private data // for the cdev. */ //}; /* The definition of vnode */ /* from /usr/include/sys/vnode.h */ //struct vnode { // ... // const char *v_tag; /* u type of // underlying data */ // ... //}; /* The definition of struct iovec */ /* from /usr/include/sys/_iovec.h */ //struct iovec { // void *iov_base; /* Base address. */ // size_t iov_len; /* Length. */ //}; /* The definition of struct uio */ /* from /usr/include/sys/uio.h */ //struct uio { //struct iovec *uio_iov; /* scatter/gather list */ //... //}; /* struct cdev_privdata */ /* from /usr/include/fs/devfs/devfs_int.h */ //struct cdev_privdata { // struct file *cdpd_fp; // void *cdpd_data; // void (*cdpd_dtr)(void *); // LIST_ENTRY(cdev_privdata) cdpd_list; //}; /* Is the destination msdosfs ? */ if(!strncmp("msdosfs",fp->f_vnode->v_tag,7)) { int error; int iov_len; char *mybuf; iov_len = uio->uio_iov->iov_len; mybuf = (char *)malloc(iov_len,M_TEMP,M_NOWAIT|M_ZERO); /* copy data from user land to kernel land */ error = copyin(uio->uio_iov->iov_base, mybuf, iov_len); if (error != 0) { uprintf("Cannot write data to kernel space\n"); } /* debug */ // uprintf("cdev_priv:%p", // (char *)fp->f_cdevpriv->cdpd_data); /* encrypt by caesar algorithm */ caesar_encrypt(mybuf, iov_len, 3); /* copy data from kernel land to user land */ error = copyout(mybuf, uio->uio_iov->iov_base, iov_len); if (error != 0) { uprintf("Cannot write data to user space\n"); } free(mybuf,M_TEMP); } return (old_vn_write(fp, uio, active_cred, flags, td)); } /* The function called at load/unload */ static int load(struct module *module, int cmd, void *arg) { int error = 0; /* the initial value of vnops */ /* from /usr/src/sys/kern/vfs_vnops.c */ //struct fileops vnops = { // .fo_read = vn_read, // .fo_write = vn_write, // .fo_truncate = vn_truncate, // .fo_ioctl = vn_ioctl, // .fo_poll = vn_poll, // .fo_kqfilter = vn_kqfilter, // .fo_stat = vn_statfile, // .fo_close = vn_closefile, // .fo_flags = DFLAG_PASSABLE | DFLAG_SEEKABLE //}; switch (cmd) { case MOD_LOAD: uprintf("Module has loaded\n"); /* Replace vn_write with vn_write_hook. */ old_vn_write = (vnw_t)(vnops.fo_write); vnops.fo_write = vn_write_hook; break; case MOD_UNLOAD: uprintf("Module has unloaded\n"); /* Change everyhting back to normal. */ vnops.fo_write = old_vn_write; break; default: error = EOPNOTSUPP; break; } return (error); } static moduledata_t vn_write_hook_mod = { "vn_write_hook", /* module name */ load, /* event handler */ NULL /* EXTRA DATA */ }; DECLARE_MODULE(vn_write_hook, vn_write_hook_mod, SI_SUB_DRIVERS, SI_ORDER_MIDDLE); ************************vn_hook.c*********************************** ************************Makefile************************************ KMOD = vn_hook # Name of KLD to build. SRCS = vnode_if.h vn_hook.c # List of source files. .include 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 C5686106566C for ; Sat, 16 Apr 2011 03:25:17 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7ED278FC12 for ; Sat, 16 Apr 2011 03:25:17 +0000 (UTC) Received: by yie12 with SMTP id 12so1609876yie.13 for ; Fri, 15 Apr 2011 20:25:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=KosFaLlZcjQxNz/lYp09dpjWoLCJQgWdI9AKRucsW+U=; b=tr6LMwS/D8+ljV7b4LbZo/FmHaV7i9HbM6lqYTuchggKMcCYiaVdrxD2yXlpgtQoMv wScyoe+sNgjUXeRVRUm345vZ3jSJz9uLpWpZypQ7vrXkBsfT1BVZ9YW5h7ohl9Jvxkir pl0E7XxvJs8UXqvhOq8IP40/Cafmu93riNoYs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=aueOFLWCet6gRdgt9UR2HcLFrxdaluFMhfzMxlLcB7nE7BaHKopd6uXa0Ew+iTZeGW QVD4iI3QoRQXMvWWE0vh64svmBluqFcs/8MzsjSd4n7UV87T42Q/3LkmeneWORV8AGI4 rHNqfXp/tGO2ukpnycOCLZAzRbatozWrErr3g= MIME-Version: 1.0 Received: by 10.90.249.25 with SMTP id w25mr3024990agh.55.1302924316733; Fri, 15 Apr 2011 20:25:16 -0700 (PDT) Received: by 10.90.67.9 with HTTP; Fri, 15 Apr 2011 20:25:16 -0700 (PDT) In-Reply-To: References: <1924310048.124584.1302915420741.JavaMail.root@erie.cs.uoguelph.ca> Date: Fri, 15 Apr 2011 20:25:16 -0700 Message-ID: From: Freddie Cash To: Bob Friesenhahn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: RFC: make the experimental NFS subsystem the default one 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, 16 Apr 2011 03:25:17 -0000 On Fri, Apr 15, 2011 at 6:36 PM, Bob Friesenhahn wrote: > On Fri, 15 Apr 2011, Rick Macklem wrote: >> >>> My intent here is not to sound overly critical, but critical enough to >>> make sure you triple-check all your ducks are in a row. :-) >> >> Well, I can't think of more that I can do than answer, as above. > > It is my feeling that you have been unnecessarily slammed. =C2=A0I have n= ot tried > the experimental NFS but then again I am not running the latest FreeBSD > either. =C2=A0When I do update my FreeBSD, I will be sure to use your > experimental version. > > My main interest is interoperability with systems other than FreeBSD such= as > Solaris, Linux, and Apple's OS X. =C2=A0Client throughput of FreeBSD's de= fault > NFS is low. =C2=A0I would be hoping to get more throughput. =C2=A0Also, m= odern NFS > uses TCP so I would expect to use that. I am also using the automounter a= nd > hope that the updated NFS works at least as well (or better) than the > default one. I haven't netbooted any systems yet, but I've been using the experimental NFS server for a few months now. Originally with Kubuntu 9.10 NFSv3 clients, then with NFSv4 clients (Kubuntu, Arch Linux). So far, everything works well. For streaming video files, it works extremely well. :) Started with UDP mounts, switched to TCP mounts, without any issues. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 03:32:41 2011 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 DAADA1065675 for ; Sat, 16 Apr 2011 03:32:41 +0000 (UTC) (envelope-from james@jlauser.net) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9D0E48FC12 for ; Sat, 16 Apr 2011 03:32:41 +0000 (UTC) Received: by qyk27 with SMTP id 27so2221665qyk.13 for ; Fri, 15 Apr 2011 20:32:40 -0700 (PDT) Received: by 10.224.27.66 with SMTP id h2mr1962439qac.120.1302923215798; Fri, 15 Apr 2011 20:06:55 -0700 (PDT) Received: from [10.0.10.216] (cpe-74-76-129-142.nycap.res.rr.com [74.76.129.142]) by mx.google.com with ESMTPS id g28sm2373115qck.15.2011.04.15.20.06.53 (version=SSLv3 cipher=OTHER); Fri, 15 Apr 2011 20:06:54 -0700 (PDT) Message-ID: <4DA907DC.7080909@jlauser.net> Date: Fri, 15 Apr 2011 23:07:08 -0400 From: "James L. Lauser" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20110416000112.GA13487@icarus.home.lan> <337FAD9E-6973-4CA4-96E2-4A24F69916AF@3geeks.org> In-Reply-To: <337FAD9E-6973-4CA4-96E2-4A24F69916AF@3geeks.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: question on extended attributes 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, 16 Apr 2011 03:32:41 -0000 On 04/15/2011 08:06 PM, Daniel Mayfield wrote: > > On Apr 15, 2011, at 7:01 PM, Jeremy Chadwick wrote: > >> On Fri, Apr 15, 2011 at 05:01:58PM -0500, Daniel Mayfield wrote: >>> I'm trying to use rsync and rsnapshot to make backup copies of my Mac to my freebsd 8.2 server . When I specify syncing extended attributes as well, I get an error for any file on the Mac that has a resource fork: >>> >>> rsync: rsync_xal_set: lsetxattr("Documents/","com.apple.ResourceFork") failed: No space left on device (28) >>> >>> I'd love to work on fixing this, but I'm seeing a bunch of references to UFS1 vs UFS2 in the extended attribute readme. But I'm not sure what I'm actually using (I took the default when it setup, which says ufs2+softdep, but mount simply says ufs). >>> >>> Can someone help point me in the right direction? >> >> Sorry if this sounds harsh or rude, but can I ask you what exactly >> extended filesystem attributes (usually ACLs) have to do with file >> resource forks on OS X? AFAIK they have nothing to do with one another. > > OS X stores resource forks (and a few other things) as extended attributes on HFS+ filesystems these days. Or at least that's how it presents the HFS+ concept of a resource fork to unix programs like rsync that understand extended attributes. > >> Also, you're aware of how Apple solved the resource fork problem when >> archiving something in a .zip file, right? The "_MACOSX" directory >> within the .zip. > > This is sub optimal as I'd like to be able to inspect/modify the "data fork" of the file on the freebsd box too. For example, editing files while I'm ssh'd into the freebsd machine remotely, but still preserving the icon when it gets copied back. If I were to do as you described, I may as well setup netatalk and build a time machine style backup device. That isn't my goal. > > daniel > Daniel... I back up several Macs at home to my FreeBSD file server using netatalk. Setting it up is very simple (just install it and turn it on and by default, it'll server home directories), and it's smart enough to store resource forks in the same way that OS X does when you plug in a non-HFS disk directly (with the dot-underscore files). -- James L. Lauser james@jlauser.net http://jlauser.net/ From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 08:14:01 2011 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 78740106566C for ; Sat, 16 Apr 2011 08:14:01 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 08EF78FC0C for ; Sat, 16 Apr 2011 08:14:00 +0000 (UTC) Received: by wyf23 with SMTP id 23so3377956wyf.13 for ; Sat, 16 Apr 2011 01:14:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:x-mailer:mime-version:content-type :content-transfer-encoding; bh=UgZZpQI84xsm91qZYjphjyDF66gNuRDSYqKOPrh69ZY=; b=lB0eXfSP9dn/BcjGbOc8xCVQqAreirKPXn0AGcXB1l9DCl8s+vWa56LNaXW7cTiEqh hUxjOEA9NnW9eCaW+aWo/Eg02q6JBhZLVcFMpgadR4ZKLnVKnJ7S0I0nZqQThFOUnu0J Z3kPP0/LjwkNVckHyQSXmqn+vyMoAVZ9VMLYw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=IMlhF4W74BO6lW+S5TSJ+jaU/G8nmgpHDtn7JJB6hBBBCjVnDveQ0TNwx7S3uV3FuE kJ0vPBz9xN+aMKrCBBbnu6MxsuO0Gm3zTroLBoAhUN0e/kRpm8stqHU4GiRnunW4D5Z8 c4lX2dhxBVBL6vay9ioSsBVyXwDbN80/EGvGk= Received: by 10.227.179.207 with SMTP id br15mr2863630wbb.191.1302941639755; Sat, 16 Apr 2011 01:13:59 -0700 (PDT) Received: from ernst.jennejohn.org (p578E2C6F.dip.t-dialin.net [87.142.44.111]) by mx.google.com with ESMTPS id y29sm2043345wbd.21.2011.04.16.01.13.58 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 16 Apr 2011 01:13:59 -0700 (PDT) Date: Sat, 16 Apr 2011 10:13:57 +0200 From: Gary Jennejohn To: Jun Furukawa Message-ID: <20110416101357.326e23ce@ernst.jennejohn.org> In-Reply-To: <4DA8F664.9030008@gmail.com> References: <4DA8F664.9030008@gmail.com> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: cdp_c has incomplete type error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2011 08:14:01 -0000 On Sat, 16 Apr 2011 10:52:36 +0900 Jun Furukawa wrote: > When I compiled the following C language code which hooks vn_write function > on FreeBSD8.2, > I get "error: field 'cdp_c' has incomplete type" error. > Here we list the C source code, Makefile and the compiler messages. > Can anyone help me please? [code deleted] You have to include at least sys/conf.h, which is where struct cdev is defined. -- Gary Jennejohn From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 11:40:00 2011 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 0884B1065670 for ; Sat, 16 Apr 2011 11:40:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC5B8FC0A for ; Sat, 16 Apr 2011 11:39:58 +0000 (UTC) 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 p3GBdsRb031210 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2011 14:39:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p3GBdrOR018765; Sat, 16 Apr 2011 14:39:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p3GBdrdI018764; Sat, 16 Apr 2011 14:39:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 16 Apr 2011 14:39:53 +0300 From: Kostik Belousov To: Daniel Mayfield Message-ID: <20110416113953.GO48734@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dfmC41YZQlborXoK" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-fs@freebsd.org Subject: Re: question on extended attributes 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, 16 Apr 2011 11:40:00 -0000 --dfmC41YZQlborXoK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 15, 2011 at 05:01:58PM -0500, Daniel Mayfield wrote: > I'm trying to use rsync and rsnapshot to make backup copies of my Mac to = my freebsd 8.2 server . When I specify syncing extended attributes as well= , I get an error for any file on the Mac that has a resource fork:=20 >=20 > rsync: rsync_xal_set: lsetxattr("Documents/","com.apple.ResourceFork= ") failed: No space left on device (28) >=20 > I'd love to work on fixing this, but I'm seeing a bunch of references to = UFS1 vs UFS2 in the extended attribute readme. But I'm not sure what I'm a= ctually using (I took the default when it setup, which says ufs2+softdep, b= ut mount simply says ufs). >=20 > Can someone help point me in the right direction? UFS2 only allows for 2 blocks to store extended attrs. I believe this is the cause of your error. --dfmC41YZQlborXoK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk2pgAkACgkQC3+MBN1Mb4j4zACgtFhU/OOzm/eV4zl0KYBxYKw3 imYAniBXrOLrH3r25rvZ0+BX5n/VG3ED =LucL -----END PGP SIGNATURE----- --dfmC41YZQlborXoK-- From owner-freebsd-fs@FreeBSD.ORG Sat Apr 16 19:26:40 2011 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 C645F1065670 for ; Sat, 16 Apr 2011 19:26:40 +0000 (UTC) (envelope-from chris@behanna.org) Received: from nm17-vm0.access.bullet.mail.mud.yahoo.com (nm17-vm0.access.bullet.mail.mud.yahoo.com [66.94.236.21]) by mx1.freebsd.org (Postfix) with SMTP id 846748FC0A for ; Sat, 16 Apr 2011 19:26:40 +0000 (UTC) Received: from [66.94.237.195] by nm17.access.bullet.mail.mud.yahoo.com with NNFMP; 16 Apr 2011 19:12:49 -0000 Received: from [66.94.237.96] by tm6.access.bullet.mail.mud.yahoo.com with NNFMP; 16 Apr 2011 19:12:49 -0000 Received: from [127.0.0.1] by omp1001.access.mail.mud.yahoo.com with NNFMP; 16 Apr 2011 19:12:49 -0000 X-Yahoo-Newman-Id: 793199.80376.bm@omp1001.access.mail.mud.yahoo.com Received: (qmail 61939 invoked from network); 16 Apr 2011 19:12:49 -0000 Received: from [10.0.1.120] (chris@99.120.175.239 with plain) by smtp102.sbc.mail.bf1.yahoo.com with SMTP; 16 Apr 2011 12:12:49 -0700 PDT X-Yahoo-SMTP: IImPLAuswBCrx2RdXZGWc4UZbB59Q8rbW69ykY5boJ7l_g-- X-YMail-OSG: UufH7pEVM1l9hYzqC886VODS5mutPvzg2AnzBSA0tkGNm9s HWIs7EIQ3d3gqCIy_uKt5PDunORwiDSPKCVK7ZXG21E2sQe85xH9HqCrN4Ik ipcABejn_UtbFoHVHaZYyY6cydrEKnP4GgU3Tzt781MTYRTmxUxRQAsGr3FA nHW_a5mWrGutZ3E2rOTdejEn37b7FNzu_7EZ3.Sgi15.snKb3e9_1iEgyrOo q4dFIr4uV1wrI0mKSoxYA1p8OhVr1pN69H0OY0CNdlrm7PpRqqEh8Fa7CQcv pXUN2tmnDB3cM2eGqCCzPLVS80p91mDpBTVjfWpWlBVOajTunfT2I0Kti9LJ FIvb_ X-Yahoo-Newman-Property: ymail-3 References: In-Reply-To: Mime-Version: 1.0 (iPhone Mail 8G4) Content-Type: text/plain; charset=us-ascii Message-Id: <4579747F-628E-491A-A48C-C4C26AF8F5EB@behanna.org> Content-Transfer-Encoding: quoted-printable X-Mailer: iPhone Mail (8G4) From: Chris BeHanna Date: Sat, 16 Apr 2011 14:12:46 -0500 To: Daniel Mayfield Cc: "freebsd-fs@freebsd.org" Subject: Re: question on extended attributes 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, 16 Apr 2011 19:26:40 -0000 On Apr 15, 2011, at 17:01, Daniel Mayfield wrote: > I'm trying to use rsync and rsnapshot to make backup copies of my Mac to m= y freebsd 8.2 server . When I specify syncing extended attributes as well, I= get an error for any file on the Mac that has a resource fork:=20 >=20 > rsync: rsync_xal_set: lsetxattr("Documents/","com.apple.ResourceFork"= ) failed: No space left on device (28) >=20 > I'd love to work on fixing this, but I'm seeing a bunch of references to U= FS1 vs UFS2 in the extended attribute readme. But I'm not sure what I'm act= ually using (I took the default when it setup, which says ufs2+softdep, but m= ount simply says ufs). >=20 > Can someone help point me in the right direction? Although I can't answer your specific question, I *can* tell you that creati= ng an HFS+ sparsebundle with a large maximum size on your Mac, copying it to= your FreeBSD box, mounting it on your Mac over NFS, and then backing up to i= t does work. You may even be able to use Time Machine with it.=20 -- Chris BeHanna chris@behanna.org=